[Idr] 2 week WG LC for draft-ietf-idr-rtc-no-rt
"Susan Hares" <shares@ndzh.com> Mon, 20 April 2015 20:59 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 6F8251B31B3 for <idr@ietfa.amsl.com>; Mon, 20 Apr 2015 13:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jLiD0g1sF7rs for <idr@ietfa.amsl.com>; Mon, 20 Apr 2015 13:59:06 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA691B31AE for <idr@ietf.org>; Mon, 20 Apr 2015 13:59:06 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=222.151.138.72;
From: Susan Hares <shares@ndzh.com>
To: idr@ietf.org
Date: Mon, 20 Apr 2015 16:58:58 -0400
Message-ID: <01a801d07bac$d4756880$7d603980$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A9_01D07B8B.4D654F20"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdB7qgBSfoAujn4fTbOJuE6lxY/Vnw==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/EOKVZQUq7HwPwYv-iS5UyeMoCSM>
Subject: [Idr] 2 week WG LC for draft-ietf-idr-rtc-no-rt
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, 20 Apr 2015 20:59:08 -0000
This begins a 2 week WG LC for draft-ietf-idr-rtc-no-rt (4/20/2015 to 5/4/2015). You can see the draft at: http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-no-rt/ Other current drafts for Route Targets in IDR are: http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-hierarchical-rr/ http://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ipv6-rt-constrain/ Appropriate questions for this WG LC are: 1) Does this default manner handling routes with no RTCs provide good operational BGP for networks you are aware of? 2) Does this method of default work for you: RTC applied + MDT-SAFI (SAFI=66) implies routes without RTs are distributed RTC applied + MCAST-VPN (SAFI=6) implies routes without RTs are distributed RTC applied + any other address family - implies routes without RTs are not distributed Should IANA create a registry which indicates the status of RTC application or is the draft sufficient: Other IDR drafts on RT constraints are: http://datatracker.ietf.org/doc/draft-ietf-idr-rtc-hierarchical-rr/ http://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ipv6-rt-constrain/ Please indicate in your message discussing this approach an indication of "support" or "no support". Sue Hares
- [Idr] 2 week WG LC for draft-ietf-idr-rtc-no-rt Susan Hares