Subject: RE: I-D ACTION:draft-ietf-l2vpn-requirements-07.txt

From: <[email-masked]>
Date: Tue, 22 Aug 2006 16:12:11 +0100

Colleagues,

I have reviewed draft-ietf-l2vpn-requirements-07 and have attached a rtf
copy with change tracking enabled which highlights various editorial
corrections.

In addition I have a few comments:

Section 5.1.  "L2VPN protocols SHOULD NOT interfere with existing Layer
2 protocols and standards of the Layer 2 network". What is meant by "and
standards of the Layer 2 network"?

Section 6.3 ("A customer application SHOULD experience consistent QoS
independent of the access network technology used at different sites
connected to the same L2VPN") seems to contradict Section 6.6.1 ("The
capacity and QoS achievable MAY be dependent on the specific access
technology in use").

Is the correct intepretation of these conflicting requirements that one
should strive to provide consistent QoS regardless of access network
technology but that this goal may not be achievable in all cases?

Section 7.6, fourth paragraph. Is the should supposed to be a SHOULD?
Also, I find the sentence "it should support a configurable option to
support one or more of the following" confusing.  Surely a solution
should support all the options where each option can be independently
turned on/off by configuration?

Section 7.6, last paragraph. Why is configuration of the security
methods restricted to only the case where L2VPN data traffic is carried
over IP?

Thanks
Ben

-- 
Ben Niven-Jenkins
Network Architect, BT Exact
  
E-mail: [email-masked] 
Office: +44 (0)1473 648225
Mobile: +44 (0)7918 077205
   Fax: +44 (0)1332 578827

[email-masked] <mailto:[email-masked]> wrote:
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the Layer 2 Virtual Private
> Networks Working Group of the IETF.
> 
> 	Title		: Service Requirements for Layer 2
> Provider Provisioned Virtual Private Networks
> 	Author(s)	: W. Augustyn, Y. Serbest
> 	Filename	: draft-ietf-l2vpn-requirements-07.txt
> 	Pages		: 26
> 	Date		: 2006-6-19
> 
> This document provides requirements for Layer 2 Provider
> Provisioned Virtual Private Networks (L2VPNs).  It first
> provides taxonomy and terminology and states generic and
> general service requirements.  It covers point-to-point VPNs
> referred to as Virtual Private Wire Service (VPWS), as well
> as multipoint-to-multipoint VPNs also known as Virtual
> Private LAN Service (VPLS).  Detailed requirements are
> expressed from a customer as well as a service provider perspective.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-requireme
> nts-07.txt 
> 
> To remove yourself from the I-D Announcement list, send a
> message to [email-masked] with the word
> unsubscribe in the body of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login
> with the username "anonymous" and a password of your e-mail
> address. After logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-l2vpn-requirements-07.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	[email-masked].
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-l2vpn-requirements-07.txt".
> 
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.