[Idr] 2 week WG adoption call for draft (5/31 to 6/14)
"Susan Hares" <shares@ndzh.com> Mon, 01 June 2015 02:51 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE191B2A08 for <idr@ietfa.amsl.com>; Sun, 31 May 2015 19:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.354
X-Spam-Level:
X-Spam-Status: No, score=-96.354 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7AkJlQP9jBfL for <idr@ietfa.amsl.com>; Sun, 31 May 2015 19:50:58 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 9651F1B2A07 for <idr@ietf.org>; Sun, 31 May 2015 19:50:57 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=184.157.80.157;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Sun, 31 May 2015 22:50:32 -0400
Message-ID: <006801d09c15$ba8bba30$2fa32e90$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0069_01D09BF4.338034B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCcFZhI02dMMr/nT2G7OxxFIHkvDg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/NTIkQgPvxbPc9WS5si0mZfQIj3k>
Cc: 'Robert Raszuk' <robert@raszuk.net>, 'Paul Jakma' <paulj@dcs.gla.ac.uk>, 'Shane Amante' <amante@apple.com>, 'Bruno Decraene' <bruno.decraene@orange.com>, draft-raszuk-wide-bgp-communities@tools.ietf.org
Subject: [Idr] 2 week WG adoption call for draft (5/31 to 6/14)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2015 02:51:01 -0000
This begins a 2 week WG adoption call for draft-raszuk-wide-bgp-communities and draft-raszuk-registered-wide-bgp-communities. These drafts can be found at: https://datatracker.ietf.org/doc/draft-raszuk-wide-bgp-communities/ http://datatracker.ietf.org/doc/draft-raszuk-registered-wide-bgp-communities / Authors (Robert Raszuk, Jeff Haas, Andrew Lange, Shane Amante, Bruno Decraene, Paul Jakma, and Richard Steenbergen) should indicate whether they know of any IPR. Since this proposal relates to existing RFCs and IDR WG document (draft-ietf-idr-as4octet-extcomm-generic-subtype-07), We have included a bit of history below. At the 6/1/2015 interim (10:00 - 11:30am EDT), there will be a short review of the technology and time to discuss the draft with Robert Raszuk. Please discuss a) If these drafts should be adopted in addition to draft-ietf-idr-as4octet-extcomm-generic-subtype-07, b) whether the new flexible format is useful for BGP deployments, and c) Any technical issues on the draft. As always, indicate "support" or "no support" within the comment. Sue Hares and John Scudder ================= A bit of history: RFC 1997 defines the BGP Community attribute (except for 2 reserved ranges) as 4 octets [2 octets AS number, 2 octets local-defined value]. RFC 4893 introduced 4 byte AS encoding, and suggested using extended communities [RFC 4360] to encoding 4 octet AS numbers. RFC5668 defines a format for a four-octet AS specific extended community with a designated type field, and defines two sub-types: Four-octet specific Route Target extended community and Four-octet specific Route Origin extended community. An IDR WG document: draft-ietf-idr-as4octet-extcomm-generic-subtype-07 (https://tools.ietf.org/html/draft-ietf-idr-as4octet-extcomm-generic-subtype -07) specifies a generic sub-type for the four-octet AS specific extended community. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 0x02 or 0x42 | 0x04 | Global | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Administrator | Local Administrator | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Global Administrator sub-field: 4 octets This sub-field contains a four-octet Autonomous System number. Local Administrator sub-field: 2 octets This sub-field contains a value that can influence routing policies. This value has semantics that are of significance for the Autonomous System in the Global Administrator field. [From draft-ietf-idr-as4octet-extcomm-generic-subtype-07] Draft-raszuk-wide-bgp-communities suggests a new BGP Path Attribute, that provides more flexible encoding than these WG RFCs and draft. The wide BGP header includes a Container header and community. The container header has: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Flags | Hop Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Registered/Local Community Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source AS Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Context AS Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Wide Community Target(s) TLV (optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Wide Community Exclude Target(s) TLV (optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Wide Community Parameter(s) TLV (optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 4: Wide BGP Community Type 1
- [Idr] 2 week WG adoption call for draft (5/31 to … Susan Hares
- Re: [Idr] 2 week WG adoption call for draft (5/31… bruno.decraene
- Re: [Idr] 2 week WG adoption call for draft (5/31… Thomas Mangin
- Re: [Idr] 2 week WG adoption call for draft (5/31… Robert Raszuk
- Re: [Idr] 2 week WG adoption call for draft (5/31… Nick Hilliard
- Re: [Idr] 2 week WG adoption call for draft (5/31… Susan Hares
- Re: [Idr] 2 week WG adoption call for draft (5/31… Nick Hilliard
- Re: [Idr] 2 week WG adoption call for draft (5/31… Robert Raszuk
- Re: [Idr] 2 week WG adoption call for draft (5/31… Gaurab Raj Upadhaya
- Re: [Idr] 2 week WG adoption call for draft (5/31… Andrew Lange
- Re: [Idr] 2 week WG adoption call for draft (5/31… Shane Amante
- Re: [Idr] 2 week WG adoption call for draft (5/31… Jon Mitchell
- Re: [Idr] 2 week WG adoption call for draft (5/31… Jeffrey Haas
- Re: [Idr] 2 week WG adoption call for draft (5/31… Shane Amante
- Re: [Idr] 2 week WG adoption call for draft (5/31… Susan Hares
- Re: [Idr] 2 week WG adoption call for draft (5/31… Robert Raszuk
- Re: [Idr] 2 week WG adoption call for draft (5/31… Susan Hares