BGP based Multi-homing in Virtual Private LAN Service
draft-ietf-bess-vpls-multihoming-05

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-ietf-bess-vpls-multihoming-05. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there is a single action which we must complete.

In the Layer2 Info Extended Community Control Flags Bit Vector registry on the Border Gateway Protocol (BGP) Extended Communities registry page located at:

https://www.iana.org/assignments/bgp-extended-communities/

two new registrations are to be made as follows:

Value: D
Name: Down connectivity status
Reference: [ RFC-to-be ]
Date: [ TBD-at-Registration ]

Value: F
Name: MAC flush indicator
Reference: [ RFC-to-be ]
Date: [ TBD-at-Registration ]

The IANA Functions Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2020-03-12):

From: The IESG
To: IETF-Announce
CC: Matthew Bocci , matthew.bocci@nokia.com, draft-ietf-bess-vpls-multihoming@ietf.org, martin.vigoureux@nokia.com, bess@ietf.org, bess-chairs@ietf.org
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (BGP based Multi-homing in Virtual Private LAN Service) to Proposed Standard


The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'BGP based Multi-homing in Virtual Private
LAN Service'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-03-12. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private
  Network (VPN) that gives its customers the appearance that their
  sites are connected via a Local Area Network (LAN).  It is often
  required for the Service Provider (SP) to give the customer redundant
  connectivity to some sites, often called "multi-homing".  This memo
  shows how BGP-based multi-homing can be offered in the context of LDP
  and BGP VPLS solutions.  This document updates RFC 4761 by defining
  new flags in the Control Flags field of the Layer2 Info Extended
  Community.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-vpls-multihoming/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bess-vpls-multihoming/ballot/

The following IPR Declarations may be related to this I-D:

  https://datatracker.ietf.org/ipr/1809/
  https://datatracker.ietf.org/ipr/3838/

draft-ietf-bess-vpls-multihoming-05

Document Shepherd Write-Up

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

  Standard track.
 
  This is appropriate as the draft describes a set of protocol extensions to enable
  multi-homing into a VPLS using BGP, including new BGP extended community flags.
 
  The intended status is properly indicated.

(2) 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

Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private
  Network (VPN) that gives its customers the appearance that their
  sites are connected via a Local Area Network (LAN).  It is often
  required for the Service Provider (SP) to give the customer redundant
  connectivity to some sites, often called "multi-homing".  This memo
  shows how BGP-based multi-homing can be offered in the context of LDP
  and BGP VPLS solutions.

Working Group Summary

  The document was developed to address the need to provide multi-homing
  into a VPLS service for resiliency, using BGP based mechanisms. The draft
  was originally developed some years ago in the L2VPN working group. It then moved
  to BESS when this WG was formed, since it handles BGP-based mechanisms. However,
  it languished for some time due to the WG changes and changes in personnel. It
  is nonetheless a useful piece of work and the resulting technology is believed
  to have been implemented and deployed.

  There is one IPR declaration on the draft .

     
Document Quality
   
  I have no concerns about the quality of the document. I believe it represents
  WG consensus, and it has been widely reviewed and discussed on the list over a
  number of years.
 
  The document does not specify any MIB changes or additions which would need
  review.

   
Personnel

  The document shepherd is Matthew Bocci (matthew.bocci@nokia.com).
  The responsible Area Director is Martin Vigoureux (martin.vigoureux@nokia.com).

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

  The document shepherd reviewed v02 of the document. I had no significant technical
  comments, but I did make some editorial comments that were resolved in
  version 03. The subsequent revisions were to resolve nits.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

  No concerns. The document has received adequate review. The document has
  been developed within the WG and reviewed over a
  period of a number of IETFs. It originated in the L2VPN working group
  and so has been developed and reviewed over many years.

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

  No further review required.

(6) Describe any specific concerns or issues that the Document Shepherd
has 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.

  No specific concerns.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

  Each author listed in the Authors Addresses section has personally indicated that
  they are not aware of any IPR that has not already been declared in accordance
  with BCP 78 and 79.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

  There is one IPR declarations on the draft, which was submitted back when this
  a WG draft in the former L2VPN working group. The shepherd is not aware of
  concerns raised about this IPR declaration.


 
(9) 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?

    I am comfortable that the document represents WG consensus and has
    been reviewed by a reasonable number of active WG participants.
    There were no objections during last call.
   

(10) 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 publicly available.)

  None indicated.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

      ID-Nits passes.


(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

  There are no relevant formal review criteria.

(13) Have all references within this document been identified as
either normative or informative?

  Yes. All references are explicitly identified as informative or normative.

(14) 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 plan for their completion?

  No

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.

  No.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

  This document updates RFC4761. The update is required because the draft presents some
  changes to the multi-homing procedures in RFC4761. The update is properly indicated
  and it is obvious form the draft text where changes to 4761 are required to support
  the mechanisms in this draft.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

  The document requests new flags from the Layer 2 information extended community
  control flags bit vector. This request is properly indicated.
     

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

  There are no new IANA registries required.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

  There are no sections containing formal language that needs reviewing.

draft-ietf-bess-vpls-multihoming-05

Document Shepherd Write-Up

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

  Standard track.
 
  This is appropriate as the draft describes a set of protocol extensions to enable
  multi-homing into a VPLS using BGP, including new BGP extended community flags.
 
  The intended status is properly indicated.

(2) 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

Virtual Private LAN Service (VPLS) is a Layer 2 Virtual Private
  Network (VPN) that gives its customers the appearance that their
  sites are connected via a Local Area Network (LAN).  It is often
  required for the Service Provider (SP) to give the customer redundant
  connectivity to some sites, often called "multi-homing".  This memo
  shows how BGP-based multi-homing can be offered in the context of LDP
  and BGP VPLS solutions.

Working Group Summary

  The document was developed to address the need to provide multi-homing
  into a VPLS service for resiliency, using BGP based mechanisms. The draft
  was originally developed some years ago in the L2VPN working group. It then moved
  to BESS when this WG was formed, since it handles BGP-based mechanisms. However,
  it languished for some time due to the WG changes and changes in personnel. It
  is nonetheless a useful piece of work and the resulting technology is believed
  to have been implemented and deployed.

  There is one IPR declaration on the draft .

     
Document Quality
   
  I have no concerns about the quality of the document. I believe it represents
  WG consensus, and it has been widely reviewed and discussed on the list over a
  number of years.
 
  The document does not specify any MIB changes or additions which would need
  review.

   
Personnel

  The document shepherd is Matthew Bocci (matthew.bocci@nokia.com).
  The responsible Area Director is Martin Vigoureux (martin.vigoureux@nokia.com).

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

  The document shepherd reviewed v02 of the document. I had no significant technical
  comments, but I did make some editorial comments that were resolved in
  version 03. The subsequent revisions were to resolve nits.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

  No concerns. The document has received adequate review. The document has
  been developed within the WG and reviewed over a
  period of a number of IETFs. It originated in the L2VPN working group
  and so has been developed and reviewed over many years.

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

  No further review required.

(6) Describe any specific concerns or issues that the Document Shepherd
has 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.

  No specific concerns.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

  Each author listed in the Authors Addresses section has personally indicated that
  they are not aware of any IPR that has not already been declared in accordance
  with BCP 78 and 79.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

  There is one IPR declarations on the draft, which was submitted back when this
  a WG draft in the former L2VPN working group. The shepherd is not aware of
  concerns raised about this IPR declaration.


 
(9) 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?

    I am comfortable that the document represents WG consensus and has
    been reviewed by a reasonable number of active WG participants.
    There were no objections during last call.
   

(10) 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 publicly available.)

  None indicated.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

      ID-Nits passes.


(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

  There are no relevant formal review criteria.

(13) Have all references within this document been identified as
either normative or informative?

  Yes. All references are explicitly identified as informative or normative.

(14) 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 plan for their completion?

  No

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in the
Last Call procedure.

  No.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

  This document updates RFC4761. The update is required because the draft presents some
  changes to the multi-homing procedures in RFC4761. The update is properly indicated
  and it is obvious form the draft text where changes to 4761 are required to support
  the mechanisms in this draft.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

  The document requests new flags from the Layer 2 information extended community
  control flags bit vector. This request is properly indicated.
     

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

  There are no new IANA registries required.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

  There are no sections containing formal language that needs reviewing.

Request for posting confirmation emailed to previous authors: Kireeti Kompella , Senad Palislamovic , Florin Balus , Jim Uttaro , Wim Henderickx , Bhupesh Kothari , bess-chairs@ietf.org, Wen Lin