[mpls] Question on the wording in section 3 of draft-ietf-mpls-seamless-mcast
"Osborne, Eric" <eric.osborne@level3.com> Thu, 07 May 2015 19:05 UTC
Return-Path: <eric.osborne@level3.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5F91A8847 for <mpls@ietfa.amsl.com>; Thu, 7 May 2015 12:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 D7gtnKCUyDOQ for <mpls@ietfa.amsl.com>; Thu, 7 May 2015 12:05:46 -0700 (PDT)
Received: from mail1.bemta12.messagelabs.com (mail1.bemta12.messagelabs.com [216.82.251.3]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E21791A882D for <mpls@ietf.org>; Thu, 7 May 2015 12:05:45 -0700 (PDT)
Received: from [216.82.250.99] by server-3.bemta-12.messagelabs.com id 6C/C3-26447-987BB455; Thu, 07 May 2015 19:05:45 +0000
X-Env-Sender: eric.osborne@level3.com
X-Msg-Ref: server-16.tower-126.messagelabs.com!1431025544!15232862!1
X-Originating-IP: [209.245.18.37]
X-StarScan-Received:
X-StarScan-Version: 6.13.14; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12952 invoked from network); 7 May 2015 19:05:45 -0000
Received: from bge23000.messagelabs1.prod.broomfield1.level3.net (HELO messagelabs1.level3.com) (209.245.18.37) by server-16.tower-126.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 May 2015 19:05:45 -0000
Received: from USIDCWVEHT02.corp.global.level3.com (usidcwveht02.corp.global.level3.com [10.1.142.32]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "USIDCWVEHT02.corp.global.level3.com", Issuer "VIDCCERT0001" (not verified)) by messagelabs1.level3.com (Postfix) with ESMTPS id C106C1F694 for <mpls@ietf.org>; Thu, 7 May 2015 19:05:44 +0000 (GMT)
Received: from USADCWVEHT01.corp.global.level3.com (10.2.36.141) by USIDCWVEHT02.corp.global.level3.com (10.1.142.32) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 7 May 2015 13:05:44 -0600
Received: from USIDCWVEMBX03.corp.global.level3.com ([fe80::e849:4e57:cb74:ed58]) by usadcwveht01.corp.global.level3.com ([::1]) with mapi id 14.03.0210.002; Thu, 7 May 2015 15:05:43 -0400
From: "Osborne, Eric" <eric.osborne@level3.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: Question on the wording in section 3 of draft-ietf-mpls-seamless-mcast
Thread-Index: AdCI+LZvUi1dPGp4SRKZspxSakqu7w==
Date: Thu, 07 May 2015 19:05:42 +0000
Message-ID: <63CB93BC589C1B4BAFDB41A0A19B7ACD1A2368BD@USIDCWVEMBX03.corp.global.level3.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.141.15]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/DlGl-Dy00AArw_j5zNqL68AB4mk>
Subject: [mpls] Question on the wording in section 3 of draft-ietf-mpls-seamless-mcast
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2015 19:05:47 -0000
Note: I sent this to draft-ietf-mpls-seamless-mcast@ietf.org but got some weird bounce so I'm not sure if it made it through. Section 3, bottom of p. 5 and into p. 6: "One possible way to support the global table multicast service is by relying on the MVPN procedures, as specified in [RFC6514], in which case the MVPN procedures specified in this[1] document would be used to support the global table multicast service. This[2] document specifies an alternative approach to support the global table multicast service." Does [1] refer to rfc6514 and [2] refer to draft-ietf-mpls-seamless-mcast? Does draft-ietf-mpls-seamless-mcast specify two approaches to global table multicast and use both of the 'this' to refer to itself? eric
- [mpls] Question on the wording in section 3 of dr… Osborne, Eric