RE: Last Call: 'Requirements for Multicast in L3 Provider-Provisioned VPNs' to Informational RFC (draft-ietf-l3vpn-ppvpn-mcast-reqts)

[<benjamin.niven-jenkins at bt.com>]

I support draft-ietf-l3vpn-ppvpn-mcast-reqts-08 becoming an
Informational RFC.  I have read the draft and have attached a number of
editorial changes/corrections as an rtf file with change tracking turned
on.

In addition I belive there are two places in the text that need further
correction:

Section 5.2.10 "with proper articulation" does the author really mean
articulation?  I think 'alignment' is a more appropriate term.

Section 5.2.11 "Most notably a solution supporting only a subset of
those requirements SHOULD be designed".  Which requirements are being
referred to by 'those requirements'?  If it the requirements in the
draft itself then I suggest the sentence is reworded to "most notably a
solution supporting only a subset of the requirements in this document
SHOULD be designed"

Thanks
Ben

-- 
Ben Niven-Jenkins
Network Architect, BT Exact
  
E-mail: benjamin.niven-jenkins at bt.com 
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827

The IESG <mailto:iesg-secretary at ietf.org> wrote:
> The IESG has received a request from the Layer 3 Virtual
> Private Networks WG to consider the following document:
> 
> - 'Requirements for Multicast in L3 Provider-Provisioned VPNs '
>    <draft-ietf-l3vpn-ppvpn-mcast-reqts-08.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action.  Please send any
> comments to the iesg at ietf.org or ietf at ietf.org mailing lists
> by 2From ietf-bounces at ietf.org Mon Aug 28 08:42:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GHgJH-0002Mv-52; Mon, 28 Aug 2006 08:33:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFSsJ-0007bC-HB
	for ietf at ietf.org; Tue, 22 Aug 2006 05:48:47 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFSsD-0000gZ-56
	for ietf at ietf.org; Tue, 22 Aug 2006 05:48:47 -0400
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 22 Aug 2006 10:48:35 +0100
Received: from E03MVY1-UKDY.domain1.systemhost.net ([193.113.30.58]) by
	i2kc06-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Tue, 22 Aug 2006 10:48:34 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6C5D0.222B776D"
Date: Tue, 22 Aug 2006 10:48:31 +0100
Message-ID: <FDDE83108C11054B813316D1C31516BF4D8EE5 at E03MVY1-UKDY.domain1.systemhost.net>
In-Reply-To: <E1GE5bm-0000ol-JH at stiedprstage1.ietf.org>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Last Call: 'Requirements for Multicast in L3
	Provider-Provisioned VPNs' to Informational RFC
	(draft-ietf-l3vpn-ppvpn-mcast-reqts)
Thread-Index: AcbC72gJWuq68q3vToylVxTBbFbfWQC38eig
From: <benjamin.niven-jenkins at bt.com>
To: <ietf at ietf.org>
X-OriginalArrivalTime: 22 Aug 2006 09:48:34.0886 (UTC)
	FILETIME=[2278F660:01C6C5D0]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 868af33ea4044bf08ad1008f65bebaaf
X-Mailman-Approved-At: Mon, 28 Aug 2006 08:33:35 -0400
Cc: thomas.morin at francetelecom.com
Subject: RE: Last Call: 'Requirements for Multicast in L3
	Provider-Provisioned VPNs' to Informational RFC
	(draft-ietf-l3vpn-ppvpn-mcast-reqts)
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Errors-To: ietf-bounces at ietf.org

This is a multi-part message in MIME format.

I support draft-ietf-l3vpn-ppvpn-mcast-reqts-08 becoming an
Informational RFC.  I have read the draft and have attached a number of
editorial changes/corrections as an rtf file with change tracking turned
on.

In addition I belive there are two places in the text that need further
correction:

Section 5.2.10 "with proper articulation" does the author really mean
articulation?  I think 'alignment' is a more appropriate term.

Section 5.2.11 "Most notably a solution supporting only a subset of
those requirements SHOULD be designed".  Which requirements are being
referred to by 'those requirements'?  If it the requirements in the
draft itself then I suggest the sentence is reworded to "most notably a
solution supporting only a subset of the requirements in this document
SHOULD be designed"

Thanks
Ben

-- 
Ben Niven-Jenkins
Network Architect, BT Exact
  
E-mail: benjamin.niven-jenkins at bt.com 
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827

The IESG <mailto:iesg-secretary at ietf.org> wrote:
> The IESG has received a request from the Layer 3 Virtual
> Private Networks WG to consider the following document:
> 
> - 'Requirements for Multicast in L3 Provider-Provisioned VPNs '
>    <draft-ietf-l3vpn-ppvpn-mcast-reqts-08.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action.  Please send any
> comments to the iesg at ietf.org or ietf at ietf.org mailing lists
> by 2006-09-01.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ppvpn-mca
> st-reqts-08.txt

Attachment: draft-ietf-l3vpn-ppvpn-mcast-reqts-08_nivenjb.rtf
Description: draft-ietf-l3vpn-ppvpn-mcast-reqts-08_nivenjb.rtf

Attachment: draft-ietf-l3vpn-ppvpn-mcast-reqts-08_nivenjb.rtf
Description: draft-ietf-l3vpn-ppvpn-mcast-reqts-08_nivenjb.rtf

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf