WG Review: Recharter of Inter-Domain Routing (idr)

A modified charter has been submitted for the Inter-Domain Routing (idr)
working group in the Routing Area of the IETF.  The IESG has not made any
determination as yet.  The modified charter is provided below for
informational purposes only.  Please send your comments to the IESG
mailing list (iesg <at> ietf.org) by Tuesday, February 16, 2010.

Inter-Domain Routing (idr)
-----------------------------
Last Modified: 2010-02-04

Additional information is available at tools.ietf.org/wg/idr

Chair(s):
- Susan Hares <shares <at> ndzh.com>
- John Scudder <jgs <at> juniper.net>

Routing Area Director(s):
- Ross Callon <rcallon <at> juniper.net>
- Adrian Farrel <adrian.farrel <at> huawei.com>

Routing Area Advisor:
- Ross Callon <rcallon <at> juniper.net>

Mailing Lists:
General Discussion: idr <at> ietf.org
To Subscribe: idr-request <at> ietf.org
In Body: subscribe idr-post
Archive: http://www.ietf.org/mail-archive/web/idr/index.html

Description of Working Group:

The Inter-Domain Routing Working Group is chartered to standardize,
develop, and support the Border Gateway Protocol Version 4 (BGP-4)
[RFC 4271] capable of supporting policy based routing for TCP/IP
internets.

The main objective of the working group is to support the use of
BGP-4 by IP version 4 and IP version 6 networks. The working group
will also continue to work on improving the robustness and
scalability of BGP.

IDR will review extensions made to BGP in other working groups at least
at WG document adoption and during working group last calls. The IDR
working group will also provide advice and guidance on BGP to other
working groups as requested.

Work Items:

The IDR working group will work on correctness, robustness and
scalability of the BGP protocol, as well as clarity and accuracy of the
BGP document set. The group will also work on extensions beyond these
areas when specifically added to the charter. The current additional
work items are:

- Relax the definition of BGP identifiers to only require AS-wide
uniqueness. This change must be made in a backward compatible way.

- Specify a means to non-disruptively introduce new BGP Capabilities
to an existing BGP session.

- Upgrade of the base BGP specification to Full Standard

- Define AS_PATH based Outbound Route Filtering.

- MIB v2 for BGP-4

- Augment the BGP multiprotocol extensions to support the use of
multiple concurrent sessions between a given pair of BGP speakers.
Each session is used to transport routes related by some session-
based attribute such as AFI/SAFI. This will provide an alternative
to the MP-BGP approach of multiplexing all routes onto a single
connection.

- Support for four-octet AS Numbers in BGP.

- Revisions to the BGP 'Minimum Route Advertisement Interval'
deprecating the previously recommended values and allowing for
withdrawals to be exempted from the MRAI.

- Advertisement of multiple paths for the same address prefix without
the new paths implicitly replacing any previous ones. Each path is
identified by a path identifier in addition to the address prefix.

- Revised error handling rules for optional transitive BGP attributes
so that a BGP speaker is no longer required to reset the session
over which a malformed attribute is received. Provide guidelines
for authors of documents that define new optional transitive
attributes, and re-assess procedures for existing optional
transitive attributes

- Specify Link Bandwidth Extended Community for use in unequal cost
load balancing.

- The definition of an "Accumulated IGP Metric" attribute for BGP
to report the sum of the metric of each link along the path.
This attribute is for use in a restricted environment where:
- all ASes are subject to the administrative control
- some form of tunneling is used to deliver a packet to its next
BGP hop
- where the path for a route leads outside the AS to which the
BGP speaker adding the attribute belongs.

- Advertisement of the best external route in BGP to assist with
resolution of the next hop in the chosen data plane.

Goals and Milestones:

Done Submit to BGP Capability Advertisement to the IESG
Done Submit BGP Security Vulnerabilities Analysis to IESG as an
Informational
Done Submit BGP4 MIB to IESG as a Proposed Standard
Done Submit BGP4 document to IESG as a Draft Standard
Done Submit Extended Communities draft to IESG as a Proposed Standard
Done Submit BGP Graceful Restart to IESG as a Proposed Standard
Done Submit revised text on Multi-Protocol BGP (rfc2858bis) to IESG as a
Draft Standard
Done Submit Subcodes for BGP Cease Notification Message to IESG as a
Proposed Standard
Done Submit 4-byte AS ID to IESG as a Proposed Standard
Done Submit Outbound Route Filter and Prefix ORF draft to IESG as
a Proposed Standard
Done Prefix and ASpath ORF draft to IESG as a Proposed Standard
Aug 2010 Submit AS-wide Unique BGP Identifier for BGP-4 as a Proposed
Standard
Aug 2010 Submit Dynamic Capability for BGP-4 to IESG as a Proposed
Standard
Aug 2010 ASpath ORF draft to IESG as a Proposed Standard
Aug 2010 Submit MIB v2 for BGP-4 as a Proposed Standard
Nov 2010 BGP Support for Four-octet AS Number Space (revised version)
Nov 2010 Revisions to the BGP 'Minimum Route Advertisement Interval'
Nov 2010 Advertisement of Multiple Paths in BGP
Nov 2010 BGP Link Bandwidth Extended Community
Nov 2010 Advertisement of the best external route in BGP
Dec 2010 Submit Multisession BGP as a Proposed Standard
Dec 2010 Error Handling for Optional Transitive BGP Attributes
Dec 2010 ASpath ORF
Dec 2010 Revise WG charter
Mar 2011 The Accumulated IGP Metric Attribute for BGP
Mar 2011 Base BGP specification (RFC 4271) as Full Standard
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-add-paths-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : Advertisement of Multiple Paths in BGP
	Author(s)       : D. Walton, et al.
	Filename        : draft-ietf-idr-add-paths-03.txt
	Pages           : 8
	Date            : 2010-02-06

In this document we propose a BGP extension that allows the
advertisement of multiple paths for the same address prefix without
the new paths implicitly replacing any previous ones.  The essence of
the extension is that each path is identified by a path identifier in
addition to the address prefix.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-add-paths-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

WG Last Call for AS-wide Unique BGP Identifier for BGP-4

Folks,

This is to start the IDR WG Last Call on advancing draft-ietf-idr-bgp-identifier-11.txt as a Proposed
Standard RFC. The deadline for comments is February 19, 2010.

A URL for the draft is http://www.ietf.org/id/draft-ietf-idr-bgp-identifier-11.txt

--John
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-bgp-identifier-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : AS-wide Unique BGP Identifier for BGP-4
	Author(s)       : E. Chen, J. Yuan
	Filename        : draft-ietf-idr-bgp-identifier-11.txt
	Pages           : 5
	Date            : 2010-02-04

To accommodate situations where the current requirements for the BGP
Identifier are not met, this document relaxes the definition of the
BGP Identifier to be a 4-octet unsigned, non-zero integer, and
relaxes the "uniqueness" requirement so that only AS-wide uniqueness
of the BGP Identifiers is required. These revisions to the base BGP
specification do not introduce any backward compatibility issue.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp-identifier-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-best-external-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : Advertisement of the best external route in BGP
	Author(s)       : P. Marques, et al.
	Filename        : draft-ietf-idr-best-external-01.txt
	Pages           : 11
	Date            : 2010-02-04

The base BGP specifications prevent a BGP speaker from advertising
any route that is not the best route for a BGP destination.  This
document specifies a modification of this rule.  Routes are divided
into two categories, "external" and "internal".  A specification is
provided for choosing a "best external route" (for a particular value
of the Network Layer Reachability Information).  A BGP speaker is
then allowed to advertise its "best external route" to its internal
BGP peers, even if that is not the best route for the destination.
The document explains why advertising the best external route can
improve convergence time without causing routing loops.  Additional
benefits include reduction of inter-domain churn and avoidance of
permanent route oscillation.  The document also generalizes the
notions of "internal" and "external" so that they can be applied to
Route Reflector Clusters and Autonomous System Confederations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-best-external-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-bgp4-mibv2-10.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version
	Author(s)       : J. Haas
	Filename        : draft-ietf-idr-bgp4-mibv2-10.txt
	Pages           : 45
	Date            : 2010-02-01

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols.  In particular it defines
objects for managing the Border Gateway Protocol, Version 4.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-mibv2-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-bgp4-mibv2-tc-mib-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : Definitions of Textual Conventions for the Management of the Fourth Version of Border Gateway
Protocol (BGP-4)
	Author(s)       : J. Haas
	Filename        : draft-ietf-idr-bgp4-mibv2-tc-mib-01.txt
	Pages           : 6
	Date            : 2010-02-01

This memo defines a portion of the Management Information Base (MIB)
which defines Textual Conventions for the management of BGP-4.  The
intent is that these textual conventions will be used in BGP-related
MIB modules that would otherwise define their own representations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-bgp4-mibv2-tc-mib-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

Revised proposed IDR charter

Folks,

As you know we're in the process of updating our charter.  Here's a revision to the version we discussed in
Hiroshima, incorporating comments received from WG members and feedback from the IESG and Routing ADs. 
The main changes are a statement that IDR has oversight responsibility for all BGP work done in the IETF,
and an elaborated scope of work section.

If you have comments, please send them within the next week.  

Thanks,

--John & Sue

Inter-Domain Routing (idr)
Last Modified: 2010-01-26

Additional information is available at tools.ietf.org/wg/idr

Chair(s):
 - Susan Hares <shares <at> ndzh.com>
 - John Scudder <jgs <at> juniper.net>

Routing Area Director(s):
 - Ross Callon <rcallon <at> juniper.net>
 - Adrian Farrel <adrian.farrel <at> huawei.com>

Routing Area Advisor:
 - Ross Callon <rcallon <at> juniper.net>

Mailing Lists:
 General Discussion: idr <at> ietf.org
 To Subscribe: idr-request <at> ietf.org
 In Body: subscribe idr-post
 Archive: http://www.ietf.org/mail-archive/web/idr/index.html

Description of Working Group:

The Inter-Domain Routing Working Group is chartered to standardize,
develop, and support the Border Gateway Protocol Version 4 (BGP-4)
[RFC 4271] capable of supporting policy based routing for TCP/IP
internets.

The main objective of the working group is to support the use of
BGP-4 by IP version 4 and IP version 6 networks. The working group
will also continue to work on improving the robustness and
scalability of BGP.

The IDR working group also has an oversight role for all extensions made
to BGP for other uses that may be developed in other working groups. IDR 
will review extensions made to BGP in other working groups at least at 
WG document adoption and during working group last calls. The IDR working 
group will also provide advice and guidance on BGP to other working groups
as requested. In some cases the IDR WG chairs may work with the chairs of
other working groups and the IESG to move BGP work into the IDR WG instead 
of the another WG.

Work Items:

The IDR working group will work on correctness, robustness and
scalability of the BGP protocol, as well as clarity and accuracy of the
BGP document set.  The group will also work on extensions beyond these
areas when specifically added to the charter.  The current additional
work items are:

- Relax the definition of BGP identifiers to only require AS-wide
  uniqueness. This change must be made in a backward compatible way.

- Specify a means to non-disruptively introduce new BGP Capabilities 
  to an existing BGP session.

- Upgrade of the base BGP specification to Full Standard

- Define AS_PATH based Outbound Route Filtering.

- MIB v2 for BGP-4

- Augment the BGP multiprotocol extensions to support the use of
  multiple concurrent sessions between a given pair of BGP speakers.
  Each session is used to transport routes related by some session-
  based attribute such as AFI/SAFI. This will provide an alternative
  to the MP-BGP approach of multiplexing all routes onto a single
  connection.

- Support for four-octet AS Numbers in BGP.

- Revisions to the BGP 'Minimum Route Advertisement Interval'
  deprecating the previously recommended values and allowing for
  withdrawals to be exempted from the MRAI.

- Advertisement of multiple paths for the same address prefix without
  the new paths implicitly replacing any previous ones. Each path is
  identified by a path identifier in addition to the address prefix.

- Revised error handling rules for optional transitive BGP attributes
  so that a BGP speaker is no longer required to reset the session
  over which a malformed attribute is received. Provide guidelines
  for authors of documents that define new optional transitive
  attributes, and re-assess procedures for existing optional
  transitive attributes

- Specify Link Bandwidth Extended Community for use in unequal cost
  load balancing.

- The definition of an "Accumulated IGP Metric" attribute for BGP
  to report the sum of the metric of each link along the path.
  This attribute is for use in a restricted environment where:
  - all ASes are subject to the administrative control
  - some form of tunneling is used to deliver a packet to its next
    BGP hop
  - where the path for a route leads outside the AS to which the
    BGP speaker adding the attribute belongs.

- Advertisement of the best external route in BGP to assist with
  resolution of the next hop in the chosen data plane.

Goals and Milestones:

Done  Submit to BGP Capability Advertisement to the IESG
Done  Submit BGP Security Vulnerabilities Analysis to IESG as an
      Informational
Done  Submit BGP4 MIB to IESG as a Proposed Standard
Done  Submit BGP4 document to IESG as a Draft Standard
Done  Submit Extended Communities draft to IESG as a Proposed Standard
Done  Submit BGP Graceful Restart to IESG as a Proposed Standard
Done  Submit revised text on Multi-Protocol BGP (rfc2858bis) to IESG as a
      Draft Standard
Done  Submit Subcodes for BGP Cease Notification Message to IESG as a
      Proposed Standard
Done  Submit 4-byte AS ID to IESG as a Proposed Standard
Done  Submit Outbound Route Filter, Prefix and ASpath ORF draft to IESG as
      a Proposed Standard
Done  Prefix and ASpath ORF draft to IESG as a Proposed Standard
Aug 2010 Submit AS-wide Unique BGP Identifier for BGP-4 as a Proposed
         Standard
Aug 2010 Submit Dynamic Capability for BGP-4 to IESG as a Proposed Standard
Aug 2010 ASpath ORF draft to IESG as a Proposed Standard
Aug 2010 Submit MIB v2 for BGP-4 as a Proposed Standard
Nov 2010 BGP Support for Four-octet AS Number Space (revised version)
Nov 2010 Revisions to the BGP 'Minimum Route Advertisement Interval'
Nov 2010 Advertisement of Multiple Paths in BGP
Nov 2010 BGP Link Bandwidth Extended Community
Nov 2010 Advertisement of the best external route in BGP
Dec 2010 Submit Multisession BGP as a Proposed Standard
Dec 2010 Error Handling for Optional Transitive BGP Attributes
Dec 2010 Revise WG charter
Mar 2011 The Accumulated IGP Metric Attribute for BGP
Mar 2011 Base BGP specification (RFC 4271) as Full Standard

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

Question on draft-ietf-idr-rfc4893bis-01.txt

I have a couple of questions on the error handling procedures in draft-ietf-idr-rfc4893bis-01.txt.

(1) Some snippets from Section 6, on Error Handling

   The general guidelines presented in [ATTR-ERROR] apply to the error
   handling of the AS4_PATH and AS4_AGGREGATOR attributes introduced in
   this document.

   ...

   A NEW BGP speaker that receives a malformed AS4_PATH attribute in an
   UPDATE message from an OLD BGP speaker MUST discard the attribute,
   and continue processing the UPDATE message.

   ...

   A NEW BGP speaker that receives a malformed AS4_AGGREGATOR attribute
   in an UPDATE message from an OLD BGP speaker MUST discard the
   attribute, and continue processing the UPDATE message

Although this section makes a reference to [ATTR-ERROR], my understanding upon reading
draft-ietf-idr-rfc4893bis-01.txt is that a malformed AS4_PATH or AS4_AGGREGATOR MUST be discarded
irrespective of the Partial bit in the Attribute Flags. Is this interpretation correct ?

(2) If the attributes AS4_PATH and AS4_AGGREGATOR are not marked as optional transitive, this should
result in a notification message, irrespective of whether this was received from an OLD or NEW speaker,
right ? Although this draft attempts to ignore attributes with errors, since it does not mention anything
specific about the attribute flags, I am assuming that the following section from RFC 4271 still holds good.

   Section 6.3.  UPDATE Message Error Handling

   If any recognized attribute has Attribute Flags that conflict with
   the Attribute Type Code, then the Error Subcode MUST be set to
   Attribute Flags Error.  The Data field MUST contain the erroneous
   attribute (type, length, and value).

Thanks,
Manish Vora
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

I-D Action:draft-ietf-idr-dynamic-cap-10.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title           : Dynamic Capability for BGP-4
	Author(s)       : E. Chen, S. Ramachandra
	Filename        : draft-ietf-idr-dynamic-cap-10.txt
	Pages           : 8
	Date            : 2010-01-15

This document defines a new BGP capability termed "Dynamic
Capability", which would allow the dynamic update of capabilities
over an established BGP session. This capability would facilitate
non-disruptive capability changes by BGP speakers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-dynamic-cap-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr

[Fwd: I-D Action:draft-walton-bgp-route-oscillation-stop-02.txt]

FYI.    -- Enke

From: FYI. -- Enke <Internet-Drafts <at> ietf.org>
Subject: I-D Action:draft-walton-bgp-route-oscillation-stop-02.txt
Date: 2009-11-13 01:15:02 GMT

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : BGP Persistent Route Oscillation Solutions
	Author(s)       : D. Walton, et al.
	Filename        : draft-walton-bgp-route-oscillation-stop-02.txt
	Pages           : 9
	Date            : 2009-11-12

In this document we present two sets of paths for an address prefix
that can be advertised by a BGP route reflector or confederation ASBR
to eliminate the MED-induced route oscillations in a network.  The
first set involves all the available paths, and would achieve the
same routing consistency as the full IBGP mesh.  The second set,
which is a subset of the first one, involves the neighbor-AS based
Group Best Paths, and would be sufficient to eliminate the MED-
induced route oscillations (subject to certain commonly adopted
topological constrains).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-walton-bgp-route-oscillation-stop-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr