Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
draft-ietf-pce-inter-layer-frwk-10

Proto-write-up for draft-ietf-pce-inter-layer-frwk-10.txt

Intended status : Informational Track

> (1.a)  Who is the Document Shepherd for this document?  Has the
>        Document Shepherd personally reviewed this version of the
>        document and, in particular, does he or she believe this
>        version is ready for forwarding to the IESG for publication?

JP Vasseur is the document shepherd.
He has personally reviewed the document and believes it is ready for
forwarding to the IESG for publication.

> (1.b)  Has the document had adequate review both from key WG members
>        and from key non-WG members?  Does the Document Shepherd have
>        any concerns about the depth or breadth of the reviews that
>        have been performed?

The I-D has been discussed and reviewed by the Working group.

> (1.c)  Does the Document Shepherd have concerns that the document
>        needs more review from a particular or broader perspective,
>        e.g., security, operational complexity, someone familiar with
>        AAA, internationalization or XML?

No concerns.

> (1.d)  Does the Document Shepherd have any specific concerns or
>        issues with this document that the Responsible Area Director
>        and/or the IESG should be aware of?  For example, perhaps he
>        or she is uncomfortable with certain parts of the document, or
>        has concerns whether there really is a need for it.  In any
>        event, if the WG has discussed those issues and has indicated
>        that it still wishes to advance the document, detail those
>        concerns here.  Has an IPR disclosure related to this document
>        been filed?  If so, please include a reference to the
>        disclosure and summarize the WG discussion and conclusion on
>        this issue.

The document is sound.

> (1.e)  How solid is the WG consensus behind this document?  Does it
>        represent the strong concurrence of a few individuals, with
>        others being silent, or does the WG as a whole understand and
>        agree with it?

Good consensus.

> (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
>        discontent?  If so, please summarise the areas of conflict in
>        separate email messages to the Responsible Area Director.  (It
>        should be in a separate email because this questionnaire is
>        entered into the ID Tracker.)

No threats. No discontent.

> (1.g)  Has the Document Shepherd personally verified that the
>        document satisfies all ID nits?  (See
>        http://www.ietf.org/ID-Checklist.html and
>        http://tools.ietf.org/tools/idnits/).  Boilerplate checks are
>        not enough; this check needs to be thorough.  Has the document
>        met all formal review criteria it needs to, such as the MIB
>        Doctor, media type and URI type reviews?

Checks have been made. No Errors.

> (1.h)  Has the document split its references into normative and
>        informative?  Are there normative references to documents that
>        are not ready for advancement or are otherwise in an unclear
>        state?  If such normative references exist, what is the
>        strategy for their completion?  Are there normative references
>        that are downward references, as described in [RFC3967]?  If
>        so, list these downward references to support the Area
>        Director in the Last Call procedure for them [RFC3967].

References split.
No downrefs.

> (1.i)  Has the Document Shepherd verified that the document IANA
>        consideration section exists and is consistent with the body
>        of the document?  If the document specifies protocol
>        extensions, are reservations requested in appropriate IANA
>        registries?  Are the IANA registries clearly identified?  If
>        the document creates a new registry, does it define the
>        proposed initial contents of the registry and an allocation
>        procedure for future registrations?  Does it suggest a
>        reasonable name for the new registry?  See [RFC2434].  If the
>        document describes an Expert Review process has Shepherd
>        conferred with the Responsible Area Director so that the IESG
>        can appoint the needed Expert during the IESG Evaluation?

No IANA action.

> (1.j)  Has the Document Shepherd verified that sections of the
>        document that are written in a formal language, such as XML
>        code, BNF rules, MIB definitions, etc., validate correctly in
>        an automated checker?

No such formal language is used.

> (1.k)  The IESG approval announcement includes a Document
>        Announcement Write-Up.  Please provide such a Document
>        Announcement Write-Up.  Recent examples can be found in the
>        "Action" announcements for approved documents.  The approval
>        announcement contains the following sections:
>
>        Technical Summary
>          Relevant content can frequently be found in the abstract
>          and/or introduction of the document.  If not, this may be
>          an indication that there are deficiencies in the abstract
>          or introduction.
    A network may comprise multiple layers. These layers may represent
    separations of technologies (e.g., packet switch capable (PSC), time
    division multiplex (TDM), or lambda switch capable (LSC)) [RFC3945],
    separation of data plane switching granularity levels (e.g., PSC-1,
    PSC-2, VC4, or VC12) [RFC5212], or a distinction between client and
    server networking roles. In this multi-layer network, Label Switched
    Paths (LSPs) in a lower layer are used to carry higher-layer LSPs
    across the lower-layer network. The network topology formed by
    lower-layer LSPs and advertised as traffic engineering links (TE
    links) in the higher layer network is called the Virtual Network
    Topology (VNT) [RFC5212].

    It may be effective to optimize network resource utilization
    globally, i.e., taking into account all layers, rather than
    optimizing resource utilization at each layer independently. This
    allows better network efficiency to be achieved and is what we call
    inter-layer traffic engineering. This includes mechanisms allowing
    the computation of end-to-end paths across layers (known as inter-
    layer path computation), and mechanisms for control and management
    of the Virtual Network Topology (VNT) by setting up and releasing
    LSPs in the lower layers [RFC5212].

    Inter-layer traffic engineering is included in the scope of the Path
    Computation Element (PCE)-based architecture [RFC4655], and PCE can
    provide a suitable mechanism for resolving inter-layer path
    computation issues.

    PCE Communication Protocol requirements for inter-layer traffic
    engineering are set out in [PCE-INTER-LAYER-REQ].

    This document describes a framework for applying the PCE-based
    architecture to inter-layer traffic engineering. It provides
    suggestions for the deployment of PCE in support of multi-layer
    networks. This document also describes network models where PCE
    performs inter-layer traffic engineering, and the relationship
    between PCE and a functional component in charge of the control and
    management of the VNT, called the Virtual Network Topology Manager
    (VNTM).
>        Working Group Summary
>          Was there anything in WG process that is worth noting?  For
>          example, was there controversy about particular points or
>          were there decisions where the consensus was particularly
>          rough?

No controversy.

>        Document Quality
>          Are there existing implementations of the protocol?  Have a
>          significant number of vendors indicated their plan to
>          implement the specification?  Are there any reviewers that
>          merit special mention as having done a thorough review,
>          e.g., one that resulted in important changes or a
>          conclusion that the document had no substantive issues?  If
>          there was a MIB Doctor, Media Type or other expert review,
>          what was its course (briefly)?  In the case of a Media Type
>          review, on what date was the request posted?

The I-D is informational and specifies a framework.