From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [Fwd: [Fwd: Re: draft-ietf-pwe3-arch-07.txt editorials]]
Date: Fri, 03 Dec 2004 12:58:48 +0000
Lines: 248
References: <418F8D35.3090308@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, pwe3 <pwe3@ietf.org>,
	"'danny@tcb.net'" <danny@tcb.net>
X-From: pwe3-bounces@ietf.org Fri Dec 03 15:35:51 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Stewart Bryant <stbryant@cisco.com>, RFC Editor <rfc-editor@rfc-editor.org>
In-Reply-To: <418F8D35.3090308@cisco.com>
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

In addition to the changes below already sent to you (attached)
Please can you make the following additional change:

In Section 6.1 Multiplexing - last paragraph

Please replace the following text:

"When a MPLS label is used as a PW Demultiplexer setting of the TTL
value [RFC3032] in the PW label is application specific, however in a
strict point to point application the TTL should be set to 2."

With the following new text:

"When an MPLS label is used as a PW Demultiplexer, setting of the TTL
value [RFC3032] in the PW label stack entry is application specific."

Reason for change
=================

The use of TTL=2 breaks PW stitching.

This is because typical MPLS forwarding hardware will decrement the TTL
in the PW multiplexing label at the stitching point and cause the packet
to become hop expired before reaching the CE-bound PE, thus preventing a
PW packet being delivered over a stitched PW.

Note that the TTL=2 text was a "should" and therefore a recommendation
rather than a requirement.


Stewart Bryant wrote:

> 
> Please make these edit changes to draft-ietf-pwe3-arch-07.txt
> 
> Note that edit (1) removes the reference that is blocking
> publication.
> 
> - Stewart
> 
> 
> 
> 
> -------- Original Message --------
> Subject: [Fwd: Re: draft-ietf-pwe3-arch-07.txt editorials]
> Date: Fri, 22 Oct 2004 10:26:01 +0100
> From: Stewart Bryant <stbryant@cisco.com>
> To: pwe3 <pwe3@ietf.org>
> 
> I propose that we send the following editorial requests to
> the RFC editor.
> 
> Note that the first change removes an important gate
> because now the only gate is L2TPv3 which is in the
> RFC-editor's queue with no gate.
> 
> - Stewart
> 
> Stewart Bryant wrote:
> 
>>
>> The following editorial changes need to be made to
>> <draft-ietf-pwe3-arch-07.txt>
>>
>> Note that the first change removes a reference that is
>> gating the draft and hence requires a change to the
>> status in the RFC editors queue.
>>
>> --------------------------------------------------
>>
>> 1)The reference [FRAG] should be deleted from
>> the Normative References
>>
>> REASON
>>
>> [FRAG] was a normative reference in section 5.4.3.
>> "PW over MPLS Generic Control Word" in the -06
>> version of the draft. This section was removed
>> and placed in a new draft. There was no other
>> reference to [FRAG] in the text and so this
>> reference should have also been removed.
>>
>> ---------------------------------------------------
>>
>> 2) In the following text "the associated PWs" should
>> be replaced by "the PW"
>>
>> "7.3.1.  Pseudo-wire Up/Down Notification
>>
>>   If a native service REQUIRES bi-directional connectivity, the
>>   corresponding emulated service can only be signaled as being up when
>>   the associated PWs, and PSN tunnels if any, are functional in both
>>   directions. "
>>
>> Also REQUIRES should be lower case.
>>
>> The text should then read
>>
>> "7.3.1.  Pseudo-wire Up/Down Notification
>>
>>   If a native service requires bi-directional connectivity, the
>>   corresponding emulated service can only be signaled as being up when
>>   the PW, and PSN tunnels if any, are functional in both
>>   directions. "
>>
>>
>> REASON
>> ------
>>
>> PWs are bi-directional and therefore, there is only one PW
>> that must be up.
>>
>> Note that the equivalent text in the requirements draft:
>>
>> "5.1.  Setup and Teardown of Pseudo-Wires
>> <snip>
>>   If a native circuit is bi-directional, the corresponding emulated
>>   circuit can be signaled "Up" only when the associated PW and PSN
>>   tunnels in both directions are functional."
>>
>> is correct and the change makes the two drafts
>> consistent.
>>
>> -----------------------------------------------------
>> 3) At the end of 5.4.3. PW-IP Packet Discrimination
>>
>> there is a spurious ".sp" which needs to be deleted
>>
>> -----------------------------------------------------
>>
>> 4) In "1.4  Terminology" the following text should
>> be removed:
>>
>>   PWE3 Payload Type    A identifier used to distinguish between
>>   Identifier           an MPLS IP payload and a CW that is not
>>   (PWE3-PID)           ECMP safe.
>>
>> REASON
>> ------
>> This term is no longer used by PWE3.
>>
>> -----------------------------------------------------
>>
>> 5) In "5.4.3. PW-IP Packet Discrimination" delete the
>> line
>>
>>   The use of this field for PWs is work in progress.
>>
>> REASON
>> ------
>> This work has progressed since -07 was sent to the IESG.
>> Text is cleaner without the line and no value is lost.
>>
>>
>> ------------------------------------------------------
>> 6) From the "Normative References" section the
>> following references should be removed as they are
>> not used:
>>
>> [RFC791]
>> [RFC1883]
>> [RFC1902]
>> [RFC2119]
>> [RFC3031]
>>
>> REASON
>> ------
>> Not referenced by the text
>>
>> ------------------------------------------------------
>>
>> 7) All references to RFC2558 should be replaced by
>> references to RFC3592
>>
>> This occur in Fig 16 and in the Normative references
>> which should now include the following definition
>> for RFC3592:
>>
>> [RFC3592]   K. Tesink, "Definitions of Managed Objects for the
>> Synchronous Optical Network/Synchronous Digital Hierarchy
>> (SONET/SDH) Interface Type", RFC3592, September 2003.
>>
>> REASON
>> ------
>> RFC2558 has been obsoleted by RFC3592
>>
>> -------------------------------------------------------
>>
>> 8) All references to [LDPMIB] should be replaced by
>> [RFC3815]
>>
>> In the informative references the reference should be
>>
>> [RFC3815]   Cucchiara, J., Sjostrand, H., and Luciani, J.,
>>            "Definitions of Managed Objects for the Multiprotocol
>>            Label Switching, Label Distribution Protocol (LDP)",
>>            RFC-3815, June 2004
>>
>> REASON
>> ------
>> This Internet-Draft was published as a Proposed Standard, RFC 3815
>> (http://www.ietf.org/rfc/rfc3815.txt), on 2004-6-22.
>>
>> The name of the internet-draft was draft-ietf-mpls-ldp-mib-14.txt
>>
>> --------------------------------------------------------
>>
>> 9) All references to [LSRMIB} should be changed to [RFC3813]
>>
>> In the informative references the reference should be
>>
>> [RFC3813] Srinivasan, C., Viswanathan, A., Nadeau, T.
>>          "Multiprotocol Label Switching (MPLS) Label
>>          Switching Router (LSR) Management Information
>>          Base (MIB)", RFC-3813, June 2004
>>
>> REASON
>> ------
>> This Internet-Draft was published as a Proposed Standard, RFC 3813
>> (http://www.ietf.org/rfc/rfc3813.txt), on 2004-6-22.
>>
>> The name of the internet-draft was draft-ietf-mpls-lsr-mib-14.txt
>>
>> -------------------------------------------------------
>>
>> 10) All references to [TEMIB] should be changed to [RFC3812]
>>
>> In the informative references the reference should be
>>
>> [RFC3812] Srinivasan, C., Viswanathan, A., Nadeau, T.
>>          "Multiprotocol Label Switching (MPLS) Traffic
>>          Engineering (TE) Management Information Base (MIB)",
>>          RFC-3812, June 2004.
>>
>> REASON
>> -------
>> This Internet-Draft was published as a Proposed Standard, RFC 3812
>> (http://www.ietf.org/rfc/rfc3812.txt), on 2004-6-22.
>>
>> The name of the internet-draft was draft-ietf-mpls-te-mib-14.txt
>>
>>
> 
> 
> 
> 
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: CEP-09 - RE: PWE3 Draft Minutes - IETF 61
Date: Wed, 8 Dec 2004 14:56:05 -0800
Lines: 492
References: <3E58C9BD-3B6E-11D9-BEAB-000393D54EA6@tcb.net>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: 'David Zelig' <Davidz@corrigent.com>
X-From: pwe3-bounces@ietf.org Thu Dec 09 00:19:06 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Danny McPherson'" <danny@tcb.net>, "'pwe3'" <pwe3@ietf.org>,
	"Stewart Bryant" <stbryant@cisco.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <3E58C9BD-3B6E-11D9-BEAB-000393D54EA6@tcb.net>
X-Scan-Signature: 4de5d7f989d6c039c8b887f1940f36ab
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Danny,

> Then finish the following encaps as they become available
> <draft-ietf-pwe3-frame-relay-03.txt>
> <draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
> <draft-ietf-pwe3-sonet-09.txt>

Draft-ietf-pwe3-sonet-09 has been submitted in August 2004 and is
available since then. It includes resolution to all comments received
via the mailing list after last call. I don't see anything that needs
finishing here.

I suggest the plan be to get the TDM requirements to IESG and following
that put the SONET draft on IESG queue. 

Thanks
Ron


> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Danny McPherson
> Sent: Saturday, November 20, 2004 7:34 PM
> To: pwe3
> Subject: [PWE3] PWE3 Draft Minutes - IETF 61
> 
> 
> 
> Folks,
> Please send me comments and corrections ASAP.
> 
> Thanks!
> 
> -danny
> 
> [snip]
> 
> 1530-1730 Afternoon Session II; Lincoln East
> 
> Administrivia
> -------------
> 
> 
> Chairs: Danny McPherson & Stewart Bryant
> Minutes: Matthew Bocci
> Slides are available on pwe3.tcb.net
> 
> Charter & Draft Status - Stewart Bryant & Danny McPherson
> ---------------------------------------------------------
> 
> Working on updating charter with ADs. Danny to send email
>   to list with prposed updated and goals and milestones.
> 
> Draft status: Stewart
> 
> Dependencies:
> Lots of dependencies between drafts. Cannot become RFCs until
>   dependencies become RFCs. Very important to get this right.
>   Draft text may change if dependency text changes.
> 
> Stewart carried out a dependency analysis: this is shown
>   and looks very complex.
> 
> This will drive order in which we send documents to
>   RFC editor.
> 
> Concerns: Not all normative references are really
>   normative. Authors need to double check this.  Also
>   need to make sure all things that should be normative
>   are called out as such.  Need to check for
>   informative refs and docs with no normative
>   references.
> 
> Base requirements now an RFC.
> 
> Architecture: list of dependencies, but one may not be
>   correct. Edits sent to the list. Now in editors queue.
>   Waiting for fragmentation and L2TP.  This will be RFC.
> 
> Fragmentation: needs an updated. Encap refs can be
>   moved to control word references.
> Andy Malis: Refs to arch can also be changed to refs
>   to CW.
> Stewart: not sure this is allowed as arch is
>   informational.
> 
> Arch needs frag, needs control, and control doesn't
>   have dependencies.
> 
> Luca Martini: Architecture doc should be an informative
>   reference becasue you define CW in architecture.
> 
> Stewart: Fragmentation called up 2 bits in CW.
> Yakov Stein: CW has to be standards track because
>   of 1st 4 bits
> 
> Luca Martini: Every documents defines the CW bits
>   that it uses. CW document is the generic template.
> 
> Mark Townsley: would be preferable if description
>   was all in one place.
> 
> Yakov Stein: important to keep things the way they
>   are now for expediency
> 
> Eric Rosen: will confise the IESG
> 
> Control Word Draft: Most refs to arch refer to sec
>   5 and could be deleted. These could be changed to
>   arch.   Will respin and send up.
> 
> IANA: This is in last call and will be sent out
>   as soon as this is completed. Needed to set up the
>   registries. Also lots of requests to stabalise code
>   points.
> 
> 
> Control : This is one of the most strategic docs.
>   Past last call, but keeps getting minor change
>   requests. This is an urgent gating draft. Need to
>   take a hard line on this.
> 
> Luca Martini: Also some editorial nits that need
>   to be fixed.
> 
> Stewart: as long as protocol works, need to draw
>   a line in the sand.
> 
> ATM and Ethernet: Had 1st go of AD review. A
>   few edits to fix.
> 
> Thomas: very close to last call.
> 
> TDM Reqs in Thomas' queue
> 
> SONET needs TDM requirements to get AD review
>   before progressing.
> 
> SATOP sent to Thomas, but want to resolve UDP
>   issues first.
> 
> CESoPSN is informational, but want to resolve
>   UDP situation too.
> 
> HDLC encap: Needs a respin to fix refs.
>   Completed last call.
> 
> Frame Relay: Needs some TLC. A get well package
>   has been agreed, and should see a new rev
>   shortly. Style out of step with rest of
>   document set. terms need fixing.
> 
> Yakov Stein: Titles of encap drafts could be
>   standardised or made more consistent.
> 
> VCCV: Pressure to move this on. It went to
>   last call. Dave Allen's comments have not yet
>   been resolved: should be in rev 04, but this
>   has not been published yet.  Needs a serious
>   edit pass, and should be last called. Depends
>   on BFD and LSP-ping.
> 
> MIBs: these have a hge cross dependency list.
>   Need to make sure procedures are published
>   before.
> 
> FCS retention: Has standard encap dependencies.
>   Not in last call yet.
> 
> Andy Malis: it is ready for last call.
> 
> Cell transparent mode ready too.
> Stewart:
> 
> TDMoIP: Need to resolve UDP issue. Appendix
>   depends on VCCV. Waiting for comments on 2
>   OAM issues.
> 
> OAM messag mapping: Big dependencies, so wait
>   for others to get out of the way.
> 
> Plan:
> 1. Get -iana-allocation- to IESG
> 2. Finish -pwe3-cw- and send to IESG
> 3. Edit -control-protocol- to sort out refs
>    and send to IESG
> 4. Edit ?fragmentation- and then send to IESG
> At this point we have the platform needed to
>    progress the encap drafts
> 5) -ethernet-encap-
> 6) -atm-encap-
> Get TDM requirements to IESG, then the TDM encaps
> 7) -tdm-requirements-
> 8) -satop-
> 9) -cesopsn
> Then finish the following encaps as they become available
> <draft-ietf-pwe3-frame-relay-03.txt>
> <draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
> <draft-ietf-pwe3-sonet-09.txt>
> 
> When we have made progress on the above we will
>   promote the other work to the priority list
> 
> 
> Architecture draft is in editors queue. Waiting on
>   frag and L2TP. CW dtaft will be standard. Arch
>   will be informational.
> 
> Yakov Stein: why is CW standards track, if it is
>   not refered to as normative in other docs.
> 
> Luca Martini; Titles are not consistent. Most say
>   MPLS/IP, some say just MPLS.... Want comments on
>   changing all of the titles and making them
>   consistent.
> 
> Danny: take to list.
> 
> Mustapha: is CW is informational, why not just
>   merge back to the architecture draft.
> 
> Danny agrees that this is an issue that needs
>   to be addressed.  Will take offline.
> 
> 
> 
> PW CW - Stewart & Danny
> -----------------------
> http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
> 
> 
> There was lots of work after last IETF. Introduced associated
>   channel concept. Only use of 001 encapsualtion is for associated
>   channel for OAM traffic. This needs a formal definition for
>   associated channel. Suggestions to the list on this. Other
>   format ID values are available for additional purposes.
> 
> Yakov Stein: word channel clashes with the use in the
>   architecture draft Stewart: propose some text to the
>   mailing list.
> 
> Channel type will have its own registry. Plan is to grandfather
>   VCCV value (21). Some errors in the text around IANA
>   assignment.
> 
> 
> 
> UDP Statement to ITU - Stewart
> ------------------------------
> 
> This is one of the most discussed issues. TDM encaps are
>   being pursued in SG13 as well. UDP encaps are only used by
>   low speed TDM.  IETF documents are vague on use of UDP.
>   Need to resolve this before we can go forward. The ITU
>   started to talk about introducing an expected mechanism
>   for handling the ports. 5 techniques proposed in
>   liaison. Extensive comment on this to the list. Unable
>   to reach consensus. Statement proopsed to the list.
>   Essentially says PWE3 deals with L2TP, and MPLS
>   tunnelled over IP. Unable to reach consensus on whether
>   we need a 3rd method, so unable to give advice to
>   ITU on where to go next. However, are willing to listen
>   to proposals on how to carry PW over UDP, but anyway
>   will need to consider issues such as congestion,
>   security, and specific application.
> 
> 
> UDP Encapsulation - Yaakov Stein
> --------------------------------
> 
> Service provider model is presented. Emulation is PE to
>   PE. IWF is located in the PE. AC is natve service.  Encap
>   sits at the PE. Becomes MPLS at the PE. However, another
>   model is that the iwf is at the CE. The AC does not
>   run the native circuit. 3 possibilities:
> 
> - MPLS AC
> - UDP/IP AC
> - other AC possibilities (L2TP, MPLS over IP, native
>     service over IP using GRE, etc)
> 
> Lively thread on the list. Over 50 emails from 16 participants.
> Advantages: UDP/IP familiar to customer base, PW label as UDP
>   port no. reduces overhead, already extensively deployed for TDM PWs,
>   reuse of AVT protocols, simplify NAT traversal.
> 
> Disadvantages: had to provide QoS without c/o pt-pt trail.
>   Cannot be layer network above UDP. UDP doesn't scale, not
>   enough port numbers and increases NAT/firewall state. Need
>   protocol for UDP port signalling. UDP checksum needs to be
>   calculated. Why a new PW type at a late stage? Security
>   and congestion control
> 
> Other comments: need to reply to ITU liaison, PWE charter
>   aimed at operators, not enterprise customers, wrong, but
>   how to stop enterprise using it, no consensus, should
>   divert to AVT, but CE-CE PWs not in AVT charter, UDP
>   OK for VoIP since adapts an application, some comments
>   seem to rule out MPLS
> 
> Presents an rebuttal:
> - QoS similar to LDP based MPLS or L2TP
> - Enterprises don't need large number of UDP ports
> - Scales better than VoIP today
> - can use manual port provisioning
> - UDP checksum can simply be set to 0
> - PW type has been in the charter from day 1
> - Security: LDP and L2TP protocols are similarly unsafe
> - Congestion similar to L2TP
> 
> Proposal:
> Explicitly limit UDP/IP to enterprises (CE-CE case)
> - only allow manual provisioning
> - enterprise responsible to security, congestion avoidance
> - MPLS should be used if large numberof PWs needed.
> 
> Stewart: would like comments to help draft ITU response
> 
> Sahsa: Agrees that there is no sense in developing a
>   control protocol for UDP PWs. Don't understand what
>   enterprise PWs means.  If it connects to a class 5
>   switch, what is it? ALso not sure that admission
>   control should be up to the customer.
> 
> Yakov Stein: On congestion avoidance, that link that
>   is UDP will sufer. SP can discard excess traffic.
>   The access PW is the point from the CE to the core
>   network.
> 
> Sasha: Confused. Are UDP PWs aonly a part of Multi
>   hop PWs?
> 
> Yakov: yes
> 
> Sasha: don't know what to do with MH PWs
> 
> Eric Rosen: is is too late to remove this TDM from
>   charter entirely?
> 
> Stewart: many people want to work on this
> 
> Eric: if you want to get this though, stop drawing
>   attention to the problems e.g. NAT, signalling, how
>   you do multiplexing, seems to need to be manually
>   configured to interoperate. Solution is to take UDP
>   out and leave up to SG13, or only have manual
>   configuration. IESG may still notice this. Better
>   to leave this in the hands of the ITU.
> 
> Luca Martini: Be careful and write a good security
>   section. You are mixing control protocol with data
>   planes. We are very exposed here.
> 
> Danny: We are trying to define protocols, not how
>   and where they are deployed. A lot of concern on
>   how to scope enterprise vs. service provider here.
>   We need to assume the protocols defined here will
>   be deployed in the Internet.
> 
> 
> Stewart: can either:
> - not respond
> - say unable to reach consesus
> - say we recognise that there are limited cases where
> UDP would be appropriate, supported by manual
>   configuration
> 
> Scott Bradner: You have about a week to honor
>   tradition and not respond, but it would be
>   better to send them a response
> 
> Thomas Narten: be pragmatic and reasonable. If we
>   don't respond, what will happen?
> Stewart: we have an opinion as to how UDP is correctly
>   operated. We have a duty of care.
> Yakov Stein: reason this was sent was that this was
>   going to be progressed in SG13. If we cannot reach
>   consensus, SG13 wil l do what it wants.
> Scott Bradner: ITU is trying to work with us. We
>   should cooperate going forward, even if it is to
>   say that we don't have an opinion. We must not
>   ignore them.
> Thomas Narten: AGrees. We can give our thoughts.
>   We may not like what they want to do, but ghould
>   explain why.
> Mark Townsley: could say PWE3 doesn't care. Is there
>   some work to do at an IAB level on what you do with UDP?
> 
> Craig White: We do need to send a fairly strong
>   statement similar to what eric expressed, but
>   need to be cognisant of the fact that they have
>   implementations. Need to say that on the Internet,
>   this is not an appropriate use, but may be
>   appropriate in a private network. be aware of
>   issues if it gets connected to Internet at any
>   time.
> Scott Bradner: What is magic about UDP in this
>   context?
> Stewart: this was not an issue until it was noticed
>   that we needed a port assignment protocol
> Scott Bradner: This working group was formed with
>   the assumption of UDP and MPLS
> Craig: congestion avoidance problem with UDP
> Scott: no real difference
> Yakov Stein: ITU would be happy to hear that we only
>   want manual configuration.
> Luca Martini: We also have an implementation of this.
>   Bottom line is that a better design is L2TPv3 and
>   this should be used instead. IETF thinks this is
>   a better idea.
> Eric Rosen: 2 issues: signalling. Suggestion that
>   you could use LDP, with port numbers instead of
>   labels. DO you use source or destination port?
>   What about NATs? not sure we can come to
>   consensus, except you need to manually configure
>   it.
> 
> Stewart: We do not recommend UDP, but L2TP. If
>   you use UDP, you so manual config.
> 
> Yakov Stein: why?
> 
> Stewart: Responds saying we recommend that you
>   only do manual configuration of the ports.
> 
> Mark Townsley: ...and if you want to do
>   automatic configuration, use L2TPv3 Issue with
>   UDP is that it can cause problems for NATs. Some
>   of the arguments made on the list are significant.
> 
> Yakov Stein: why does RTP group get away with this?
> 
> Shasha: Neither MPLS nor L2TP are suitable for
>   NAT traversal. Could say: No signalling protocol,
>   should not be used in NAT environment. Agree
>   that there is substantially more VoIP and so
>   we could say that UDP already used for VoIP
>   sessions with operational success.
> 
> Mark Townsley: L2TPv3 deigned to run over UDP.
>   Every NAT knows how to do L2TPv3 as in RFC2661
> Thomas Narten: Liaison doesn't ask if it is a
>   good or a bad thing. It asks how to do port
>   number stuff. We should answer the question.
> 
> Stewart: Our advice is that this is only done
>   in a manually configured mode, and anything
>   more advanced should be made as a proposal
>   to the PWE3 group.
> 
> Yakov Stein: pick one and send it back already!
>   Pick manually configured, but use L2TPv3 for
>   signalled
> 
> Consensus around this. Propose to the mailing
>   list by Friday afternoon.
> 
> 
> 
> PW Multi-Hop Requirements - Luca Martini
> ----------------------------------------
> 
> Presents the outcome of the requirements team.
> 
> Last IETF was a discussion about PW stitching. Since
>   then, we had a long drawn out email thread. Concluded
>   we needed a requirement document.
> 
> Document not achieved by this IETF deadline.
> 
> Met face to face. We are regrouping, and trying to
>   produce a draft by the end of november
>   concentrating on requirements for this technology.
>   This will guide if we need to do any more protocol
>   work.
> 
> 
> Open Microphone
> ---------------
> 
> Luca Martini: What is the state of the rechartering?
> Danny: Will provide an update on the charter, goals
>   and milestones on the mailing list.
> 
> Meeting Adjourned
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Diego Caviglia" <Diego.Caviglia@marconi.com>
Subject: LDP Signalling for PWs
Date: Mon, 13 Dec 2004 10:29:23 +0100
Lines: 14
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-From: pwe3-bounces@ietf.org Mon Dec 13 10:50:45 2004
Return-path: <pwe3-bounces@ietf.org>
To: pwe3@ietf.org
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26,
	2003) at 13/12/2004 09:29:22
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi all,
              ID draft-ietf-pwe3-control-protocol-13 states that ...The PEs
will establish an LDP session using the Extended Discovery .." it is not
clear to me why I can't use basic discovery mechansim given that I have
e.g. an MPLS tunnel between the two PEs and thus a can tunnel Hello packets
between the LSP peers.

What am I missing?

Thanks.

Regards

Diego


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Gandhi, Upma" <Upma.Gandhi@networkgeneral.com>
Subject: RE: LDP Signalling for PWs
Date: Mon, 13 Dec 2004 05:49:43 -0800
Lines: 189
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3-bounces@ietf.org, pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Mon Dec 13 16:47:11 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] LDP Signalling for PWs
Thread-Index: AcThFvB4UYz8G5S3QFOsIHXcWDuakwAAy3oA
To: "Diego Caviglia" <Diego.Caviglia@marconi.com>
X-OriginalArrivalTime: 13 Dec 2004 13:49:57.0021 (UTC)
	FILETIME=[A19FA4D0:01C4E11A]
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 13 Dec 2004 10:44:39 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Even though after setting up of this tunnel, they seems to be adjacent
but other PE is still unaware of topology of other end.
   Can someone else put the light on this ?

Thanks & Regards
Upma

-----Original Message-----
From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]=20
Sent: Monday, December 13, 2004 6:52 PM
To: Gandhi, Upma
Cc: pwe3-bounces@ietf.org
Subject: RE: [PWE3] LDP Signalling for PWs


Seems that there is a misunderstanding.

w.r.t. the following picture

         |<-------------- Emulated Service ---------------->|
         |                                                  |
         |          |<------- Pseudo Wire ------>|          |
         |          |                            |          |
         |          |    |<-- PSN Tunnel -->|    |          |
         | PW End   V    V                  V    V  PW End  |
         V Service  +----+                  +----+  Service V
   +-----+    |     | =
PE1|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D| PE2|     |   =
 +-----+
   |     |----------|............PW1.............|----------|     |
   | CE1 |    |     |    |                  |    |     |    | CE2 |
   |     |----------|............PW2.............|----------|     |
   +-----+  ^ |     |    =
|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D|    |     | ^  =
+-----+
         ^  |       +----+                  +----+     | |  ^
         |  |   Provider Edge 1         Provider Edge 2  |  |
         |  |                                            |  |
   Customer |                                            | Customer
   Edge 1   |                                            | Edge 2
            |                                            |
            |                                            |
    Attachment Circuit (AC)                    Attachment Circuit (AC)
    native ethernet service                    native ethernet service

Supposing that the PSN Tunnel is already in place referring to the
set-up of the PW that must be done using LDP why I can't behave as the
twp PEs are diretly connected given that there is a tunnel between them?

Regards

Diego






"Gandhi, Upma" <Upma.Gandhi@networkgeneral.com> on 13/12/2004 14.16.12

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: LDP Signalling for PWs
Date: Mon, 13 Dec 2004 15:08:03 -0700
Organization: Cisco Systems
Lines: 39
References: <OFF6051414.23CBD140-ONC1256F69.0033C150@uk.marconicomms.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Mon Dec 13 23:21:21 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Diego Caviglia <Diego.Caviglia@marconi.com>
In-Reply-To: <OFF6051414.23CBD140-ONC1256F69.0033C150@uk.marconicomms.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Diego,

Extended discovery means that the UDP hello packets to port 646 will 
have a destination IP address that is the remote PE's address.
Basic discovery involves sending the UDP hello packets to port 646 to 
destination address 224.0.0.2 ( the all routers multicast address ).
Packets to address 224.0.0.2 will not travel any further then the 
immediate neighbors.
Normally there is not MPLS FEC for 224.0.0.2

Luca


Diego Caviglia wrote:

>Hi all,
>              ID draft-ietf-pwe3-control-protocol-13 states that ...The PEs
>will establish an LDP session using the Extended Discovery .." it is not
>clear to me why I can't use basic discovery mechansim given that I have
>e.g. an MPLS tunnel between the two PEs and thus a can tunnel Hello packets
>between the LSP peers.
>
>What am I missing?
>
>Thanks.
>
>Regards
>
>Diego
>
>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: LDP Signalling for PWs
Date: Mon, 13 Dec 2004 15:12:15 -0700
Organization: Cisco Systems
Lines: 223
References: <485C8799EA83DF4DAF2C1E78F8198D7328BD66@BNGEXMB01.corp.netgen.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Mon Dec 13 23:23:45 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: "Gandhi, Upma" <Upma.Gandhi@networkgeneral.com>
In-Reply-To: <485C8799EA83DF4DAF2C1E78F8198D7328BD66@BNGEXMB01.corp.netgen.local>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: e367d58950869b6582535ddf5a673488
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I'm not sure where to start ....
The tunnel is not an "all purpose tunnel". Only IP packets that match 
the specific FEC will be put into the tunnel.
So only packets directed to specific IP addresses will traverse the tunnel.
There is no "adjacency" between the two PE.

Luca

Gandhi, Upma wrote:

>Even though after setting up of this tunnel, they seems to be adjacent
>but other PE is still unaware of topology of other end.
>   Can someone else put the light on this ?
>
>Thanks & Regards
>Upma
>
>-----Original Message-----
>From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com] 
>Sent: Monday, December 13, 2004 6:52 PM
>To: Gandhi, Upma
>Cc: pwe3-bounces@ietf.org
>Subject: RE: [PWE3] LDP Signalling for PWs
>
>
>Seems that there is a misunderstanding.
>
>w.r.t. the following picture
>
>         |<-------------- Emulated Service ---------------->|
>         |                                                  |
>         |          |<------- Pseudo Wire ------>|          |
>         |          |                            |          |
>         |          |    |<-- PSN Tunnel -->|    |          |
>         | PW End   V    V                  V    V  PW End  |
>         V Service  +----+                  +----+  Service V
>   +-----+    |     | PE1|==================| PE2|     |    +-----+
>   |     |----------|............PW1.............|----------|     |
>   | CE1 |    |     |    |                  |    |     |    | CE2 |
>   |     |----------|............PW2.............|----------|     |
>   +-----+  ^ |     |    |==================|    |     | ^  +-----+
>         ^  |       +----+                  +----+     | |  ^
>         |  |   Provider Edge 1         Provider Edge 2  |  |
>         |  |                                            |  |
>   Customer |                                            | Customer
>   Edge 1   |                                            | Edge 2
>            |                                            |
>            |                                            |
>    Attachment Circuit (AC)                    Attachment Circuit (AC)
>    native ethernet service                    native ethernet service
>
>Supposing that the PSN Tunnel is already in place referring to the
>set-up of the PW that must be done using LDP why I can't behave as the
>twp PEs are diretly connected given that there is a tunnel between them?
>
>Regards
>
>Diego
>
>
>
>
>
>
>"Gandhi, Upma" <Upma.Gandhi@networkgeneral.com> on 13/12/2004 14.16.12
>
>To:    "Diego Caviglia" <Diego.Caviglia@marconi.com>
>cc:    <pwe3-bounces" pwe3-bounces@ietf.org"@smtpoutuk02.marconi.com>
>
>Subject:    RE: [PWE3] LDP Signalling for PWs
>
>
>Then there is a need to extend those tunneling technology i.e RSVP-TE or
>any other technology  to send Pwid/PW type mapping which is used in
>figuring out L2 technology/ or understanding L2 technology i.e ATM/FR
>for which PWE3 is a transportation method.
>   Without this mapping other PE won't be able to understand L2 beneth
>that.
>
>-----Original Message-----
>From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
>Sent: Monday, December 13, 2004 6:36 PM
>To: Gandhi, Upma
>Cc: pwe3-bounces" pwe3-bounces@ietf.org"@smtpoutuk02.marconi.com
>Subject: RE: [PWE3] LDP Signalling for PWs
>
>
>My understanding is that the MPLS tunnel can be set-up also using
>RSVP-TE moreover the tunnel can be every kind of tunnel, MPLS is just a
>possible implementation.
>
>Supposing that I have already in place a tunnel between two PEs and I
>want to set-up a session why I can't use basic discovery?  By means of
>the tunnel the two end-point are adjacent.
>
>Regards.
>
>Diego
>
>
>
>"Gandhi, Upma" <Upma.Gandhi@networkgeneral.com> on 13/12/2004 14.01.27
>
>To:    "Diego Caviglia" <Diego.Caviglia@marconi.com>
>cc:    "<pwe3-bounces" <pwe3-bounces@ietf.org>
>
>Subject:    RE: [PWE3] LDP Signalling for PWs
>
>
>But MPLS tunnel  would internally be using LDP Extended discovery method
>to create the MPLS tunnel (assuming that its not static MPLS
>tunnel) for the same reason of not being in same AS or same topology or
>different ISPs.
>
>
>
>-----Original Message-----
>From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
>Sent: Monday, December 13, 2004 6:08 PM
>To: Gandhi, Upma
>Cc: <pwe3-bounces
>Subject: RE: [PWE3] LDP Signalling for Pws
>
>
>Hi Ghandi,
>              thank you for your reply, but I think I didn't make myself
>clear.
>
>My question is why I have to use the LDP extended discovery procedure,
>that is designed for non adjacent peers?
>
>In my view, given that I have a tunnel (e.g. an MPLS tunnel), the two
>LDP peers can be viewed as adjacent and thus I can use basic discovery.
>
>Regards
>
>Diego
>
>
>
>"Gandhi, Upma" <Upma.Gandhi@networkgeneral.com> on 13/12/2004 12.46.17
>
>To:    "Diego Caviglia" <Diego.Caviglia@marconi.com>
>cc:    <pwe3-bounces@ietf.org>
>
>Subject:    RE: [PWE3] LDP Signalling for PWs
>
>
>Hello Diego,
>
>To support PWE3, LDP has been extended which helps in negotiating PW
>type which further helps in determining different L2.
>To transport L2 messages over PSN network, one extra layer of control
>word has been added and to properly interpret L2 message and so Control
>word  i.e ATM, ETHERNET, Frame Relay LDP has been extended for some TLV
>i.e Pwid/generalized PWid which is used to understand how L2 would be
>interpreted.
>  As far as some basic discovery mechanism is concerned, since these PE
>might not be directly connected or immediate peer or of same topology,
>
>There is need for some session management between them. Since LDP
>already support this, it is being extended , even RSVP-TE is also in
>consideration.
>
>Thanks & Regards
>Upma
>
>-----Original Message-----
>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
>Diego Caviglia
>Sent: Monday, December 13, 2004 2:59 PM
>To: pwe3@ietf.org
>Subject: [PWE3] LDP Signalling for PWs
>
>Hi all,
>              ID draft-ietf-pwe3-control-protocol-13 states that ...The
>PEs will establish an LDP session using the Extended Discovery .." it is
>not clear to me why I can't use basic discovery mechansim given that I
>have e.g. an MPLS tunnel between the two PEs and thus a can tunnel Hello
>packets between the LSP peers.
>
>What am I missing?
>
>Thanks.
>
>Regards
>
>Diego
>
>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: IANA document allocation
Date: Mon, 13 Dec 2004 15:19:45 -0700
Organization: Cisco Systems
Lines: 19
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'W. Mark Townsley'" <townsley@cisco.com>
X-From: pwe3-bounces@ietf.org Mon Dec 13 23:33:00 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

WG,

Thomas Narten, our sponsoring AD, has asked me to change the IANA 
allocation document to reflect only two kind of allocations:
IETF consensus , and Expert review.

This means that I would remove the first come first served ranges, and 
the vendor specific ranges that are currently defined in the documents.

My personal opinion is that this is a good change as , "the expert" , 
can probably still respond quickly ( as opposed to an IETF consensus 
process ), yet can make sure that there is a good clear description and 
application for the allocated values.

I would like to hear from the WG if there are any strong opinions about 
this change to the IANA allocation documents.

Thanks.
Luca


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Shah, Himanshu" <hshah@ciena.com>
Subject: RE: LDP Signalling for PWs
Date: Mon, 13 Dec 2004 17:41:52 -0500
Lines: 81
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Mon Dec 13 23:52:59 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
	<Diego.Caviglia@marconi.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

If you allow tunnel (lets say RSVP-TE based) to be 
a logical IP i/f, one could conceivably send 
regular LDP hello to discover the remote PE.

This would be no different than if the target 
LDP peer were to be on the direct link (adjacent).

However, in order to differentiate topology based
LDP (link hello) from PWE3 signaling LDP (targetted), you have to
set the LDP Hello with t-bit set and send it
on unicast LDP Peer ID.

Unless of course, you recognize the i/f as tunnel
and 
1) use the tunnel end-point address as the unicast
address
2) send targetted hello

then you achieve what you intended.

/himanshu



> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Monday, December 13, 2004 5:08 PM
> To: Diego Caviglia
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] LDP Signalling for PWs
> 
> 
> Diego,
> 
> Extended discovery means that the UDP hello packets to port 646 will 
> have a destination IP address that is the remote PE's address.
> Basic discovery involves sending the UDP hello packets to port 646 to 
> destination address 224.0.0.2 ( the all routers multicast address ).
> Packets to address 224.0.0.2 will not travel any further then the 
> immediate neighbors.
> Normally there is not MPLS FEC for 224.0.0.2
> 
> Luca
> 
> 
> Diego Caviglia wrote:
> 
> >Hi all,
> >              ID draft-ietf-pwe3-control-protocol-13 states 
> that ...The PEs
> >will establish an LDP session using the Extended Discovery 
> .." it is not
> >clear to me why I can't use basic discovery mechansim given 
> that I have
> >e.g. an MPLS tunnel between the two PEs and thus a can 
> tunnel Hello packets
> >between the LSP peers.
> >
> >What am I missing?
> >
> >Thanks.
> >
> >Regards
> >
> >Diego
> >
> >
> >
> >_______________________________________________
> >pwe3 mailing list
> >pwe3@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pwe3
> >
> >  
> >
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Diego Caviglia" <Diego.Caviglia@marconi.com>
Subject: RE: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 10:13:39 +0100
Lines: 102
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: pwe3 <pwe3@ietf.org>,
	"\"\"'Luca Martini'\" <lmartini\"" <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 10:27:05 2004
Return-path: <pwe3-bounces@ietf.org>
To: hshah@ciena.com
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26,
	2003) at 14/12/2004 09:14:14
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Shah,
              thank for your replay, I agree with you.

May be could be useful to state that in the LDP signalling draft.

What is the feeling of the list on that matter?

Diego



"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 11:21:51 +0000
Lines: 136
References: <OF933D5D70.D4CD148D-ONC1256F6A.00328BBB@uk.marconicomms.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: " <lmartini" <lmartini@cisco.com>, pwe3 <pwe3@ietf.org>, hshah@ciena.com
X-From: pwe3-bounces@ietf.org Tue Dec 14 12:27:01 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Diego Caviglia <Diego.Caviglia@marconi.com>
In-Reply-To: <OF933D5D70.D4CD148D-ONC1256F6A.00328BBB@uk.marconicomms.com>
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

We are really trying to get the control draft to RFC,
and therefore to restrict the changes, and that
means taking a hard line on anything except
protocol design errors.

This looks more like an applicability issue than a
correctness issue, and as perhaps we should
put it in an applicability draft?

- Stewart

Diego Caviglia wrote:
> Shah,
>               thank for your replay, I agree with you.
> 
> May be could be useful to state that in the LDP signalling draft.
> 
> What is the feeling of the list on that matter?
> 
> Diego
> 
> 
> 
> "Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> 
> To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
>        <Diego.Caviglia@marconi.com>
> cc:    pwe3@ietf.org
> 
> Subject:    RE: [PWE3] LDP Signalling for PWs
> 
> 
> If you allow tunnel (lets say RSVP-TE based) to be
> a logical IP i/f, one could conceivably send
> regular LDP hello to discover the remote PE.
> 
> This would be no different than if the target
> LDP peer were to be on the direct link (adjacent).
> 
> However, in order to differentiate topology based
> LDP (link hello) from PWE3 signaling LDP (targetted), you have to
> set the LDP Hello with t-bit set and send it
> on unicast LDP Peer ID.
> 
> Unless of course, you recognize the i/f as tunnel
> and
> 1) use the tunnel end-point address as the unicast
> address
> 2) send targetted hello
> 
> then you achieve what you intended.
> 
> /himanshu
> 
> 
> 
> 
>>-----Original Message-----
>>From: Luca Martini [mailto:lmartini@cisco.com]
>>Sent: Monday, December 13, 2004 5:08 PM
>>To: Diego Caviglia
>>Cc: pwe3@ietf.org
>>Subject: Re: [PWE3] LDP Signalling for PWs
>>
>>
>>Diego,
>>
>>Extended discovery means that the UDP hello packets to port 646 will
>>have a destination IP address that is the remote PE's address.
>>Basic discovery involves sending the UDP hello packets to port 646 to
>>destination address 224.0.0.2 ( the all routers multicast address ).
>>Packets to address 224.0.0.2 will not travel any further then the
>>immediate neighbors.
>>Normally there is not MPLS FEC for 224.0.0.2
>>
>>Luca
>>
>>
>>Diego Caviglia wrote:
>>
>>
>>>Hi all,
>>>             ID draft-ietf-pwe3-control-protocol-13 states
>>
>>that ...The PEs
>>
>>>will establish an LDP session using the Extended Discovery
>>
>>.." it is not
>>
>>>clear to me why I can't use basic discovery mechansim given
>>
>>that I have
>>
>>>e.g. an MPLS tunnel between the two PEs and thus a can
>>
>>tunnel Hello packets
>>
>>>between the LSP peers.
>>>
>>>What am I missing?
>>>
>>>Thanks.
>>>
>>>Regards
>>>
>>>Diego
>>>
>>>
>>>
>>>_______________________________________________
>>>pwe3 mailing list
>>>pwe3@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/pwe3
>>>
>>>
>>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Diego Caviglia" <Diego.Caviglia@marconi.com>
Subject: Re: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 12:30:27 +0100
Lines: 160
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: lmartini@cisco.com, "pwe3 <pwe3" <pwe3@ietf.org>, hshah <hshah@ciena.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 12:37:54 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Stewart Bryant <stbryant" <stbryant@cisco.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26,
	2003) at 14/12/2004 11:30:28
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Stewart,
                   no problem from my side I see that the ID is number 13
and thus is better to restrict the modify.

Purpose of my proposal is to state somewhere, an applicability ID could be
good, that is possible, using the procedure Shah depicted in his mail, to
use a tunnel to transport the Hello messages.

Regards

Diego



Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 09:36:07 -0700
Organization: Cisco Systems
Lines: 200
References: <OF0B3DF827.699BA57A-ONC1256F6A.003EF67E@uk.marconicomms.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3 <pwe3" <pwe3@ietf.org>, hshah <hshah@ciena.com>,
	"Stewart Bryant <stbryant" <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 17:50:13 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Diego Caviglia <Diego.Caviglia@marconi.com>
In-Reply-To: <OF0B3DF827.699BA57A-ONC1256F6A.003EF67E@uk.marconicomms.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Diego,

What Himanshu described still involves putting multicast into the rsvp 
tunnel. I do not believe that this is the practice today.
It can be done , but there is no significant advantage to just using the 
extended discovery mechanism. You should keep in mind that normal 
behavior is to actually put all the LDP packets into the MPLS LSP 
between the 2 PEs. ( regardless if it is RSVP sin galled or LDP signaled ).

Luca


Diego Caviglia wrote:

>Stewart,
>                   no problem from my side I see that the ID is number 13
>and thus is better to restrict the modify.
>
>Purpose of my proposal is to state somewhere, an applicability ID could be
>good, that is possible, using the procedure Shah depicted in his mail, to
>use a tunnel to transport the Hello messages.
>
>Regards
>
>Diego
>
>
>
>Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
>
>To:    Diego Caviglia <Diego.Caviglia@marconi.com>
>cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
>       <lmartini@cisco.com>
>
>Subject:    Re: [PWE3] LDP Signalling for PWs
>
>
>We are really trying to get the control draft to RFC,
>and therefore to restrict the changes, and that
>means taking a hard line on anything except
>protocol design errors.
>
>This looks more like an applicability issue than a
>correctness issue, and as perhaps we should
>put it in an applicability draft?
>
>- Stewart
>
>Diego Caviglia wrote:
>  
>
>>Shah,
>>              thank for your replay, I agree with you.
>>
>>May be could be useful to state that in the LDP signalling draft.
>>
>>What is the feeling of the list on that matter?
>>
>>Diego
>>
>>
>>
>>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
>>
>>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
>>       <Diego.Caviglia@marconi.com>
>>cc:    pwe3@ietf.org
>>
>>Subject:    RE: [PWE3] LDP Signalling for PWs
>>
>>
>>If you allow tunnel (lets say RSVP-TE based) to be
>>a logical IP i/f, one could conceivably send
>>regular LDP hello to discover the remote PE.
>>
>>This would be no different than if the target
>>LDP peer were to be on the direct link (adjacent).
>>
>>However, in order to differentiate topology based
>>LDP (link hello) from PWE3 signaling LDP (targetted), you have to
>>set the LDP Hello with t-bit set and send it
>>on unicast LDP Peer ID.
>>
>>Unless of course, you recognize the i/f as tunnel
>>and
>>1) use the tunnel end-point address as the unicast
>>address
>>2) send targetted hello
>>
>>then you achieve what you intended.
>>
>>/himanshu
>>
>>
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Luca Martini [mailto:lmartini@cisco.com]
>>>Sent: Monday, December 13, 2004 5:08 PM
>>>To: Diego Caviglia
>>>Cc: pwe3@ietf.org
>>>Subject: Re: [PWE3] LDP Signalling for PWs
>>>
>>>
>>>Diego,
>>>
>>>Extended discovery means that the UDP hello packets to port 646 will
>>>have a destination IP address that is the remote PE's address.
>>>Basic discovery involves sending the UDP hello packets to port 646 to
>>>destination address 224.0.0.2 ( the all routers multicast address ).
>>>Packets to address 224.0.0.2 will not travel any further then the
>>>immediate neighbors.
>>>Normally there is not MPLS FEC for 224.0.0.2
>>>
>>>Luca
>>>
>>>
>>>Diego Caviglia wrote:
>>>
>>>
>>>      
>>>
>>>>Hi all,
>>>>            ID draft-ietf-pwe3-control-protocol-13 states
>>>>        
>>>>
>>>that ...The PEs
>>>
>>>      
>>>
>>>>will establish an LDP session using the Extended Discovery
>>>>        
>>>>
>>>.." it is not
>>>
>>>      
>>>
>>>>clear to me why I can't use basic discovery mechansim given
>>>>        
>>>>
>>>that I have
>>>
>>>      
>>>
>>>>e.g. an MPLS tunnel between the two PEs and thus a can
>>>>        
>>>>
>>>tunnel Hello packets
>>>
>>>      
>>>
>>>>between the LSP peers.
>>>>
>>>>What am I missing?
>>>>
>>>>Thanks.
>>>>
>>>>Regards
>>>>
>>>>Diego
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>pwe3 mailing list
>>>>pwe3@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/pwe3
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>pwe3 mailing list
>>>pwe3@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/pwe3
>>>
>>>      
>>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
>>
>>    
>>
>
>
>
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Shah, Himanshu" <hshah@ciena.com>
Subject: RE: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 12:08:53 -0500
Lines: 241
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: "pwe3 <pwe3" <pwe3@ietf.org>,
	"Stewart Bryant <stbryant" <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 18:33:11 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
	<Diego.Caviglia@marconi.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Nope.

I meant that router intelligently recognizes that
logical IP interface is a "tunnel" and hence for
targetted LDP purposes, send targetted hello to 
unicast IP address (which is the tunnel endpoint's
IP address). 

So if you are doing, topology LDP, you would send
link hello (a way to have LDP work across RSVP-TE
cloud using this tunnel) and at the same time if you 
are doing PWE3 signaling, you would also send targetted 
hello for extended discovery (using unicast IP address).

Hope this clears up.

Either way, I don't think there is any need to change
pwe3-control draft, because this would either be
an implementation detail or a suggested possibility in
applicability draft as Stewart suggested.

/himanshu

> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Tuesday, December 14, 2004 11:36 AM
> To: Diego Caviglia
> Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> Subject: Re: [PWE3] LDP Signalling for PWs
> 
> 
> Diego,
> 
> What Himanshu described still involves putting multicast into 
> the rsvp 
> tunnel. I do not believe that this is the practice today.
> It can be done , but there is no significant advantage to 
> just using the 
> extended discovery mechanism. You should keep in mind that normal 
> behavior is to actually put all the LDP packets into the MPLS LSP 
> between the 2 PEs. ( regardless if it is RSVP sin galled or 
> LDP signaled ).
> 
> Luca
> 
> 
> Diego Caviglia wrote:
> 
> >Stewart,
> >                   no problem from my side I see that the ID 
> is number 13
> >and thus is better to restrict the modify.
> >
> >Purpose of my proposal is to state somewhere, an 
> applicability ID could be
> >good, that is possible, using the procedure Shah depicted in 
> his mail, to
> >use a tunnel to transport the Hello messages.
> >
> >Regards
> >
> >Diego
> >
> >
> >
> >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> >
> >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> >       <lmartini@cisco.com>
> >
> >Subject:    Re: [PWE3] LDP Signalling for PWs
> >
> >
> >We are really trying to get the control draft to RFC,
> >and therefore to restrict the changes, and that
> >means taking a hard line on anything except
> >protocol design errors.
> >
> >This looks more like an applicability issue than a
> >correctness issue, and as perhaps we should
> >put it in an applicability draft?
> >
> >- Stewart
> >
> >Diego Caviglia wrote:
> >  
> >
> >>Shah,
> >>              thank for your replay, I agree with you.
> >>
> >>May be could be useful to state that in the LDP signalling draft.
> >>
> >>What is the feeling of the list on that matter?
> >>
> >>Diego
> >>
> >>
> >>
> >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> >>
> >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> >>       <Diego.Caviglia@marconi.com>
> >>cc:    pwe3@ietf.org
> >>
> >>Subject:    RE: [PWE3] LDP Signalling for PWs
> >>
> >>
> >>If you allow tunnel (lets say RSVP-TE based) to be
> >>a logical IP i/f, one could conceivably send
> >>regular LDP hello to discover the remote PE.
> >>
> >>This would be no different than if the target
> >>LDP peer were to be on the direct link (adjacent).
> >>
> >>However, in order to differentiate topology based
> >>LDP (link hello) from PWE3 signaling LDP (targetted), you have to
> >>set the LDP Hello with t-bit set and send it
> >>on unicast LDP Peer ID.
> >>
> >>Unless of course, you recognize the i/f as tunnel
> >>and
> >>1) use the tunnel end-point address as the unicast
> >>address
> >>2) send targetted hello
> >>
> >>then you achieve what you intended.
> >>
> >>/himanshu
> >>
> >>
> >>
> >>
> >>    
> >>
> >>>-----Original Message-----
> >>>From: Luca Martini [mailto:lmartini@cisco.com]
> >>>Sent: Monday, December 13, 2004 5:08 PM
> >>>To: Diego Caviglia
> >>>Cc: pwe3@ietf.org
> >>>Subject: Re: [PWE3] LDP Signalling for PWs
> >>>
> >>>
> >>>Diego,
> >>>
> >>>Extended discovery means that the UDP hello packets to 
> port 646 will
> >>>have a destination IP address that is the remote PE's address.
> >>>Basic discovery involves sending the UDP hello packets to 
> port 646 to
> >>>destination address 224.0.0.2 ( the all routers multicast 
> address ).
> >>>Packets to address 224.0.0.2 will not travel any further then the
> >>>immediate neighbors.
> >>>Normally there is not MPLS FEC for 224.0.0.2
> >>>
> >>>Luca
> >>>
> >>>
> >>>Diego Caviglia wrote:
> >>>
> >>>
> >>>      
> >>>
> >>>>Hi all,
> >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> >>>>        
> >>>>
> >>>that ...The PEs
> >>>
> >>>      
> >>>
> >>>>will establish an LDP session using the Extended Discovery
> >>>>        
> >>>>
> >>>.." it is not
> >>>
> >>>      
> >>>
> >>>>clear to me why I can't use basic discovery mechansim given
> >>>>        
> >>>>
> >>>that I have
> >>>
> >>>      
> >>>
> >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> >>>>        
> >>>>
> >>>tunnel Hello packets
> >>>
> >>>      
> >>>
> >>>>between the LSP peers.
> >>>>
> >>>>What am I missing?
> >>>>
> >>>>Thanks.
> >>>>
> >>>>Regards
> >>>>
> >>>>Diego
> >>>>
> >>>>
> >>>>
> >>>>_______________________________________________
> >>>>pwe3 mailing list
> >>>>pwe3@ietf.org
> >>>>https://www1.ietf.org/mailman/listinfo/pwe3
> >>>>
> >>>>
> >>>>
> >>>>        
> >>>>
> >>>_______________________________________________
> >>>pwe3 mailing list
> >>>pwe3@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/pwe3
> >>>
> >>>      
> >>>
> >>
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>pwe3 mailing list
> >>pwe3@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/pwe3
> >>
> >>
> >>    
> >>
> >
> >
> >
> >
> >  
> >
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Shah, Himanshu" <hshah@ciena.com>
Subject: RE: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 12:21:51 -0500
Lines: 267
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: "'pwe3 <pwe3'" <pwe3@ietf.org>,
	"'Stewart Bryant <stbryant'" <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 18:42:58 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>, "'Diego Caviglia'"
	<Diego.Caviglia@marconi.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

One more clarification....

Granted that one could very well do basic 
discovery using multicast IP address and
then exchange PW FECs over this tunnel.

The only reason for still doing extended
discovery using targetted hello is to 
remain interoperable with tons of those PEs
out there who specifically support extended
discovery even when a remote PE is directly
connected via a "tunnel" or a direct link.

IMO.

himanshu

> -----Original Message-----
> From: Shah, Himanshu 
> Sent: Tuesday, December 14, 2004 12:09 PM
> To: 'Luca Martini'; Diego Caviglia
> Cc: Stewart Bryant <stbryant; pwe3 <pwe3
> Subject: RE: [PWE3] LDP Signalling for PWs
> 
> 
> Nope.
> 
> I meant that router intelligently recognizes that
> logical IP interface is a "tunnel" and hence for
> targetted LDP purposes, send targetted hello to 
> unicast IP address (which is the tunnel endpoint's
> IP address). 
> 
> So if you are doing, topology LDP, you would send
> link hello (a way to have LDP work across RSVP-TE
> cloud using this tunnel) and at the same time if you 
> are doing PWE3 signaling, you would also send targetted 
> hello for extended discovery (using unicast IP address).
> 
> Hope this clears up.
> 
> Either way, I don't think there is any need to change
> pwe3-control draft, because this would either be
> an implementation detail or a suggested possibility in
> applicability draft as Stewart suggested.
> 
> /himanshu
> 
> > -----Original Message-----
> > From: Luca Martini [mailto:lmartini@cisco.com]
> > Sent: Tuesday, December 14, 2004 11:36 AM
> > To: Diego Caviglia
> > Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> > Subject: Re: [PWE3] LDP Signalling for PWs
> > 
> > 
> > Diego,
> > 
> > What Himanshu described still involves putting multicast into 
> > the rsvp 
> > tunnel. I do not believe that this is the practice today.
> > It can be done , but there is no significant advantage to 
> > just using the 
> > extended discovery mechanism. You should keep in mind that normal 
> > behavior is to actually put all the LDP packets into the MPLS LSP 
> > between the 2 PEs. ( regardless if it is RSVP sin galled or 
> > LDP signaled ).
> > 
> > Luca
> > 
> > 
> > Diego Caviglia wrote:
> > 
> > >Stewart,
> > >                   no problem from my side I see that the ID 
> > is number 13
> > >and thus is better to restrict the modify.
> > >
> > >Purpose of my proposal is to state somewhere, an 
> > applicability ID could be
> > >good, that is possible, using the procedure Shah depicted in 
> > his mail, to
> > >use a tunnel to transport the Hello messages.
> > >
> > >Regards
> > >
> > >Diego
> > >
> > >
> > >
> > >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> > >
> > >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> > >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> > >       <lmartini@cisco.com>
> > >
> > >Subject:    Re: [PWE3] LDP Signalling for PWs
> > >
> > >
> > >We are really trying to get the control draft to RFC,
> > >and therefore to restrict the changes, and that
> > >means taking a hard line on anything except
> > >protocol design errors.
> > >
> > >This looks more like an applicability issue than a
> > >correctness issue, and as perhaps we should
> > >put it in an applicability draft?
> > >
> > >- Stewart
> > >
> > >Diego Caviglia wrote:
> > >  
> > >
> > >>Shah,
> > >>              thank for your replay, I agree with you.
> > >>
> > >>May be could be useful to state that in the LDP signalling draft.
> > >>
> > >>What is the feeling of the list on that matter?
> > >>
> > >>Diego
> > >>
> > >>
> > >>
> > >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> > >>
> > >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> > >>       <Diego.Caviglia@marconi.com>
> > >>cc:    pwe3@ietf.org
> > >>
> > >>Subject:    RE: [PWE3] LDP Signalling for PWs
> > >>
> > >>
> > >>If you allow tunnel (lets say RSVP-TE based) to be
> > >>a logical IP i/f, one could conceivably send
> > >>regular LDP hello to discover the remote PE.
> > >>
> > >>This would be no different than if the target
> > >>LDP peer were to be on the direct link (adjacent).
> > >>
> > >>However, in order to differentiate topology based
> > >>LDP (link hello) from PWE3 signaling LDP (targetted), you have to
> > >>set the LDP Hello with t-bit set and send it
> > >>on unicast LDP Peer ID.
> > >>
> > >>Unless of course, you recognize the i/f as tunnel
> > >>and
> > >>1) use the tunnel end-point address as the unicast
> > >>address
> > >>2) send targetted hello
> > >>
> > >>then you achieve what you intended.
> > >>
> > >>/himanshu
> > >>
> > >>
> > >>
> > >>
> > >>    
> > >>
> > >>>-----Original Message-----
> > >>>From: Luca Martini [mailto:lmartini@cisco.com]
> > >>>Sent: Monday, December 13, 2004 5:08 PM
> > >>>To: Diego Caviglia
> > >>>Cc: pwe3@ietf.org
> > >>>Subject: Re: [PWE3] LDP Signalling for PWs
> > >>>
> > >>>
> > >>>Diego,
> > >>>
> > >>>Extended discovery means that the UDP hello packets to 
> > port 646 will
> > >>>have a destination IP address that is the remote PE's address.
> > >>>Basic discovery involves sending the UDP hello packets to 
> > port 646 to
> > >>>destination address 224.0.0.2 ( the all routers multicast 
> > address ).
> > >>>Packets to address 224.0.0.2 will not travel any further then the
> > >>>immediate neighbors.
> > >>>Normally there is not MPLS FEC for 224.0.0.2
> > >>>
> > >>>Luca
> > >>>
> > >>>
> > >>>Diego Caviglia wrote:
> > >>>
> > >>>
> > >>>      
> > >>>
> > >>>>Hi all,
> > >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> > >>>>        
> > >>>>
> > >>>that ...The PEs
> > >>>
> > >>>      
> > >>>
> > >>>>will establish an LDP session using the Extended Discovery
> > >>>>        
> > >>>>
> > >>>.." it is not
> > >>>
> > >>>      
> > >>>
> > >>>>clear to me why I can't use basic discovery mechansim given
> > >>>>        
> > >>>>
> > >>>that I have
> > >>>
> > >>>      
> > >>>
> > >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> > >>>>        
> > >>>>
> > >>>tunnel Hello packets
> > >>>
> > >>>      
> > >>>
> > >>>>between the LSP peers.
> > >>>>
> > >>>>What am I missing?
> > >>>>
> > >>>>Thanks.
> > >>>>
> > >>>>Regards
> > >>>>
> > >>>>Diego
> > >>>>
> > >>>>
> > >>>>
> > >>>>_______________________________________________
> > >>>>pwe3 mailing list
> > >>>>pwe3@ietf.org
> > >>>>https://www1.ietf.org/mailman/listinfo/pwe3
> > >>>>
> > >>>>
> > >>>>
> > >>>>        
> > >>>>
> > >>>_______________________________________________
> > >>>pwe3 mailing list
> > >>>pwe3@ietf.org
> > >>>https://www1.ietf.org/mailman/listinfo/pwe3
> > >>>
> > >>>      
> > >>>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>_______________________________________________
> > >>pwe3 mailing list
> > >>pwe3@ietf.org
> > >>https://www1.ietf.org/mailman/listinfo/pwe3
> > >>
> > >>
> > >>    
> > >>
> > >
> > >
> > >
> > >
> > >  
> > >
> > 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com>
Subject: Re: LDP Signalling for PWs
Date: Tue, 14 Dec 2004 15:57:59 -0500
Lines: 291
References: <BEB81A42E3EDB346B7FFB63804D1509603D495@mamxm01.ciena.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "'pwe3 <pwe3'" <pwe3@ietf.org>, 'Luca Martini' <lmartini@cisco.com>,
	"'Stewart Bryant <stbryant'" <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Tue Dec 14 22:34:49 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U)
X-Accept-Language: en
To: "Shah, Himanshu" <hshah@ciena.com>
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Himanshu,

"Shah, Himanshu" wrote:

> Granted that one could very well do basic
> discovery using multicast IP address

over a tunnel/logical IP interface.
Agree with the above and I believe it is what Diego suggested.

There seems to be some advantage in using basic discovery over a tunnel in
that it is not necessary to configure a PE with the remote PE addresses for
PW signaling ...

> and
> then exchange PW FECs over this tunnel.
>
> The only reason for still doing extended
> discovery using targetted hello is to
> remain interoperable with tons of those PEs
> out there who specifically support extended
> discovery even when a remote PE is directly
> connected via a "tunnel" or a direct link.
>

Agree there is no need to change this feature for interoperablility
purposes, as long as the draft does not preclude other options.

Thanks
Cheng-Yin

>
> IMO.
>
> himanshu
>
> > -----Original Message-----
> > From: Shah, Himanshu
> > Sent: Tuesday, December 14, 2004 12:09 PM
> > To: 'Luca Martini'; Diego Caviglia
> > Cc: Stewart Bryant <stbryant; pwe3 <pwe3
> > Subject: RE: [PWE3] LDP Signalling for PWs
> >
> >
> > Nope.
> >
> > I meant that router intelligently recognizes that
> > logical IP interface is a "tunnel" and hence for
> > targetted LDP purposes, send targetted hello to
> > unicast IP address (which is the tunnel endpoint's
> > IP address).
> >
> > So if you are doing, topology LDP, you would send
> > link hello (a way to have LDP work across RSVP-TE
> > cloud using this tunnel) and at the same time if you
> > are doing PWE3 signaling, you would also send targetted
> > hello for extended discovery (using unicast IP address).
> >
> > Hope this clears up.
> >
> > Either way, I don't think there is any need to change
> > pwe3-control draft, because this would either be
> > an implementation detail or a suggested possibility in
> > applicability draft as Stewart suggested.
> >
> > /himanshu
> >
> > > -----Original Message-----
> > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > Sent: Tuesday, December 14, 2004 11:36 AM
> > > To: Diego Caviglia
> > > Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> > > Subject: Re: [PWE3] LDP Signalling for PWs
> > >
> > >
> > > Diego,
> > >
> > > What Himanshu described still involves putting multicast into
> > > the rsvp
> > > tunnel. I do not believe that this is the practice today.
> > > It can be done , but there is no significant advantage to
> > > just using the
> > > extended discovery mechanism. You should keep in mind that normal
> > > behavior is to actually put all the LDP packets into the MPLS LSP
> > > between the 2 PEs. ( regardless if it is RSVP sin galled or
> > > LDP signaled ).
> > >
> > > Luca
> > >
> > >
> > > Diego Caviglia wrote:
> > >
> > > >Stewart,
> > > >                   no problem from my side I see that the ID
> > > is number 13
> > > >and thus is better to restrict the modify.
> > > >
> > > >Purpose of my proposal is to state somewhere, an
> > > applicability ID could be
> > > >good, that is possible, using the procedure Shah depicted in
> > > his mail, to
> > > >use a tunnel to transport the Hello messages.
> > > >
> > > >Regards
> > > >
> > > >Diego
> > > >
> > > >
> > > >
> > > >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> > > >
> > > >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> > > >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> > > >       <lmartini@cisco.com>
> > > >
> > > >Subject:    Re: [PWE3] LDP Signalling for PWs
> > > >
> > > >
> > > >We are really trying to get the control draft to RFC,
> > > >and therefore to restrict the changes, and that
> > > >means taking a hard line on anything except
> > > >protocol design errors.
> > > >
> > > >This looks more like an applicability issue than a
> > > >correctness issue, and as perhaps we should
> > > >put it in an applicability draft?
> > > >
> > > >- Stewart
> > > >
> > > >Diego Caviglia wrote:
> > > >
> > > >
> > > >>Shah,
> > > >>              thank for your replay, I agree with you.
> > > >>
> > > >>May be could be useful to state that in the LDP signalling draft.
> > > >>
> > > >>What is the feeling of the list on that matter?
> > > >>
> > > >>Diego
> > > >>
> > > >>
> > > >>
> > > >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> > > >>
> > > >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> > > >>       <Diego.Caviglia@marconi.com>
> > > >>cc:    pwe3@ietf.org
> > > >>
> > > >>Subject:    RE: [PWE3] LDP Signalling for PWs
> > > >>
> > > >>
> > > >>If you allow tunnel (lets say RSVP-TE based) to be
> > > >>a logical IP i/f, one could conceivably send
> > > >>regular LDP hello to discover the remote PE.
> > > >>
> > > >>This would be no different than if the target
> > > >>LDP peer were to be on the direct link (adjacent).
> > > >>
> > > >>However, in order to differentiate topology based
> > > >>LDP (link hello) from PWE3 signaling LDP (targetted), you have to
> > > >>set the LDP Hello with t-bit set and send it
> > > >>on unicast LDP Peer ID.
> > > >>
> > > >>Unless of course, you recognize the i/f as tunnel
> > > >>and
> > > >>1) use the tunnel end-point address as the unicast
> > > >>address
> > > >>2) send targetted hello
> > > >>
> > > >>then you achieve what you intended.
> > > >>
> > > >>/himanshu
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>>-----Original Message-----
> > > >>>From: Luca Martini [mailto:lmartini@cisco.com]
> > > >>>Sent: Monday, December 13, 2004 5:08 PM
> > > >>>To: Diego Caviglia
> > > >>>Cc: pwe3@ietf.org
> > > >>>Subject: Re: [PWE3] LDP Signalling for PWs
> > > >>>
> > > >>>
> > > >>>Diego,
> > > >>>
> > > >>>Extended discovery means that the UDP hello packets to
> > > port 646 will
> > > >>>have a destination IP address that is the remote PE's address.
> > > >>>Basic discovery involves sending the UDP hello packets to
> > > port 646 to
> > > >>>destination address 224.0.0.2 ( the all routers multicast
> > > address ).
> > > >>>Packets to address 224.0.0.2 will not travel any further then the
> > > >>>immediate neighbors.
> > > >>>Normally there is not MPLS FEC for 224.0.0.2
> > > >>>
> > > >>>Luca
> > > >>>
> > > >>>
> > > >>>Diego Caviglia wrote:
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>>Hi all,
> > > >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> > > >>>>
> > > >>>>
> > > >>>that ...The PEs
> > > >>>
> > > >>>
> > > >>>
> > > >>>>will establish an LDP session using the Extended Discovery
> > > >>>>
> > > >>>>
> > > >>>.." it is not
> > > >>>
> > > >>>
> > > >>>
> > > >>>>clear to me why I can't use basic discovery mechansim given
> > > >>>>
> > > >>>>
> > > >>>that I have
> > > >>>
> > > >>>
> > > >>>
> > > >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> > > >>>>
> > > >>>>
> > > >>>tunnel Hello packets
> > > >>>
> > > >>>
> > > >>>
> > > >>>>between the LSP peers.
> > > >>>>
> > > >>>>What am I missing?
> > > >>>>
> > > >>>>Thanks.
> > > >>>>
> > > >>>>Regards
> > > >>>>
> > > >>>>Diego
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>_______________________________________________
> > > >>>>pwe3 mailing list
> > > >>>>pwe3@ietf.org
> > > >>>>https://www1.ietf.org/mailman/listinfo/pwe3
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>_______________________________________________
> > > >>>pwe3 mailing list
> > > >>>pwe3@ietf.org
> > > >>>https://www1.ietf.org/mailman/listinfo/pwe3
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>_______________________________________________
> > > >>pwe3 mailing list
> > > >>pwe3@ietf.org
> > > >>https://www1.ietf.org/mailman/listinfo/pwe3
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Tue, 14 Dec 2004 15:51:43 -0700
Organization: Cisco Systems
Lines: 188
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: philippe.niger@francetelecom.com, ckoc@zteusa.com, yaakov_s@rad.com,
	Alik Shimelmits <alik@AXERRA.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, busschbach@lucent.com,
	nabil.n.bitar@verizon.com, peter.j.willis@bt.com,
	richard.spencer@bt.com, dimitri.papadimitriou@alcatel.be,
	simon.delord@francetelecom.com, rahul@juniper.net,
	Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>, neil.2.harrison@bt.com,
	jdrake@calient.net, dbrungard@att.com, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Wed Dec 15 06:33:09 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Dec 2004 00:28:03 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Sasha,
Bringing this discussion to the PWE3 list...

Thanks for the comments!
See below.

Luca


Sasha Vainshtein wrote:

> Luca and all, I have just started reading 
> draft-martini-pwe3-MH-PW-requirements-00.txt that has been announced 
> today. I have a few comments/questions that I'd like to discuss on 
> this list first.  
>
>    1. There are several *ediorial* nits that are worth fixing. E.g.:
>           * In Fig.2, there are PW1, PW3 and PW4, but no PW2, just an
>             "unnumbered" PW
>
???
I see PW2 in the picture.

>           * This notation contradicts, IMHO, the explanatory text
>             below that states that "PWs are used to connect the
>             Attachment circuits (ACs) attached to PE1 to the
>             corresponding ACs attached to PE3"
>
Yes, this requirement draft defines a new model , that might contradict 
the letter of some existing documents.

>           * The notion of a "PW segment" introduced later is not used
>             in the diagram
>
yes pw-segment , and SH-PW seem to be the same.
Can we remove the PW-segment definition ? or maybe alias it to SH-PW ?
Anybody ?

>           * Discussion of the scalability issues (item ii in Section 5
>             "Use Cases") states that full mesh of unidirectional PSN
>             tunnels between *N* PEs will provde *N2* tunnels (instead
>             of *N^2*)
>
This is really weird ! Somewhere in the e-mail , or the IETF directories 
the ^  got removed. The version I have locally on my computer has the ^ 
in it.


>           * Punctuation is wrong in items iii and iv of the same
>             section (neither a colon nor a full stop separate the name
>             of the issue from the first statement of the exposition) etc.
>
ok fixed.

>    1. The "Terminology" section mentions "*PW access point address*" -
>       a notion that is not used anywhere in the document (and, IMHO,
>       is not really defined in the document either). (And, BTW, I
>       think that the Client layer service accesses the server layer at
>       the *access* *point*, not at the *access point address*)
>
ok, will comment this out for now, if we use it , we'll put it back.

>    1. I think that the following statement in the "Use Cases" section
>       requires clarification: "*At a minimum PW control
>       channel establishment requires knowledge of and reachability to
>       the remote (ultimate) PE IP address*". I understand that
>       *reachability* of the remote ultuimate PE IP address may be
>       problematic in some cases; but do we really envision the case
>       when a PE can be set up without the one of the ultimate PEs
>       possessing any *knowledge* about IP address of its remote peer?
>       And, if this is the case, can in-band OAM provide end-to-end
>       connectivity verification?
>
sure. you can use 127.0.0.1 as the IP address of the in-band OAM packets .
I think that the requirement is to be able to establish a MH-PW between 
2 U-PEs with out having complete knowledge of each other's IP addresses. 
This does not mean that some S-PE in the middle does not know about at 
least one of the U-PE IP addresses.
Most of the text following is more a justification for the requirement.

>    1. Some of the MH-PW requirements look as if they equally apply to
>       SH-PWs. E.g., if "full client/server transparency" is a
>       mandatory requirement for MH-PW, why not for SH-PW? And why is
>       it limited to only S-PEs (and with exceptions)? It seems that
>       one of the editors (Luca?) was really dissatisfied with this
>       text, too...
>
I only edited format this time ;-) so I did not express any opinion.... 
I think this was Nabil.
This is probably not a valid requirement for MH-PW as it is written. We 
are not going to change the encapsulation of PWs unless there is a 
really good reason why then cannot be turned into MH-PWs.

Do you agree ?


>    1. Still more on the "full client/server transparency": I have seen
>       Neil's comments on the PWE3 list that can be interpreted as if
>       FCS retention is part of this transparency. If this is so, then
>       we cannot meet the requirement to use PWE3 encapsulations in
>       MH-PWs (since they, at best, consider FCS retention as OPTIONAL).
>
Ok, so we either say that PW do not fit , or MH-PWs have to be based on 
SH-PWs.
I think that the latter is a clear requirement, and much stronger then 
the former.

>    1. What exactly is meant by "tunneled MH-PWs" and "overlay tunnels"
>       (in item ii of Section 6.1)? These notions are not defined
>       anywhere (AFAIK)
>
I think that this means that if PW are used to build a PSN, then if the 
PSN is in turn used to carry PWs, the latter should not be impacted by 
the former PWs.
( quite frankly I cannot see how they could ... )

>    1. Change of encapsulation mode defined as an option for  S-PEs is
>       not defined unambiguously. E.g., suppose that I want to carry an
>       ATM VC bewteen two CEs: can an S-PE change encapsulation from
>       "N-to-one" to "One-to-one"? Or from Cell relay to SPDU? (In case
>       anybody has his/ger doubts, I find this ptoposal abhorrent, but
>       it is not explicitly prohibited by the text as I read it)
>
yes. Actually I would like to ask the SPs , if they really want to 
operate a network that might have an Interworking function somewhere 
along it path?  To me this is operational suicide. After all a PW could 
be interworked several times .. like ethernet -> ATM ->Frame-Relay -> 
Ethernet ....
Interworking at the S-PE  is one of the requirements that I would like 
to seriously consider removing.

>    1. Item i in Section 6.2 requires that U-PEs and S-PE are capable
>       of admission control per PSN tunnel. Does this preclude PSN
>       tunnels that do not have any explicit QoS guarantees (like
>       L2TPv3)? Or does it mean that, for these ctunnels, admission
>       control simply admits everything? (I'm pretty sure that at least
>       one of you will attribute this comment one more incaration of
>       the original PWE3 sin, namely, that MPLS = IP, but then, at
>       least one other participant of this team has explicitly
>       requested L2TPv3 becoming as standard as MPLS for PWs ;-)
>
This is not an unreasonable question. L2TPv3 might have several session 
each with different QoS settings in the DSCP bits of the IP header. 
Tunnel CAC need not be based on RSVP-TE. I believe that the intent was 
to mention only MPLS LSPs.
However I would like to hear from Lei how can CAC be used in l2TPv3.
( also this section has spell errors and grammar issues ... )
We also need to consider that TE is unidirectional , but PW are 
bi-directional.  what happens if a PW is admitted in one direction , but 
fails in the other direction ?

>    1. Item ii in Section 6.2 seems even more suspicious because it
>       requires that U-PEs and S-PEs actually select a path across the
>       PSN along which the traffic will be tunneled. IMHO we have nvere
>       before discussed this "requirement"; can somebdy please point to
>       its origin?
>
I think this is needs to be re-written to fit into the pwe3 charter :

When setting up a MH-PW, S-PEs and U-PEs MUST be able to request a 
tunnel across the PSN in such a way as to  satisfy the MH-PW QoS and 
bandwidth requirements. Restrictions may apply depending on the method 
used for setting up a PW segment and on PSN  tunnel types.
Note that this is not new, and can be achieved today in many SH-PW 
implementations.

>    1. Last (for the moment) but not least: Skipping quite a few
>       sections, what exactly is intended by the statement in item
>       iii,. Section 6.6 "*The MH-PW client SHOULD support a A Forward
>       Defect Indicator (FDI)*" ? MH-PW clients, IMHO, are native
>       services for which PWE3 is provided, right? So, if a service
>       (like Ethernet, FR or NxDS0) does not provide FDI, it does not
>       deserve becoming a client of an MH-PW (and should feel happy
>       that less restrictive SH-PWs still bother carrying it)?
>
I believe that this refers to the PW status TLV infrastructure. Where we 
can send a fault indication in the forward direction.
right ?

Thanks.
Luca

> Hopefully these comments will be helpful.   Regards, 
>                                   Sasha Vainshtein 
> email:                         sasha@axerra.com 
> <mailto:sasha@axerra.com> phone:                       +972-3-7569993 
> (office) fax:                            +972-3-6487779 
> mobile:                      +972-52-8674833 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Diego Caviglia" <Diego.Caviglia@marconi.com>
Subject: Re: LDP Signalling for PWs
Date: Wed, 15 Dec 2004 08:27:14 +0100
Lines: 311
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: pwe3@ietf.org, lmartini@cisco.com, hshah@ciena.com, stbryant@cisco.com
X-From: pwe3-bounces@ietf.org Wed Dec 15 08:41:54 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Cheng-Yin Lee <Cheng-Yin.Lee" <Cheng-Yin.Lee@alcatel.com>
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26,
	2003) at 15/12/2004 07:26:53
X-Scan-Signature: b360bd6cb019c35178e5cf9eeb747a5c
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Hi Cheng-Yin,
                              yes that was I had in mind.

Regards.

Diego



Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com> on 14/12/2004 21.57.59

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-0
	0.txt
Date: Wed, 15 Dec 2004 10:01:30 +0200
Lines: 264
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: philippe.niger@francetelecom.com, ckoc@zteusa.com, yaakov_s@rad.com,
	Alik Shimelmits <alik@AXERRA.com>, busschbach@lucent.com,
	dbrungard@att.com, nabil.n.bitar@verizon.com,
	peter.j.willis@bt.com, richard.spencer@bt.com,
	dimitri.papadimitriou@alcatel.be, simon.delord@francetelecom.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, rahul@juniper.net,
	neil.2.harrison@bt.com, Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>, jdrake@calient.net,
	Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Wed Dec 15 09:17:07 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Luca and all,
Please see some answers inline.
I have snipped parts of the text that are not relevant to the key issues.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Wednesday, December 15, 2004 12:52 AM
> To: Sasha Vainshtein
> Cc: philippe.niger@francetelecom.com; ckoc@zteusa.com; 
> yaakov_s@rad.com; Alik Shimelmits; PWE3 WG (E-mail); 
> busschbach@lucent.com; nabil.n.bitar@verizon.com; 
> peter.j.willis@bt.com; richard.spencer@bt.com; 
> dimitri.papadimitriou@alcatel.be; 
> simon.delord@francetelecom.com; rahul@juniper.net; Sharon 
> Galtzur; Ping Pan; neil.2.harrison@bt.com; 
> jdrake@calient.net; dbrungard@att.com; Matthew.Bocci@alcatel.co.uk
> Subject: [PWE3] Re: I-D 
> ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
> 
> 
> Sasha,
> Bringing this discussion to the PWE3 list...
>
[Sasha] OK.
> 
> Thanks for the comments!
> See below.
> 
> Luca
> 
> 
> Sasha Vainshtein wrote:
> 
> > Luca and all, I have just started reading 
> > draft-martini-pwe3-MH-PW-requirements-00.txt that has been 
> announced 
> > today. I have a few comments/questions that I'd like to discuss on 
> > this list first.  
> >
> >    1. There are several *ediorial* nits that are worth fixing. 
>
[Sasha] ... snipped ...
>
> >    1. I think that the following statement in the "Use Cases" section
> >       requires clarification: "*At a minimum PW control
> >       channel establishment requires knowledge of and reachability to
> >       the remote (ultimate) PE IP address*". I understand that
> >       *reachability* of the remote ultuimate PE IP address may be
> >       problematic in some cases; but do we really envision the case
> >       when a PE can be set up without the one of the ultimate PEs
> >       possessing any *knowledge* about IP address of its remote peer?
> >       And, if this is the case, can in-band OAM provide end-to-end
> >       connectivity verification?
> >
> sure. you can use 127.0.0.1 as the IP address of the in-band 
> OAM packets .
> I think that the requirement is to be able to establish a 
> MH-PW between 
> 2 U-PEs with out having complete knowledge of each other's IP 
> addresses. 
> This does not mean that some S-PE in the middle does not know 
> about at 
> least one of the U-PE IP addresses.
> Most of the text following is more a justification for the 
> requirement.
>
[Sasha] I am still not so sure. Here are two issues that require discussion

1. E2E connectivity verification for MH-PWs. If the corresponding
OAM packets do not carry unambigouous identification of the expected 
remote end point, this functionality cannot be fully supported, IMHO.
And unambiguous identification of the remote peer end point that does not
yield an umbiguous identification of the containing U-PE seems highly
problematic to me. There is a difference between carrying such an
identification
in the CV packets and carrying it as the Destination IP address in the IP
header of these packets (assuming that they are IP packets) - a
situation dealt with in the LSP Ping proposal: Destination IP address
of the LSP Ping packets is from 127.0.0.0/8 so that it would be recognized
as
having local destination by every LSR that terminates the LSP (e.g., 
in the traceroute mode or due to misconnection). But the payload carries
the explicit FEC stack.

2. Requirement (mentioned by several people in the discussion on the DT
list)
for "one-touch single-ended provisioning of an MH-PE". The draft in question
presents a weaker form of this requirement (Section 6.5., item ii), speaking
about
an option to signal a MH-PW using a minimal number of OSS touches, where 
the minimal number" may be greater than 1. But if we tend for single-touch
provisioning, the following logic looks correct to me:
* The device to be touched MUST be one of the U-PEs
* It MUST receive the information containg unambiguous identification of the
remote 
peer end point, including unambiguous identification of the remote U-PE

Of course, one could argue that unambiguous identification of the remote
U-PE
does not have to be its IP address. But in real life, what other unambiguous
identification of devices do we have? Phone numbers?
>
> >    1. Some of the MH-PW requirements look as if they 
> equally apply to
> >       SH-PWs. E.g., if "full client/server transparency" is a
> >       mandatory requirement for MH-PW, why not for SH-PW? And why is
> >       it limited to only S-PEs (and with exceptions)? It seems that
> >       one of the editors (Luca?) was really dissatisfied with this
> >       text, too...
> >
> I only edited format this time ;-) so I did not express any 
> opinion.... 
> I think this was Nabil.
> This is probably not a valid requirement for MH-PW as it is 
> written. We 
> are not going to change the encapsulation of PWs unless there is a 
> really good reason why then cannot be turned into MH-PWs.
> 
> Do you agree ?
> 
[Sasha] Of course I agree that we should preserve PW encapsulations when 
going from SH-PWs to MH-PWs. Any other approach would be a nightmare
for the vendors and operators.

At the same time, please note that the current PWE3 Architecture document
has its own wording for "client/servr transparency". It is called
"Principle of Minimum Intervention" (Section 3.3.5). So I have two
practical suggestions for the next revision of the draft:

* Use one consistent set of notions and terms, presumably based
  on the existing PWE3 architecture with the necessary extensions
* Provide (as an Annex?) consistent translation between this set of terms 
  and the applicable terms/motions of G.805.

The alternative is the current situation when a requirement that has been
explicitly formulated (even if not always met) for SH-PWs looks like a
new requirement restricted to MH-PWs because it is formulated
using a different language.
> 
> >    1. Still more on the "full client/server transparency": 
> I have seen
> >       Neil's comments on the PWE3 list that can be interpreted as if
> >       FCS retention is part of this transparency. If this 
> is so, then
> >       we cannot meet the requirement to use PWE3 encapsulations in
> >       MH-PWs (since they, at best, consider FCS retention 
> as OPTIONAL).
> >
> Ok, so we either say that PW do not fit , or MH-PWs have to 
> be based on SH-PWs.
> I think that the latter is a clear requirement, and much 
> stronger then the former.
>
[Sasha] AsI have said already, I agree that MH-PWs and SH-PWs
MUST use the same encapsulation. And I think that this should
be explicitly stated in the MH-PW requirements draft.
>
... snipped ...
>
> >    1. Change of encapsulation mode defined as an option for S-PEs is
> >       not defined unambiguously. E.g., suppose that I want  to carry an
> >       ATM VC bewteen two CEs: can an S-PE change encapsulation from
> >       "N-to-one" to "One-to-one"? Or from Cell relay to SPDU? (In case
> >       anybody has his/her doubts, I find this ptoposal abhorrent, but
> >       it is not explicitly prohibited by the text as I read it)
> >
> yes. Actually I would like to ask the SPs , if they really want to 
> operate a network that might have an Interworking function somewhere 
> along it path?  To me this is operational suicide. After all a PW could 
> be interworked several times .. like ethernet -> ATM ->Frame-Relay -> 
> Ethernet ....
> Interworking at the S-PE  is one of the requirements that I 
> would like to seriously consider removing.
>
[Sasha] I could not say it better! 
>
> >    1. Item i in Section 6.2 requires that U-PEs and S-PE are capable
> >       of admission control per PSN tunnel. Does this preclude PSN
> >       tunnels that do not have any explicit QoS guarantees (like
> >       L2TPv3)? Or does it mean that, for these ctunnels, admission
> >       control simply admits everything? (I'm pretty sure that at least
> >       one of you will attribute this comment one more incaration of
> >       the original PWE3 sin, namely, that MPLS = IP, but then, at
> >       least one other participant of this team has explicitly
> >       requested L2TPv3 becoming as standard as MPLS for PWs ;-)
> >
> This is not an unreasonable question. L2TPv3 might have 
> several session each with different QoS settings in the DSCP bits of the
IP header. 
> Tunnel CAC need not be based on RSVP-TE. I believe that the  intent was 
> to mention only MPLS LSPs.
>
[Sasha] If this was the intent, let's implement it!
>
> However I would like to hear from Lei how can CAC be used in l2TPv3.
> ( also this section has spell errors and grammar issues ... )
> We also need to consider that TE is unidirectional , but PW are 
> bi-directional.  what happens if a PW is admitted in one 
> direction , but fails in the other direction ?
>
[Sasha] I assume the setup should fail?
>
> >    1. Item ii in Section 6.2 seems even more suspicious because it
> >       requires that U-PEs and S-PEs actually select a path across the
> >       PSN along which the traffic will be tunneled. IMHO we have nvere
> >       before discussed this "requirement"; can somebody please point to
> >       its origin?
> >
> I think this is needs to be re-written to fit into the pwe3 charter :
> 
> When setting up a MH-PW, S-PEs and U-PEs MUST be able to request a 
> tunnel across the PSN in such a way as to  satisfy the MH-PW QoS and 
> bandwidth requirements. Restrictions may apply depending on 
> the method 
> used for setting up a PW segment and on PSN  tunnel types.
> Note that this is not new, and can be achieved today in many SH-PW 
> implementations.
>
[Sasha] This sounds reasonable to me.  
>
> >    1. Last (for the moment) but not least: Skipping quite a few
> >       sections, what exactly is intended by the statement in item
> >       iii,. Section 6.6 "*The MH-PW client SHOULD support a A Forward
> >       Defect Indicator (FDI)*" ? MH-PW clients, IMHO, are native
> >       services for which PWE3 is provided, right? So, if a service
> >       (like Ethernet, FR or NxDS0) does not provide FDI, it does not
> >       deserve becoming a client of an MH-PW (and should feel happy
> >       that less restrictive SH-PWs still bother carrying it)?
> >
> I believe that this refers to the PW status TLV infrastructure. Where we 
> can send a fault indication in the forward direction. right ?
>
[Sasha] I think that the text, as written, admits too many interpretations,
partly due to the fact that it uses terms (like MH-PW client) that are
not explicitly defined. 

And I suspect that FDI belongs to the data plane, not to the control plane, 
so I doubt if the PW Status TLV is relevant for the text as written...
(That is why FR does not have any FDI...)
> 
> Thanks.
> Luca
> 
> > Hopefully these comments will be helpful.   Regards, 
> >                                   Sasha Vainshtein 
> > email:                         sasha@axerra.com 
> > <mailto:sasha@axerra.com> phone:                       
> +972-3-7569993 
> > (office) fax:                            +972-3-6487779 
> > mobile:                      +972-52-8674833 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: LDP Signalling for PWs
Date: Wed, 15 Dec 2004 10:15:51 +0200
Lines: 357
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: lmartini@cisco.com, pwe3@ietf.org, hshah@ciena.com, stbryant@cisco.com
X-From: pwe3-bounces@ietf.org Wed Dec 15 09:24:06 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Diego Caviglia'" <Diego.Caviglia@marconi.com>,
	"Cheng-Yin Lee <Cheng-Yin.Lee" <Cheng-Yin.Lee@alcatel.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 4d9ae72af46718088458d214998cc683
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Diego, Che-Yin and all,
Please see a brief comment inline.

Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
> Sent: Wednesday, December 15, 2004 9:27 AM
> To: Cheng-Yin Lee <Cheng-Yin.Lee
> Cc: pwe3@ietf.org; lmartini@cisco.com; hshah@ciena.com; 
> stbryant@cisco.com
> Subject: Re: [PWE3] LDP Signalling for PWs
> 
> 
> 
> Hi Cheng-Yin,
>                               yes that was I had in mind.
> 
> Regards.
> 
> Diego
> 
> 
> 
> Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com> on 14/12/2004 21.57.59
> 
> To:    "Shah, Himanshu" <hshah@ciena.com>
> cc:    "'Luca Martini'" <lmartini@cisco.com>, "'Diego Caviglia'"
>        <Diego.Caviglia@marconi.com>, "'pwe3 <pwe3'" <pwe3@ietf.org>,
>        "'Stewart Bryant <stbryant'" <stbryant@cisco.com>
> 
> Subject:    Re: [PWE3] LDP Signalling for PWs
> 
> 
> Himanshu,
> 
> "Shah, Himanshu" wrote:
> 
> > Granted that one could very well do basic
> > discovery using multicast IP address
> 
> over a tunnel/logical IP interface.
> Agree with the above and I believe it is what Diego suggested.
> 
> There seems to be some advantage in using basic discovery 
> over a tunnel in
> that it is not necessary to configure a PE with the remote PE 
> addresses for
> PW signaling ...
>
[Sasha] I do not see any advantage here. 
You know (one of) the IP address(es) of the remote PE
because you need it to configure the tunnel first.
And then you must configure the PE to use a specific 
tunnel LSP leading to the specific peer PE instead. 
>
> > and
> > then exchange PW FECs over this tunnel.
> >
> > The only reason for still doing extended
> > discovery using targetted hello is to
> > remain interoperable with tons of those PEs
> > out there who specifically support extended
> > discovery even when a remote PE is directly
> > connected via a "tunnel" or a direct link.
> >
> 
> Agree there is no need to change this feature for interoperablility
> purposes, as long as the draft does not preclude other options.
> 
> Thanks
> Cheng-Yin
> 
> >
> > IMO.
> >
> > himanshu
> >
> > > -----Original Message-----
> > > From: Shah, Himanshu
> > > Sent: Tuesday, December 14, 2004 12:09 PM
> > > To: 'Luca Martini'; Diego Caviglia
> > > Cc: Stewart Bryant <stbryant; pwe3 <pwe3
> > > Subject: RE: [PWE3] LDP Signalling for PWs
> > >
> > >
> > > Nope.
> > >
> > > I meant that router intelligently recognizes that
> > > logical IP interface is a "tunnel" and hence for
> > > targetted LDP purposes, send targetted hello to
> > > unicast IP address (which is the tunnel endpoint's
> > > IP address).
> > >
> > > So if you are doing, topology LDP, you would send
> > > link hello (a way to have LDP work across RSVP-TE
> > > cloud using this tunnel) and at the same time if you
> > > are doing PWE3 signaling, you would also send targetted
> > > hello for extended discovery (using unicast IP address).
> > >
> > > Hope this clears up.
> > >
> > > Either way, I don't think there is any need to change
> > > pwe3-control draft, because this would either be
> > > an implementation detail or a suggested possibility in
> > > applicability draft as Stewart suggested.
> > >
> > > /himanshu
> > >
> > > > -----Original Message-----
> > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > Sent: Tuesday, December 14, 2004 11:36 AM
> > > > To: Diego Caviglia
> > > > Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> > > > Subject: Re: [PWE3] LDP Signalling for PWs
> > > >
> > > >
> > > > Diego,
> > > >
> > > > What Himanshu described still involves putting multicast into
> > > > the rsvp
> > > > tunnel. I do not believe that this is the practice today.
> > > > It can be done , but there is no significant advantage to
> > > > just using the
> > > > extended discovery mechanism. You should keep in mind 
> that normal
> > > > behavior is to actually put all the LDP packets into 
> the MPLS LSP
> > > > between the 2 PEs. ( regardless if it is RSVP sin galled or
> > > > LDP signaled ).
> > > >
> > > > Luca
> > > >
> > > >
> > > > Diego Caviglia wrote:
> > > >
> > > > >Stewart,
> > > > >                   no problem from my side I see that the ID
> > > > is number 13
> > > > >and thus is better to restrict the modify.
> > > > >
> > > > >Purpose of my proposal is to state somewhere, an
> > > > applicability ID could be
> > > > >good, that is possible, using the procedure Shah depicted in
> > > > his mail, to
> > > > >use a tunnel to transport the Hello messages.
> > > > >
> > > > >Regards
> > > > >
> > > > >Diego
> > > > >
> > > > >
> > > > >
> > > > >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> > > > >
> > > > >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> > > > >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> > > > >       <lmartini@cisco.com>
> > > > >
> > > > >Subject:    Re: [PWE3] LDP Signalling for PWs
> > > > >
> > > > >
> > > > >We are really trying to get the control draft to RFC,
> > > > >and therefore to restrict the changes, and that
> > > > >means taking a hard line on anything except
> > > > >protocol design errors.
> > > > >
> > > > >This looks more like an applicability issue than a
> > > > >correctness issue, and as perhaps we should
> > > > >put it in an applicability draft?
> > > > >
> > > > >- Stewart
> > > > >
> > > > >Diego Caviglia wrote:
> > > > >
> > > > >
> > > > >>Shah,
> > > > >>              thank for your replay, I agree with you.
> > > > >>
> > > > >>May be could be useful to state that in the LDP 
> signalling draft.
> > > > >>
> > > > >>What is the feeling of the list on that matter?
> > > > >>
> > > > >>Diego
> > > > >>
> > > > >>
> > > > >>
> > > > >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> > > > >>
> > > > >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> > > > >>       <Diego.Caviglia@marconi.com>
> > > > >>cc:    pwe3@ietf.org
> > > > >>
> > > > >>Subject:    RE: [PWE3] LDP Signalling for PWs
> > > > >>
> > > > >>
> > > > >>If you allow tunnel (lets say RSVP-TE based) to be
> > > > >>a logical IP i/f, one could conceivably send
> > > > >>regular LDP hello to discover the remote PE.
> > > > >>
> > > > >>This would be no different than if the target
> > > > >>LDP peer were to be on the direct link (adjacent).
> > > > >>
> > > > >>However, in order to differentiate topology based
> > > > >>LDP (link hello) from PWE3 signaling LDP (targetted), 
> you have to
> > > > >>set the LDP Hello with t-bit set and send it
> > > > >>on unicast LDP Peer ID.
> > > > >>
> > > > >>Unless of course, you recognize the i/f as tunnel
> > > > >>and
> > > > >>1) use the tunnel end-point address as the unicast
> > > > >>address
> > > > >>2) send targetted hello
> > > > >>
> > > > >>then you achieve what you intended.
> > > > >>
> > > > >>/himanshu
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>>-----Original Message-----
> > > > >>>From: Luca Martini [mailto:lmartini@cisco.com]
> > > > >>>Sent: Monday, December 13, 2004 5:08 PM
> > > > >>>To: Diego Caviglia
> > > > >>>Cc: pwe3@ietf.org
> > > > >>>Subject: Re: [PWE3] LDP Signalling for PWs
> > > > >>>
> > > > >>>
> > > > >>>Diego,
> > > > >>>
> > > > >>>Extended discovery means that the UDP hello packets to
> > > > port 646 will
> > > > >>>have a destination IP address that is the remote 
> PE's address.
> > > > >>>Basic discovery involves sending the UDP hello packets to
> > > > port 646 to
> > > > >>>destination address 224.0.0.2 ( the all routers multicast
> > > > address ).
> > > > >>>Packets to address 224.0.0.2 will not travel any 
> further then the
> > > > >>>immediate neighbors.
> > > > >>>Normally there is not MPLS FEC for 224.0.0.2
> > > > >>>
> > > > >>>Luca
> > > > >>>
> > > > >>>
> > > > >>>Diego Caviglia wrote:
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>Hi all,
> > > > >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> > > > >>>>
> > > > >>>>
> > > > >>>that ...The PEs
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>will establish an LDP session using the Extended Discovery
> > > > >>>>
> > > > >>>>
> > > > >>>.." it is not
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>clear to me why I can't use basic discovery mechansim given
> > > > >>>>
> > > > >>>>
> > > > >>>that I have
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> > > > >>>>
> > > > >>>>
> > > > >>>tunnel Hello packets
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>>between the LSP peers.
> > > > >>>>
> > > > >>>>What am I missing?
> > > > >>>>
> > > > >>>>Thanks.
> > > > >>>>
> > > > >>>>Regards
> > > > >>>>
> > > > >>>>Diego
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>_______________________________________________
> > > > >>>>pwe3 mailing list
> > > > >>>>pwe3@ietf.org
> > > > >>>>https://www1.ietf.org/mailman/listinfo/pwe3
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>_______________________________________________
> > > > >>>pwe3 mailing list
> > > > >>>pwe3@ietf.org
> > > > >>>https://www1.ietf.org/mailman/listinfo/pwe3
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>_______________________________________________
> > > > >>pwe3 mailing list
> > > > >>pwe3@ietf.org
> > > > >>https://www1.ietf.org/mailman/listinfo/pwe3
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Florin Balus" <balus@nortelnetworks.com>
Subject: RE: LDP Signalling for PWs
Date: Wed, 15 Dec 2004 06:23:08 -0500
Lines: 1025
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0470084876=="
Cc: pwe3@ietf.org, lmartini@cisco.com, hshah@ciena.com, stbryant@cisco.com
X-From: pwe3-bounces@ietf.org Wed Dec 15 12:36:41 2004
Return-path: <pwe3-bounces@ietf.org>
To: Sasha Vainshtein <Sasha@AXERRA.com>, "'Diego Caviglia'"
	<Diego.Caviglia@marconi.com>, "Cheng-Yin Lee <Cheng-Yin.Lee"
	<Cheng-Yin.Lee@alcatel.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 880a8a97dfe9ef08c1612a7c933970ae
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0470084876==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4E298.77A8D1C5"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4E298.77A8D1C5
Content-Type: text/plain


Before discussing whether or not it is worthwhile to support signaling PW
over LDP interfaces supported on top of PSN tunnels (using basic discovery):
it's worthwhile to keep LDP basic discovery option in scope for the PW
signaling even if it is just for the case of directly connected PEs! 

Why open up a new LDP session using targeted discovery between directly
connected PEs that already discovered each other using a basic discovery
phase? 
Florin

> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Sasha Vainshtein
> Sent: Wednesday, December 15, 2004 3:16 AM
> To: 'Diego Caviglia'; Cheng-Yin Lee <Cheng-Yin.Lee
> Cc: lmartini@cisco.com; pwe3@ietf.org; hshah@ciena.com; 
> stbryant@cisco.com
> Subject: RE: [PWE3] LDP Signalling for PWs
> 
> 
> Diego, Che-Yin and all,
> Please see a brief comment inline.
> 
> Regards,
>                                   Sasha Vainshtein
> email:                         sasha@axerra.com 
> <mailto:sasha@axerra.com> 
> phone:                       +972-3-7569993 (office)
> fax:                            +972-3-6487779
> mobile:                      +972-52-8674833 
> 
> 
> > -----Original Message-----
> > From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
> > Sent: Wednesday, December 15, 2004 9:27 AM
> > To: Cheng-Yin Lee <Cheng-Yin.Lee
> > Cc: pwe3@ietf.org; lmartini@cisco.com; hshah@ciena.com;
> > stbryant@cisco.com
> > Subject: Re: [PWE3] LDP Signalling for PWs
> > 
> > 
> > 
> > Hi Cheng-Yin,
> >                               yes that was I had in mind.
> > 
> > Regards.
> > 
> > Diego
> > 
> > 
> > 
> > Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com> on 14/12/2004 21.57.59
> > 
> > To:    "Shah, Himanshu" <hshah@ciena.com>
> > cc:    "'Luca Martini'" <lmartini@cisco.com>, "'Diego Caviglia'"
> >        <Diego.Caviglia@marconi.com>, "'pwe3 <pwe3'" <pwe3@ietf.org>,
> >        "'Stewart Bryant <stbryant'" <stbryant@cisco.com>
> > 
> > Subject:    Re: [PWE3] LDP Signalling for PWs
> > 
> > 
> > Himanshu,
> > 
> > "Shah, Himanshu" wrote:
> > 
> > > Granted that one could very well do basic
> > > discovery using multicast IP address
> > 
> > over a tunnel/logical IP interface.
> > Agree with the above and I believe it is what Diego suggested.
> > 
> > There seems to be some advantage in using basic discovery
> > over a tunnel in
> > that it is not necessary to configure a PE with the remote PE 
> > addresses for
> > PW signaling ...
> >
> [Sasha] I do not see any advantage here. 
> You know (one of) the IP address(es) of the remote PE
> because you need it to configure the tunnel first.
> And then you must configure the PE to use a specific 
> tunnel LSP leading to the specific peer PE instead. 
> >
> > > and
> > > then exchange PW FECs over this tunnel.
> > >
> > > The only reason for still doing extended
> > > discovery using targetted hello is to
> > > remain interoperable with tons of those PEs
> > > out there who specifically support extended
> > > discovery even when a remote PE is directly
> > > connected via a "tunnel" or a direct link.
> > >
> > 
> > Agree there is no need to change this feature for interoperablility 
> > purposes, as long as the draft does not preclude other options.
> > 
> > Thanks
> > Cheng-Yin
> > 
> > >
> > > IMO.
> > >
> > > himanshu
> > >
> > > > -----Original Message-----
> > > > From: Shah, Himanshu
> > > > Sent: Tuesday, December 14, 2004 12:09 PM
> > > > To: 'Luca Martini'; Diego Caviglia
> > > > Cc: Stewart Bryant <stbryant; pwe3 <pwe3
> > > > Subject: RE: [PWE3] LDP Signalling for PWs
> > > >
> > > >
> > > > Nope.
> > > >
> > > > I meant that router intelligently recognizes that
> > > > logical IP interface is a "tunnel" and hence for targetted LDP 
> > > > purposes, send targetted hello to unicast IP address 
> (which is the 
> > > > tunnel endpoint's IP address).
> > > >
> > > > So if you are doing, topology LDP, you would send
> > > > link hello (a way to have LDP work across RSVP-TE
> > > > cloud using this tunnel) and at the same time if you
> > > > are doing PWE3 signaling, you would also send targetted 
> hello for 
> > > > extended discovery (using unicast IP address).
> > > >
> > > > Hope this clears up.
> > > >
> > > > Either way, I don't think there is any need to change 
> pwe3-control 
> > > > draft, because this would either be an implementation 
> detail or a 
> > > > suggested possibility in applicability draft as Stewart 
> suggested.
> > > >
> > > > /himanshu
> > > >
> > > > > -----Original Message-----
> > > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > > Sent: Tuesday, December 14, 2004 11:36 AM
> > > > > To: Diego Caviglia
> > > > > Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> > > > > Subject: Re: [PWE3] LDP Signalling for PWs
> > > > >
> > > > >
> > > > > Diego,
> > > > >
> > > > > What Himanshu described still involves putting multicast into 
> > > > > the rsvp tunnel. I do not believe that this is the practice 
> > > > > today. It can be done , but there is no significant 
> advantage to
> > > > > just using the
> > > > > extended discovery mechanism. You should keep in mind 
> > that normal
> > > > > behavior is to actually put all the LDP packets into
> > the MPLS LSP
> > > > > between the 2 PEs. ( regardless if it is RSVP sin 
> galled or LDP 
> > > > > signaled ).
> > > > >
> > > > > Luca
> > > > >
> > > > >
> > > > > Diego Caviglia wrote:
> > > > >
> > > > > >Stewart,
> > > > > >                   no problem from my side I see that the ID
> > > > > is number 13
> > > > > >and thus is better to restrict the modify.
> > > > > >
> > > > > >Purpose of my proposal is to state somewhere, an
> > > > > applicability ID could be
> > > > > >good, that is possible, using the procedure Shah depicted in
> > > > > his mail, to
> > > > > >use a tunnel to transport the Hello messages.
> > > > > >
> > > > > >Regards
> > > > > >
> > > > > >Diego
> > > > > >
> > > > > >
> > > > > >
> > > > > >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> > > > > >
> > > > > >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> > > > > >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> > > > > >       <lmartini@cisco.com>
> > > > > >
> > > > > >Subject:    Re: [PWE3] LDP Signalling for PWs
> > > > > >
> > > > > >
> > > > > >We are really trying to get the control draft to RFC, and 
> > > > > >therefore to restrict the changes, and that means 
> taking a hard 
> > > > > >line on anything except protocol design errors.
> > > > > >
> > > > > >This looks more like an applicability issue than a 
> correctness 
> > > > > >issue, and as perhaps we should put it in an applicability 
> > > > > >draft?
> > > > > >
> > > > > >- Stewart
> > > > > >
> > > > > >Diego Caviglia wrote:
> > > > > >
> > > > > >
> > > > > >>Shah,
> > > > > >>              thank for your replay, I agree with you.
> > > > > >>
> > > > > >>May be could be useful to state that in the LDP
> > signalling draft.
> > > > > >>
> > > > > >>What is the feeling of the list on that matter?
> > > > > >>
> > > > > >>Diego
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> > > > > >>
> > > > > >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> > > > > >>       <Diego.Caviglia@marconi.com>
> > > > > >>cc:    pwe3@ietf.org
> > > > > >>
> > > > > >>Subject:    RE: [PWE3] LDP Signalling for PWs
> > > > > >>
> > > > > >>
> > > > > >>If you allow tunnel (lets say RSVP-TE based) to be
> > > > > >>a logical IP i/f, one could conceivably send
> > > > > >>regular LDP hello to discover the remote PE.
> > > > > >>
> > > > > >>This would be no different than if the target
> > > > > >>LDP peer were to be on the direct link (adjacent).
> > > > > >>
> > > > > >>However, in order to differentiate topology based
> > > > > >>LDP (link hello) from PWE3 signaling LDP (targetted),
> > you have to
> > > > > >>set the LDP Hello with t-bit set and send it
> > > > > >>on unicast LDP Peer ID.
> > > > > >>
> > > > > >>Unless of course, you recognize the i/f as tunnel
> > > > > >>and
> > > > > >>1) use the tunnel end-point address as the unicast address
> > > > > >>2) send targetted hello
> > > > > >>
> > > > > >>then you achieve what you intended.
> > > > > >>
> > > > > >>/himanshu
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>>-----Original Message-----
> > > > > >>>From: Luca Martini [mailto:lmartini@cisco.com]
> > > > > >>>Sent: Monday, December 13, 2004 5:08 PM
> > > > > >>>To: Diego Caviglia
> > > > > >>>Cc: pwe3@ietf.org
> > > > > >>>Subject: Re: [PWE3] LDP Signalling for PWs
> > > > > >>>
> > > > > >>>
> > > > > >>>Diego,
> > > > > >>>
> > > > > >>>Extended discovery means that the UDP hello packets to
> > > > > port 646 will
> > > > > >>>have a destination IP address that is the remote
> > PE's address.
> > > > > >>>Basic discovery involves sending the UDP hello packets to
> > > > > port 646 to
> > > > > >>>destination address 224.0.0.2 ( the all routers multicast
> > > > > address ).
> > > > > >>>Packets to address 224.0.0.2 will not travel any
> > further then the
> > > > > >>>immediate neighbors.
> > > > > >>>Normally there is not MPLS FEC for 224.0.0.2
> > > > > >>>
> > > > > >>>Luca
> > > > > >>>
> > > > > >>>
> > > > > >>>Diego Caviglia wrote:
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>>Hi all,
> > > > > >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> > > > > >>>>
> > > > > >>>>
> > > > > >>>that ...The PEs
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>>will establish an LDP session using the Extended Discovery
> > > > > >>>>
> > > > > >>>>
> > > > > >>>.." it is not
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>>clear to me why I can't use basic discovery 
> mechansim given
> > > > > >>>>
> > > > > >>>>
> > > > > >>>that I have
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> > > > > >>>>
> > > > > >>>>
> > > > > >>>tunnel Hello packets
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>>between the LSP peers.
> > > > > >>>>
> > > > > >>>>What am I missing?
> > > > > >>>>
> > > > > >>>>Thanks.
> > > > > >>>>
> > > > > >>>>Regards
> > > > > >>>>
> > > > > >>>>Diego
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>_______________________________________________
> > > > > >>>>pwe3 mailing list
> > > > > >>>>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>>
> > > > > >>>_______________________________________________
> > > > > >>>pwe3 mailing list
> > > > > >>>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>_______________________________________________
> > > > > >>pwe3 mailing list
> > > > > >>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pwe3
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> > 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 

------_=_NextPart_001_01C4E298.77A8D1C5
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.2">
<TITLE>RE: [PWE3] LDP Signalling for PWs</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Before discussing whether or not it is worthwhile to =
support signaling PW over LDP interfaces supported on top of PSN =
tunnels (using basic discovery): it's worthwhile to keep LDP basic =
discovery option in scope for the PW signaling even if it is just for =
the case of directly connected PEs! </FONT></P>

<P><FONT SIZE=3D2>Why open up a new LDP session using targeted =
discovery between directly connected PEs that already discovered each =
other using a basic discovery phase? </FONT></P>

<P><FONT SIZE=3D2>Florin</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: pwe3-bounces@ietf.org [<A =
HREF=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</A>] =
On </FONT>
<BR><FONT SIZE=3D2>&gt; Behalf Of Sasha Vainshtein</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, December 15, 2004 3:16 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Diego Caviglia'; Cheng-Yin Lee =
&lt;Cheng-Yin.Lee</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: lmartini@cisco.com; pwe3@ietf.org; =
hshah@ciena.com; </FONT>
<BR><FONT SIZE=3D2>&gt; stbryant@cisco.com</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [PWE3] LDP Signalling for =
PWs</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Diego, Che-Yin and all,</FONT>
<BR><FONT SIZE=3D2>&gt; Please see a brief comment inline.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Regards,</FONT>
<BR><FONT =
SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; Sasha Vainshtein</FONT>
<BR><FONT SIZE=3D2>&gt; =
email:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; sasha@axerra.com </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;<A =
HREF=3D"mailto:sasha@axerra.com">mailto:sasha@axerra.com</A>&gt; =
</FONT>
<BR><FONT SIZE=3D2>&gt; =
phone:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+972-3-7569993 (office)</FONT>
<BR><FONT SIZE=3D2>&gt; =
fax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; +972-3-6487779</FONT>
<BR><FONT SIZE=3D2>&gt; =
mobile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+972-52-8674833 </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Diego Caviglia [<A =
HREF=3D"mailto:Diego.Caviglia@marconi.com">mailto:Diego.Caviglia@marconi=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Wednesday, December 15, 2004 9:27 =
AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: Cheng-Yin Lee &lt;Cheng-Yin.Lee</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: pwe3@ietf.org; lmartini@cisco.com; =
hshah@ciena.com;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; stbryant@cisco.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: Re: [PWE3] LDP Signalling for =
PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Hi Cheng-Yin,</FONT>
<BR><FONT SIZE=3D2>&gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes that was I had in mind.</FO=
NT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Diego</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cheng-Yin Lee =
&lt;Cheng-Yin.Lee@alcatel.com&gt; on 14/12/2004 21.57.59</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To:&nbsp;&nbsp;&nbsp; &quot;Shah, =
Himanshu&quot; &lt;hshah@ciena.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; cc:&nbsp;&nbsp;&nbsp; &quot;'Luca =
Martini'&quot; &lt;lmartini@cisco.com&gt;, &quot;'Diego =
Caviglia'&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;Diego.Caviglia@marconi.com&gt;, &quot;'pwe3 &lt;pwe3'&quot; =
&lt;pwe3@ietf.org&gt;,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;'Stewart Bryant &lt;stbryant'&quot; =
&lt;stbryant@cisco.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject:&nbsp;&nbsp;&nbsp; Re: [PWE3] LDP =
Signalling for PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Himanshu,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;Shah, Himanshu&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Granted that one could very well do =
basic</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; discovery using multicast IP =
address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; over a tunnel/logical IP interface.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Agree with the above and I believe it is =
what Diego suggested.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; There seems to be some advantage in using =
basic discovery</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; over a tunnel in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that it is not necessary to configure a PE =
with the remote PE </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; addresses for</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; PW signaling ...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; [Sasha] I do not see any advantage here. =
</FONT>
<BR><FONT SIZE=3D2>&gt; You know (one of) the IP address(es) of the =
remote PE</FONT>
<BR><FONT SIZE=3D2>&gt; because you need it to configure the tunnel =
first.</FONT>
<BR><FONT SIZE=3D2>&gt; And then you must configure the PE to use a =
specific </FONT>
<BR><FONT SIZE=3D2>&gt; tunnel LSP leading to the specific peer PE =
instead. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; then exchange PW FECs over this =
tunnel.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; The only reason for still doing =
extended</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; discovery using targetted hello is =
to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; remain interoperable with tons of =
those PEs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; out there who specifically support =
extended</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; discovery even when a remote PE is =
directly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; connected via a &quot;tunnel&quot; or =
a direct link.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Agree there is no need to change this =
feature for interoperablility </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; purposes, as long as the draft does not =
preclude other options.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cheng-Yin</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; IMO.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; From: Shah, Himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Sent: Tuesday, December 14, 2004 =
12:09 PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; To: 'Luca Martini'; Diego =
Caviglia</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Cc: Stewart Bryant &lt;stbryant; =
pwe3 &lt;pwe3</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Subject: RE: [PWE3] LDP =
Signalling for PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Nope.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I meant that router =
intelligently recognizes that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; logical IP interface is a =
&quot;tunnel&quot; and hence for targetted LDP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; purposes, send targetted hello =
to unicast IP address </FONT>
<BR><FONT SIZE=3D2>&gt; (which is the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; tunnel endpoint's IP =
address).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; So if you are doing, topology =
LDP, you would send</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; link hello (a way to have LDP =
work across RSVP-TE</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; cloud using this tunnel) and at =
the same time if you</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; are doing PWE3 signaling, you =
would also send targetted </FONT>
<BR><FONT SIZE=3D2>&gt; hello for </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; extended discovery (using =
unicast IP address).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Hope this clears up.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; Either way, I don't think there =
is any need to change </FONT>
<BR><FONT SIZE=3D2>&gt; pwe3-control </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; draft, because this would either =
be an implementation </FONT>
<BR><FONT SIZE=3D2>&gt; detail or a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; suggested possibility in =
applicability draft as Stewart </FONT>
<BR><FONT SIZE=3D2>&gt; suggested.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; /himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; -----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; From: Luca Martini [<A =
HREF=3D"mailto:lmartini@cisco.com">mailto:lmartini@cisco.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Sent: Tuesday, December 14, =
2004 11:36 AM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; To: Diego Caviglia</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Cc: Stewart Bryant =
&lt;stbryant; Shah, Himanshu; pwe3 &lt;pwe3</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Subject: Re: [PWE3] LDP =
Signalling for PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Diego,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; What Himanshu described =
still involves putting multicast into </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; the rsvp tunnel. I do not =
believe that this is the practice </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; today. It can be done , but =
there is no significant </FONT>
<BR><FONT SIZE=3D2>&gt; advantage to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; just using the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; extended discovery =
mechanism. You should keep in mind </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that normal</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; behavior is to actually put =
all the LDP packets into</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the MPLS LSP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; between the 2 PEs. ( =
regardless if it is RSVP sin </FONT>
<BR><FONT SIZE=3D2>&gt; galled or LDP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; signaled ).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Luca</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; Diego Caviglia =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Stewart,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no problem from my side I see =
that the ID</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; is number 13</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;and thus is better to =
restrict the modify.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Purpose of my proposal =
is to state somewhere, an</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; applicability ID could =
be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;good, that is possible, =
using the procedure Shah depicted in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; his mail, to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;use a tunnel to =
transport the Hello messages.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Regards</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Diego</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Stewart Bryant =
&lt;stbryant@cisco.com&gt; on 14/12/2004 12.21.51</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;To:&nbsp;&nbsp;&nbsp; =
Diego Caviglia &lt;Diego.Caviglia@marconi.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;cc:&nbsp;&nbsp;&nbsp; =
hshah@ciena.com, pwe3 &lt;pwe3@ietf.org&gt;, &quot; =
&lt;lmartini&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;lmartini@cisco.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;Subject:&nbsp;&nbsp;&nbsp; Re: [PWE3] LDP Signalling for PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;We are really trying to =
get the control draft to RFC, and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;therefore to restrict =
the changes, and that means </FONT>
<BR><FONT SIZE=3D2>&gt; taking a hard </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;line on anything except =
protocol design errors.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;This looks more like an =
applicability issue than a </FONT>
<BR><FONT SIZE=3D2>&gt; correctness </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;issue, and as perhaps =
we should put it in an applicability </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;draft?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;- Stewart</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;Diego Caviglia =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;Shah,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; thank for your replay, I agree with you.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;May be could be =
useful to state that in the LDP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; signalling draft.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;What is the feeling =
of the list on that matter?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;Diego</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&quot;Shah, =
Himanshu&quot; &lt;hshah@ciena.com&gt; on 13/12/2004 23.41.52</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;To:&nbsp;&nbsp;&nbsp; &quot;'Luca Martini'&quot; =
&lt;lmartini@cisco.com&gt;, Diego Caviglia</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;Diego.Caviglia@marconi.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;cc:&nbsp;&nbsp;&nbsp; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;Subject:&nbsp;&nbsp;&nbsp; RE: [PWE3] LDP Signalling for =
PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;If you allow tunnel =
(lets say RSVP-TE based) to be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;a logical IP i/f, =
one could conceivably send</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;regular LDP hello =
to discover the remote PE.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;This would be no =
different than if the target</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;LDP peer were to be =
on the direct link (adjacent).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;However, in order =
to differentiate topology based</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;LDP (link hello) =
from PWE3 signaling LDP (targetted),</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; you have to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;set the LDP Hello =
with t-bit set and send it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;on unicast LDP Peer =
ID.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;Unless of course, =
you recognize the i/f as tunnel</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;and</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;1) use the tunnel =
end-point address as the unicast address</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;2) send targetted =
hello</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;then you achieve =
what you intended.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;/himanshu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;-----Original =
Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;From: Luca =
Martini [<A =
HREF=3D"mailto:lmartini@cisco.com">mailto:lmartini@cisco.com</A>]</FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Sent: Monday, =
December 13, 2004 5:08 PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;To: Diego =
Caviglia</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Cc: =
pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Subject: Re: =
[PWE3] LDP Signalling for PWs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Diego,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Extended =
discovery means that the UDP hello packets to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; port 646 will</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;have a =
destination IP address that is the remote</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; PE's address.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Basic discovery =
involves sending the UDP hello packets to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; port 646 to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;destination =
address 224.0.0.2 ( the all routers multicast</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; address ).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Packets to =
address 224.0.0.2 will not travel any</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; further then the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;immediate =
neighbors.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Normally there =
is not MPLS FEC for 224.0.0.2</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Luca</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;Diego Caviglia =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;Hi =
all,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; ID draft-ietf-pwe3-control-protocol-13 states</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;that ...The =
PEs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;will =
establish an LDP session using the Extended Discovery</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;..&quot; it is =
not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;clear to me =
why I can't use basic discovery </FONT>
<BR><FONT SIZE=3D2>&gt; mechansim given</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;that I =
have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;e.g. an =
MPLS tunnel between the two PEs and thus a can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;tunnel Hello =
packets</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;between the =
LSP peers.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;What am I =
missing?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;Thanks.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;Regards</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;Diego</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;pwe3 =
mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;&gt;pwe3@ietf.org <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;&gt;_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;pwe3 mailing =
list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;pwe3@ietf.org =
<A HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; =
&gt;&gt;_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;pwe3 mailing =
list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;pwe3@ietf.org <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3 mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; pwe3@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/pwe3" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/pwe3</A></FONT>=

<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4E298.77A8D1C5--


--===============0470084876==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3

--===============0470084876==--




From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: draft-ietf-pwe3-fragmentation-07.txt - LAST CALL
Date: Wed, 15 Dec 2004 14:28:43 +0000
Lines: 69
References: <41A1F5D1.40308@cisco.com> <09fa01c4d0d7$b4b73c70$749c9ed9@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: andy.malis@tellabs.com, mark@townsley.net, pwe3 <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Wed Dec 15 15:58:51 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Adrian Farrel <adrian@olddog.co.uk>
In-Reply-To: <09fa01c4d0d7$b4b73c70$749c9ed9@Puppy>
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Last call has completed with just these comments.

Please could the authors address these, and as soon as 08
gets in the repository, the chairs will send to IESG
and request publication.

Thanks

Stewart


Adrian Farrel wrote:
> Hi,
> 
> 
>>This is the start of two week last call for
>>draft-ietf-pwe3-fragmentation-07.txt.
>>
>>Last call will end Tuesday 7th December 2004
> 
> 
> Some minor comments (nits).
> Apologies for not having followed the evolution of this draft in detail.
> 
> Adrian
> ===
> The expansion of acronyms at first usage seems patchy.
> - PWE3 is used in the abstract and title and should probably be expanded in both those
> places
> - PWE3, PSN and PDU in section 2
> - CE and PE in section 3
> 
> Section 4
>     use fragmentation MUST be provisioned in the sender.
> s/provisioned/configured/
> 
> Section 5.1
>     Deployments MUST avoid a situation which relies upon a combination
>     of IP and PW fragmentation and reassembly on the same node. Such
> I don't believe you can specify this as a MUST in a protocol spec. The best you can do is
> "SHOULD" and probably you ought to use "should".
> 
> Section 5.4.2
>     MRRU (Maximum Reassembled Receive Unit AVP), attribute number TBD2,
>     is the maximum size in octets of a reassembled frame, including any
>     PW framing, but not including the L2TP encapsulation or L2-specific
>     sublayer. Presence of this AVP signifies the ability to receive PW
>     fragments and reassemble them. Packet fragments MUST NOT be sent to
>     an implementation which has not received this value from its peer
>     in a control message.
> Hopefully the confusion is just mine!
> Do you mean...
>     Packet fragments MUST NOT be sent *by*
>     an implementation which has not received this value from its peer
>     in a control message.
> If you do actually mean what you say then some re-wording to stress this might be helpful.
> 
> Section 7
>     This document does not define any new values for IANA to maintain.
> Looks like the subsequent text defines new values for IANA to maintain?
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: IANA document allocation
Date: Wed, 15 Dec 2004 14:31:25 +0000
Lines: 36
References: <41BE1581.4050902@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Wed Dec 15 16:00:26 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <41BE1581.4050902@cisco.com>
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


I agree with the change that Thomas is proposing

Stewart

Luca Martini wrote:

> WG,
> 
> Thomas Narten, our sponsoring AD, has asked me to change the IANA 
> allocation document to reflect only two kind of allocations:
> IETF consensus , and Expert review.
> 
> This means that I would remove the first come first served ranges, and 
> the vendor specific ranges that are currently defined in the documents.
> 
> My personal opinion is that this is a good change as , "the expert" , 
> can probably still respond quickly ( as opposed to an IETF consensus 
> process ), yet can make sure that there is a good clear description and 
> application for the allocated values.
> 
> I would like to hear from the WG if there are any strong opinions about 
> this change to the IANA allocation documents.
> 
> Thanks.
> Luca
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: pwe3 draft status update
Date: Wed, 15 Dec 2004 14:51:38 +0000
Lines: 61
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-bounces@ietf.org Wed Dec 15 16:07:04 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: pwe3 <pwe3@ietf.org>
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

This is what I think that the current status of our drafts is.

Please could the editors/authors check their drafts and let me
have any corrections.

Thanks

Stewart


draft-ietf-pwe3-arch-07.txt - RFC editor's queue

draft-ietf-pwe3-atm-encap-07.txt - waiting on AD action

draft-ietf-pwe3-cell-transport-01.txt - waiting LC comment resolution

draft-ietf-pwe3-cep-mib-05.txt - work in progress

draft-ietf-pwe3-cesopsn-01.txt - need to check that UDP text is OK

draft-ietf-pwe3-control-protocol-14.txt - sent to IESG today

draft-ietf-pwe3-cw-01 - sent to IESG today

draft-ietf-pwe3-enet-mib-05.txt - work in progress

draft-ietf-pwe3-ethernet-encap-08.txt - waiting on AD action

draft-ietf-pwe3-fcs-retention-02.txt - exits LC tomorrow

draft-ietf-pwe3-fragmentation-07.txt - needs a nits edit goes to IESG

draft-ietf-pwe3-frame-relay-03.txt - needs major edit. Luca has this in hand.

draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt - needs a refresh

draft-ietf-pwe3-iana-allocation-07.txt - waiting on 08

draft-ietf-pwe3-oam-msg-map-01.txt - work in progress

draft-ietf-pwe3-pw-atm-mib-00.txt - work in progress

draft-ietf-pwe3-pw-mib-05.txt - work in progress

draft-ietf-pwe3-pw-mpls-mib-06.txt - work in progress

draft-ietf-pwe3-pw-tc-mib-05.txt - work in progress

draft-ietf-pwe3-satop-01.txt - waiting on AD action

draft-ietf-pwe3-satop-mib-02.txt - work in progress

draft-ietf-pwe3-sonet-09.txt - ready to go to IESG

draft-ietf-pwe3-tdm-mib-01.txt - work in progress

draft-ietf-pwe3-tdm-requirements-05.txt - waiting on AD action

draft-ietf-pwe3-tdmoip-02.txt - need to check that UDP text is OK

draft-ietf-pwe3-vccv-03.txt - work in progress


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: Re: IANA document allocation
Date: Wed, 15 Dec 2004 10:59:52 -0500
Lines: 43
References: <41BE1581.4050902@cisco.com>
 <41C04ABD.1070209@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"'W. Mark Townsley'" <townsley@cisco.com>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Dec 15 17:04:05 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
To: Stewart Bryant <stbryant@cisco.com>
In-Reply-To: <41C04ABD.1070209@cisco.com>
References: <41BE1581.4050902@cisco.com>
 <41C04ABD.1070209@cisco.com>
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Yes, I do have a strong feeling about this.  As a prior "victim" of the 
IANA expert review process, it needs to work much better in practice than 
it has in the past in order for this to be practical.  How are the 
following issues to be addressed:

- Naming the expert or experts

- Replacing the experts following retirement, death, boredom, WG shutdown, etc.

- Assuring timely response from the experts, who after all are volunteers 
and presumably have revenue responsibilities

I would also like to hear more about the supposed evils of FCFS registry 
ranges.  There are many existing IANA registries with FCFS ranges.  Are 
there problems associated with these registries?

Thanks,
Andy

-----------

At 12/15/2004 02:31 PM +0000, Stewart Bryant wrote:

>I agree with the change that Thomas is proposing
>
>Stewart
>
>Luca Martini wrote:
>
>>WG,
>>Thomas Narten, our sponsoring AD, has asked me to change the IANA 
>>allocation document to reflect only two kind of allocations:
>>IETF consensus , and Expert review.
>>This means that I would remove the first come first served ranges, and 
>>the vendor specific ranges that are currently defined in the documents.
>>My personal opinion is that this is a good change as , "the expert" , can 
>>probably still respond quickly ( as opposed to an IETF consensus process 
>>), yet can make sure that there is a good clear description and 
>>application for the allocated values.
>>I would like to hear from the WG if there are any strong opinions about 
>>this change to the IANA allocation documents.
>>Thanks.
>>Luca


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Eric Rosen <erosen@cisco.com>
Subject: Re: IANA document allocation
Date: Thu, 16 Dec 2004 10:56:39 -0500
Lines: 15
References: <41BE1581.4050902@cisco.com>
Reply-To: erosen@cisco.com
Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Thu Dec 16 17:15:24 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
To: Luca Martini <lmartini@cisco.com>
In-reply-to: Your message of Mon, 13 Dec 2004 15:19:45 -0700.
	<41BE1581.4050902@cisco.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


> Thomas Narten, our sponsoring AD, has asked me to change the IANA 
> allocation document to reflect only two kind of allocations: 
> IETF consensus , and Expert review. 

> This means that I would remove the first come first served ranges, and 
> the vendor specific ranges that are currently defined in the documents. 

I strongly oppose this change. 

The FCFS range is there for a valid reason.  Eliminating it merely increases
the  political power  of the  IESG to  suppress innovation,  and  that would
certainly be a move in the wrong direction. 

I also agree with Andy's arguments that the change is not practical. 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Shah, Himanshu" <hshah@ciena.com>
Subject: RE: IANA document allocation
Date: Thu, 16 Dec 2004 11:44:47 -0500
Lines: 38
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Thu Dec 16 17:54:33 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'erosen@cisco.com'" <erosen@cisco.com>, Luca Martini <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

I also oppose to these changes strongly,
for about the same reasons.

/himanshu

> -----Original Message-----
> From: Eric Rosen [mailto:erosen@cisco.com]
> Sent: Thursday, December 16, 2004 10:57 AM
> To: Luca Martini
> Cc: 'W. Mark Townsley'; PWE3 WG (E-mail)
> Subject: Re: [PWE3] IANA document allocation 
> 
> 
> 
> > Thomas Narten, our sponsoring AD, has asked me to change the IANA 
> > allocation document to reflect only two kind of allocations: 
> > IETF consensus , and Expert review. 
> 
> > This means that I would remove the first come first served 
> ranges, and 
> > the vendor specific ranges that are currently defined in 
> the documents. 
> 
> I strongly oppose this change. 
> 
> The FCFS range is there for a valid reason.  Eliminating it 
> merely increases
> the  political power  of the  IESG to  suppress innovation,  
> and  that would
> certainly be a move in the wrong direction. 
> 
> I also agree with Andy's arguments that the change is not practical. 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-cw-01.txt
Date: Thu, 16 Dec 2004 15:55:41 -0500
Lines: 97
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Thu Dec 16 22:29:32 2004
Return-path: <pwe3-bounces@ietf.org>
To: i-d-announce@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Pseudo Wire Emulation Edge to Edge Working Group of the IETF.

	Title		: PWE3 Control Word for use over an MPLS PSN
	Author(s)	: S. Bryant, et al.
	Filename	: draft-ietf-pwe3-cw-01.txt
	Pages		: 8
	Date		: 2004-12-16
	
This document describes the preferred designs of the PWE3 Control 
   Word, and the PW Associated Channel Header. The design of these 
   fields is chosen so that an MPLS LSR performing deep packet 
   inspection will not confuse a PWE3 payload with an IP payload.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org 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-pwe3-cw-01.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-cw-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: CEP-09 - RE: PWE3 Draft Minutes - IETF 61
Date: Fri, 17 Dec 2004 09:33:55 +0000
Lines: 517
References: <008401c4dd79$1ba22910$73db4dd1@lycium.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'David Zelig' <Davidz@corrigent.com>, 'pwe3' <pwe3@ietf.org>,
	'Danny McPherson' <danny@tcb.net>
X-From: pwe3-bounces@ietf.org Fri Dec 17 10:37:20 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Ron Cohen <ronc@lyciumnetworks.com>
In-Reply-To: <008401c4dd79$1ba22910$73db4dd1@lycium.net>
X-Scan-Signature: 5df1f98f3253c63b673ea560243aa58f
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org



Ron Cohen wrote:
> Danny,
> 
> 
>>Then finish the following encaps as they become available
>><draft-ietf-pwe3-frame-relay-03.txt>
>><draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
>><draft-ietf-pwe3-sonet-09.txt>
> 
> 
> Draft-ietf-pwe3-sonet-09 has been submitted in August 2004 and is
> available since then. It includes resolution to all comments received
> via the mailing list after last call. I don't see anything that needs
> finishing here.
> 
> I suggest the plan be to get the TDM requirements to IESG and following
> that put the SONET draft on IESG queue. 

Ron

As soon as we see the feedback on TDM requirements and SATOP
(already in the IESG queue) we will either submit SONET by
return, or request an update from you to reflect the
feedback.

Stewart

> 
> Thanks
> Ron
> 
> 
> 
>>-----Original Message-----
>>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
>>Behalf Of Danny McPherson
>>Sent: Saturday, November 20, 2004 7:34 PM
>>To: pwe3
>>Subject: [PWE3] PWE3 Draft Minutes - IETF 61
>>
>>
>>
>>Folks,
>>Please send me comments and corrections ASAP.
>>
>>Thanks!
>>
>>-danny
>>
>>[snip]
>>
>>1530-1730 Afternoon Session II; Lincoln East
>>
>>Administrivia
>>-------------
>>
>>
>>Chairs: Danny McPherson & Stewart Bryant
>>Minutes: Matthew Bocci
>>Slides are available on pwe3.tcb.net
>>
>>Charter & Draft Status - Stewart Bryant & Danny McPherson
>>---------------------------------------------------------
>>
>>Working on updating charter with ADs. Danny to send email
>>  to list with prposed updated and goals and milestones.
>>
>>Draft status: Stewart
>>
>>Dependencies:
>>Lots of dependencies between drafts. Cannot become RFCs until
>>  dependencies become RFCs. Very important to get this right.
>>  Draft text may change if dependency text changes.
>>
>>Stewart carried out a dependency analysis: this is shown
>>  and looks very complex.
>>
>>This will drive order in which we send documents to
>>  RFC editor.
>>
>>Concerns: Not all normative references are really
>>  normative. Authors need to double check this.  Also
>>  need to make sure all things that should be normative
>>  are called out as such.  Need to check for
>>  informative refs and docs with no normative
>>  references.
>>
>>Base requirements now an RFC.
>>
>>Architecture: list of dependencies, but one may not be
>>  correct. Edits sent to the list. Now in editors queue.
>>  Waiting for fragmentation and L2TP.  This will be RFC.
>>
>>Fragmentation: needs an updated. Encap refs can be
>>  moved to control word references.
>>Andy Malis: Refs to arch can also be changed to refs
>>  to CW.
>>Stewart: not sure this is allowed as arch is
>>  informational.
>>
>>Arch needs frag, needs control, and control doesn't
>>  have dependencies.
>>
>>Luca Martini: Architecture doc should be an informative
>>  reference becasue you define CW in architecture.
>>
>>Stewart: Fragmentation called up 2 bits in CW.
>>Yakov Stein: CW has to be standards track because
>>  of 1st 4 bits
>>
>>Luca Martini: Every documents defines the CW bits
>>  that it uses. CW document is the generic template.
>>
>>Mark Townsley: would be preferable if description
>>  was all in one place.
>>
>>Yakov Stein: important to keep things the way they
>>  are now for expediency
>>
>>Eric Rosen: will confise the IESG
>>
>>Control Word Draft: Most refs to arch refer to sec
>>  5 and could be deleted. These could be changed to
>>  arch.   Will respin and send up.
>>
>>IANA: This is in last call and will be sent out
>>  as soon as this is completed. Needed to set up the
>>  registries. Also lots of requests to stabalise code
>>  points.
>>
>>
>>Control : This is one of the most strategic docs.
>>  Past last call, but keeps getting minor change
>>  requests. This is an urgent gating draft. Need to
>>  take a hard line on this.
>>
>>Luca Martini: Also some editorial nits that need
>>  to be fixed.
>>
>>Stewart: as long as protocol works, need to draw
>>  a line in the sand.
>>
>>ATM and Ethernet: Had 1st go of AD review. A
>>  few edits to fix.
>>
>>Thomas: very close to last call.
>>
>>TDM Reqs in Thomas' queue
>>
>>SONET needs TDM requirements to get AD review
>>  before progressing.
>>
>>SATOP sent to Thomas, but want to resolve UDP
>>  issues first.
>>
>>CESoPSN is informational, but want to resolve
>>  UDP situation too.
>>
>>HDLC encap: Needs a respin to fix refs.
>>  Completed last call.
>>
>>Frame Relay: Needs some TLC. A get well package
>>  has been agreed, and should see a new rev
>>  shortly. Style out of step with rest of
>>  document set. terms need fixing.
>>
>>Yakov Stein: Titles of encap drafts could be
>>  standardised or made more consistent.
>>
>>VCCV: Pressure to move this on. It went to
>>  last call. Dave Allen's comments have not yet
>>  been resolved: should be in rev 04, but this
>>  has not been published yet.  Needs a serious
>>  edit pass, and should be last called. Depends
>>  on BFD and LSP-ping.
>>
>>MIBs: these have a hge cross dependency list.
>>  Need to make sure procedures are published
>>  before.
>>
>>FCS retention: Has standard encap dependencies.
>>  Not in last call yet.
>>
>>Andy Malis: it is ready for last call.
>>
>>Cell transparent mode ready too.
>>Stewart:
>>
>>TDMoIP: Need to resolve UDP issue. Appendix
>>  depends on VCCV. Waiting for comments on 2
>>  OAM issues.
>>
>>OAM messag mapping: Big dependencies, so wait
>>  for others to get out of the way.
>>
>>Plan:
>>1. Get -iana-allocation- to IESG
>>2. Finish -pwe3-cw- and send to IESG
>>3. Edit -control-protocol- to sort out refs
>>   and send to IESG
>>4. Edit ?fragmentation- and then send to IESG
>>At this point we have the platform needed to
>>   progress the encap drafts
>>5) -ethernet-encap-
>>6) -atm-encap-
>>Get TDM requirements to IESG, then the TDM encaps
>>7) -tdm-requirements-
>>8) -satop-
>>9) -cesopsn
>>Then finish the following encaps as they become available
>><draft-ietf-pwe3-frame-relay-03.txt>
>><draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
>><draft-ietf-pwe3-sonet-09.txt>
>>
>>When we have made progress on the above we will
>>  promote the other work to the priority list
>>
>>
>>Architecture draft is in editors queue. Waiting on
>>  frag and L2TP. CW dtaft will be standard. Arch
>>  will be informational.
>>
>>Yakov Stein: why is CW standards track, if it is
>>  not refered to as normative in other docs.
>>
>>Luca Martini; Titles are not consistent. Most say
>>  MPLS/IP, some say just MPLS.... Want comments on
>>  changing all of the titles and making them
>>  consistent.
>>
>>Danny: take to list.
>>
>>Mustapha: is CW is informational, why not just
>>  merge back to the architecture draft.
>>
>>Danny agrees that this is an issue that needs
>>  to be addressed.  Will take offline.
>>
>>
>>
>>PW CW - Stewart & Danny
>>-----------------------
>>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
>>
>>
>>There was lots of work after last IETF. Introduced associated
>>  channel concept. Only use of 001 encapsualtion is for associated
>>  channel for OAM traffic. This needs a formal definition for
>>  associated channel. Suggestions to the list on this. Other
>>  format ID values are available for additional purposes.
>>
>>Yakov Stein: word channel clashes with the use in the
>>  architecture draft Stewart: propose some text to the
>>  mailing list.
>>
>>Channel type will have its own registry. Plan is to grandfather
>>  VCCV value (21). Some errors in the text around IANA
>>  assignment.
>>
>>
>>
>>UDP Statement to ITU - Stewart
>>------------------------------
>>
>>This is one of the most discussed issues. TDM encaps are
>>  being pursued in SG13 as well. UDP encaps are only used by
>>  low speed TDM.  IETF documents are vague on use of UDP.
>>  Need to resolve this before we can go forward. The ITU
>>  started to talk about introducing an expected mechanism
>>  for handling the ports. 5 techniques proposed in
>>  liaison. Extensive comment on this to the list. Unable
>>  to reach consensus. Statement proopsed to the list.
>>  Essentially says PWE3 deals with L2TP, and MPLS
>>  tunnelled over IP. Unable to reach consensus on whether
>>  we need a 3rd method, so unable to give advice to
>>  ITU on where to go next. However, are willing to listen
>>  to proposals on how to carry PW over UDP, but anyway
>>  will need to consider issues such as congestion,
>>  security, and specific application.
>>
>>
>>UDP Encapsulation - Yaakov Stein
>>--------------------------------
>>
>>Service provider model is presented. Emulation is PE to
>>  PE. IWF is located in the PE. AC is natve service.  Encap
>>  sits at the PE. Becomes MPLS at the PE. However, another
>>  model is that the iwf is at the CE. The AC does not
>>  run the native circuit. 3 possibilities:
>>
>>- MPLS AC
>>- UDP/IP AC
>>- other AC possibilities (L2TP, MPLS over IP, native
>>    service over IP using GRE, etc)
>>
>>Lively thread on the list. Over 50 emails from 16 participants.
>>Advantages: UDP/IP familiar to customer base, PW label as UDP
>>  port no. reduces overhead, already extensively deployed for TDM PWs,
>>  reuse of AVT protocols, simplify NAT traversal.
>>
>>Disadvantages: had to provide QoS without c/o pt-pt trail.
>>  Cannot be layer network above UDP. UDP doesn't scale, not
>>  enough port numbers and increases NAT/firewall state. Need
>>  protocol for UDP port signalling. UDP checksum needs to be
>>  calculated. Why a new PW type at a late stage? Security
>>  and congestion control
>>
>>Other comments: need to reply to ITU liaison, PWE charter
>>  aimed at operators, not enterprise customers, wrong, but
>>  how to stop enterprise using it, no consensus, should
>>  divert to AVT, but CE-CE PWs not in AVT charter, UDP
>>  OK for VoIP since adapts an application, some comments
>>  seem to rule out MPLS
>>
>>Presents an rebuttal:
>>- QoS similar to LDP based MPLS or L2TP
>>- Enterprises don't need large number of UDP ports
>>- Scales better than VoIP today
>>- can use manual port provisioning
>>- UDP checksum can simply be set to 0
>>- PW type has been in the charter from day 1
>>- Security: LDP and L2TP protocols are similarly unsafe
>>- Congestion similar to L2TP
>>
>>Proposal:
>>Explicitly limit UDP/IP to enterprises (CE-CE case)
>>- only allow manual provisioning
>>- enterprise responsible to security, congestion avoidance
>>- MPLS should be used if large numberof PWs needed.
>>
>>Stewart: would like comments to help draft ITU response
>>
>>Sahsa: Agrees that there is no sense in developing a
>>  control protocol for UDP PWs. Don't understand what
>>  enterprise PWs means.  If it connects to a class 5
>>  switch, what is it? ALso not sure that admission
>>  control should be up to the customer.
>>
>>Yakov Stein: On congestion avoidance, that link that
>>  is UDP will sufer. SP can discard excess traffic.
>>  The access PW is the point from the CE to the core
>>  network.
>>
>>Sasha: Confused. Are UDP PWs aonly a part of Multi
>>  hop PWs?
>>
>>Yakov: yes
>>
>>Sasha: don't know what to do with MH PWs
>>
>>Eric Rosen: is is too late to remove this TDM from
>>  charter entirely?
>>
>>Stewart: many people want to work on this
>>
>>Eric: if you want to get this though, stop drawing
>>  attention to the problems e.g. NAT, signalling, how
>>  you do multiplexing, seems to need to be manually
>>  configured to interoperate. Solution is to take UDP
>>  out and leave up to SG13, or only have manual
>>  configuration. IESG may still notice this. Better
>>  to leave this in the hands of the ITU.
>>
>>Luca Martini: Be careful and write a good security
>>  section. You are mixing control protocol with data
>>  planes. We are very exposed here.
>>
>>Danny: We are trying to define protocols, not how
>>  and where they are deployed. A lot of concern on
>>  how to scope enterprise vs. service provider here.
>>  We need to assume the protocols defined here will
>>  be deployed in the Internet.
>>
>>
>>Stewart: can either:
>>- not respond
>>- say unable to reach consesus
>>- say we recognise that there are limited cases where
>>UDP would be appropriate, supported by manual
>>  configuration
>>
>>Scott Bradner: You have about a week to honor
>>  tradition and not respond, but it would be
>>  better to send them a response
>>
>>Thomas Narten: be pragmatic and reasonable. If we
>>  don't respond, what will happen?
>>Stewart: we have an opinion as to how UDP is correctly
>>  operated. We have a duty of care.
>>Yakov Stein: reason this was sent was that this was
>>  going to be progressed in SG13. If we cannot reach
>>  consensus, SG13 wil l do what it wants.
>>Scott Bradner: ITU is trying to work with us. We
>>  should cooperate going forward, even if it is to
>>  say that we don't have an opinion. We must not
>>  ignore them.
>>Thomas Narten: AGrees. We can give our thoughts.
>>  We may not like what they want to do, but ghould
>>  explain why.
>>Mark Townsley: could say PWE3 doesn't care. Is there
>>  some work to do at an IAB level on what you do with UDP?
>>
>>Craig White: We do need to send a fairly strong
>>  statement similar to what eric expressed, but
>>  need to be cognisant of the fact that they have
>>  implementations. Need to say that on the Internet,
>>  this is not an appropriate use, but may be
>>  appropriate in a private network. be aware of
>>  issues if it gets connected to Internet at any
>>  time.
>>Scott Bradner: What is magic about UDP in this
>>  context?
>>Stewart: this was not an issue until it was noticed
>>  that we needed a port assignment protocol
>>Scott Bradner: This working group was formed with
>>  the assumption of UDP and MPLS
>>Craig: congestion avoidance problem with UDP
>>Scott: no real difference
>>Yakov Stein: ITU would be happy to hear that we only
>>  want manual configuration.
>>Luca Martini: We also have an implementation of this.
>>  Bottom line is that a better design is L2TPv3 and
>>  this should be used instead. IETF thinks this is
>>  a better idea.
>>Eric Rosen: 2 issues: signalling. Suggestion that
>>  you could use LDP, with port numbers instead of
>>  labels. DO you use source or destination port?
>>  What about NATs? not sure we can come to
>>  consensus, except you need to manually configure
>>  it.
>>
>>Stewart: We do not recommend UDP, but L2TP. If
>>  you use UDP, you so manual config.
>>
>>Yakov Stein: why?
>>
>>Stewart: Responds saying we recommend that you
>>  only do manual configuration of the ports.
>>
>>Mark Townsley: ...and if you want to do
>>  automatic configuration, use L2TPv3 Issue with
>>  UDP is that it can cause problems for NATs. Some
>>  of the arguments made on the list are significant.
>>
>>Yakov Stein: why does RTP group get away with this?
>>
>>Shasha: Neither MPLS nor L2TP are suitable for
>>  NAT traversal. Could say: No signalling protocol,
>>  should not be used in NAT environment. Agree
>>  that there is substantially more VoIP and so
>>  we could say that UDP already used for VoIP
>>  sessions with operational success.
>>
>>Mark Townsley: L2TPv3 deigned to run over UDP.
>>  Every NAT knows how to do L2TPv3 as in RFC2661
>>Thomas Narten: Liaison doesn't ask if it is a
>>  good or a bad thing. It asks how to do port
>>  number stuff. We should answer the question.
>>
>>Stewart: Our advice is that this is only done
>>  in a manually configured mode, and anything
>>  more advanced should be made as a proposal
>>  to the PWE3 group.
>>
>>Yakov Stein: pick one and send it back already!
>>  Pick manually configured, but use L2TPv3 for
>>  signalled
>>
>>Consensus around this. Propose to the mailing
>>  list by Friday afternoon.
>>
>>
>>
>>PW Multi-Hop Requirements - Luca Martini
>>----------------------------------------
>>
>>Presents the outcome of the requirements team.
>>
>>Last IETF was a discussion about PW stitching. Since
>>  then, we had a long drawn out email thread. Concluded
>>  we needed a requirement document.
>>
>>Document not achieved by this IETF deadline.
>>
>>Met face to face. We are regrouping, and trying to
>>  produce a draft by the end of november
>>  concentrating on requirements for this technology.
>>  This will guide if we need to do any more protocol
>>  work.
>>
>>
>>Open Microphone
>>---------------
>>
>>Luca Martini: What is the state of the rechartering?
>>Danny: Will provide an update on the charter, goals
>>  and milestones on the mailing list.
>>
>>Meeting Adjourned
>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: CEP-09 - RE: PWE3 Draft Minutes - IETF 61
Date: Fri, 17 Dec 2004 07:02:14 -0800
Lines: 553
References: <41C2A803.6090907@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: 'pwe3' <pwe3@ietf.org>, 'David Zelig' <Davidz@corrigent.com>,
	'Danny McPherson' <danny@tcb.net>
X-From: pwe3-bounces@ietf.org Fri Dec 17 16:19:43 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Stewart Bryant'" <stbryant@cisco.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <41C2A803.6090907@cisco.com>
X-OriginalArrivalTime: 17 Dec 2004 15:01:08.0914 (UTC)
	FILETIME=[3D85C920:01C4E449]
X-Scan-Signature: b271b9c4fc51b08326fa0949e61c0156
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Stewart,

> As soon as we see the feedback on TDM requirements and SATOP
> (already in the IESG queue) we will either submit SONET by
> return, or request an update from you to reflect the
> feedback.

I don't see any reason to wait for feedback on SATOP. I don't see ATM
emulation draft waiting for feedback on FR emulation draft. If SATOP is
already on the IESG queue I suggest to put CEP on that queue as well. 

Thanks
Ron




> -----Original Message-----
> From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> Behalf Of Stewart Bryant
> Sent: Friday, December 17, 2004 1:34 AM
> To: Ron Cohen
> Cc: 'David Zelig'; 'pwe3'; 'Danny McPherson'
> Subject: Re: CEP-09 - RE: [PWE3] PWE3 Draft Minutes - IETF 61
> 
> 
> 
> 
> Ron Cohen wrote:
> > Danny,
> > 
> > 
> >>Then finish the following encaps as they become available
> >><draft-ietf-pwe3-frame-relay-03.txt>
> >><draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
> >><draft-ietf-pwe3-sonet-09.txt>
> > 
> > 
> > Draft-ietf-pwe3-sonet-09 has been submitted in August 2004 and is
> > available since then. It includes resolution to all 
> comments received
> > via the mailing list after last call. I don't see anything 
> that needs
> > finishing here.
> > 
> > I suggest the plan be to get the TDM requirements to IESG 
> and following
> > that put the SONET draft on IESG queue. 
> 
> Ron
> 
> As soon as we see the feedback on TDM requirements and SATOP
> (already in the IESG queue) we will either submit SONET by
> return, or request an update from you to reflect the
> feedback.
> 
> Stewart
> 
> > 
> > Thanks
> > Ron
> > 
> > 
> > 
> >>-----Original Message-----
> >>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On 
> >>Behalf Of Danny McPherson
> >>Sent: Saturday, November 20, 2004 7:34 PM
> >>To: pwe3
> >>Subject: [PWE3] PWE3 Draft Minutes - IETF 61
> >>
> >>
> >>
> >>Folks,
> >>Please send me comments and corrections ASAP.
> >>
> >>Thanks!
> >>
> >>-danny
> >>
> >>[snip]
> >>
> >>1530-1730 Afternoon Session II; Lincoln East
> >>
> >>Administrivia
> >>-------------
> >>
> >>
> >>Chairs: Danny McPherson & Stewart Bryant
> >>Minutes: Matthew Bocci
> >>Slides are available on pwe3.tcb.net
> >>
> >>Charter & Draft Status - Stewart Bryant & Danny McPherson
> >>---------------------------------------------------------
> >>
> >>Working on updating charter with ADs. Danny to send email
> >>  to list with prposed updated and goals and milestones.
> >>
> >>Draft status: Stewart
> >>
> >>Dependencies:
> >>Lots of dependencies between drafts. Cannot become RFCs until
> >>  dependencies become RFCs. Very important to get this right.
> >>  Draft text may change if dependency text changes.
> >>
> >>Stewart carried out a dependency analysis: this is shown
> >>  and looks very complex.
> >>
> >>This will drive order in which we send documents to
> >>  RFC editor.
> >>
> >>Concerns: Not all normative references are really
> >>  normative. Authors need to double check this.  Also
> >>  need to make sure all things that should be normative
> >>  are called out as such.  Need to check for
> >>  informative refs and docs with no normative
> >>  references.
> >>
> >>Base requirements now an RFC.
> >>
> >>Architecture: list of dependencies, but one may not be
> >>  correct. Edits sent to the list. Now in editors queue.
> >>  Waiting for fragmentation and L2TP.  This will be RFC.
> >>
> >>Fragmentation: needs an updated. Encap refs can be
> >>  moved to control word references.
> >>Andy Malis: Refs to arch can also be changed to refs
> >>  to CW.
> >>Stewart: not sure this is allowed as arch is
> >>  informational.
> >>
> >>Arch needs frag, needs control, and control doesn't
> >>  have dependencies.
> >>
> >>Luca Martini: Architecture doc should be an informative
> >>  reference becasue you define CW in architecture.
> >>
> >>Stewart: Fragmentation called up 2 bits in CW.
> >>Yakov Stein: CW has to be standards track because
> >>  of 1st 4 bits
> >>
> >>Luca Martini: Every documents defines the CW bits
> >>  that it uses. CW document is the generic template.
> >>
> >>Mark Townsley: would be preferable if description
> >>  was all in one place.
> >>
> >>Yakov Stein: important to keep things the way they
> >>  are now for expediency
> >>
> >>Eric Rosen: will confise the IESG
> >>
> >>Control Word Draft: Most refs to arch refer to sec
> >>  5 and could be deleted. These could be changed to
> >>  arch.   Will respin and send up.
> >>
> >>IANA: This is in last call and will be sent out
> >>  as soon as this is completed. Needed to set up the
> >>  registries. Also lots of requests to stabalise code
> >>  points.
> >>
> >>
> >>Control : This is one of the most strategic docs.
> >>  Past last call, but keeps getting minor change
> >>  requests. This is an urgent gating draft. Need to
> >>  take a hard line on this.
> >>
> >>Luca Martini: Also some editorial nits that need
> >>  to be fixed.
> >>
> >>Stewart: as long as protocol works, need to draw
> >>  a line in the sand.
> >>
> >>ATM and Ethernet: Had 1st go of AD review. A
> >>  few edits to fix.
> >>
> >>Thomas: very close to last call.
> >>
> >>TDM Reqs in Thomas' queue
> >>
> >>SONET needs TDM requirements to get AD review
> >>  before progressing.
> >>
> >>SATOP sent to Thomas, but want to resolve UDP
> >>  issues first.
> >>
> >>CESoPSN is informational, but want to resolve
> >>  UDP situation too.
> >>
> >>HDLC encap: Needs a respin to fix refs.
> >>  Completed last call.
> >>
> >>Frame Relay: Needs some TLC. A get well package
> >>  has been agreed, and should see a new rev
> >>  shortly. Style out of step with rest of
> >>  document set. terms need fixing.
> >>
> >>Yakov Stein: Titles of encap drafts could be
> >>  standardised or made more consistent.
> >>
> >>VCCV: Pressure to move this on. It went to
> >>  last call. Dave Allen's comments have not yet
> >>  been resolved: should be in rev 04, but this
> >>  has not been published yet.  Needs a serious
> >>  edit pass, and should be last called. Depends
> >>  on BFD and LSP-ping.
> >>
> >>MIBs: these have a hge cross dependency list.
> >>  Need to make sure procedures are published
> >>  before.
> >>
> >>FCS retention: Has standard encap dependencies.
> >>  Not in last call yet.
> >>
> >>Andy Malis: it is ready for last call.
> >>
> >>Cell transparent mode ready too.
> >>Stewart:
> >>
> >>TDMoIP: Need to resolve UDP issue. Appendix
> >>  depends on VCCV. Waiting for comments on 2
> >>  OAM issues.
> >>
> >>OAM messag mapping: Big dependencies, so wait
> >>  for others to get out of the way.
> >>
> >>Plan:
> >>1. Get -iana-allocation- to IESG
> >>2. Finish -pwe3-cw- and send to IESG
> >>3. Edit -control-protocol- to sort out refs
> >>   and send to IESG
> >>4. Edit ?fragmentation- and then send to IESG
> >>At this point we have the platform needed to
> >>   progress the encap drafts
> >>5) -ethernet-encap-
> >>6) -atm-encap-
> >>Get TDM requirements to IESG, then the TDM encaps
> >>7) -tdm-requirements-
> >>8) -satop-
> >>9) -cesopsn
> >>Then finish the following encaps as they become available
> >><draft-ietf-pwe3-frame-relay-03.txt>
> >><draft-ietf-pwe3-hdlc-ppp-encap-mpls-03.txt>
> >><draft-ietf-pwe3-sonet-09.txt>
> >>
> >>When we have made progress on the above we will
> >>  promote the other work to the priority list
> >>
> >>
> >>Architecture draft is in editors queue. Waiting on
> >>  frag and L2TP. CW dtaft will be standard. Arch
> >>  will be informational.
> >>
> >>Yakov Stein: why is CW standards track, if it is
> >>  not refered to as normative in other docs.
> >>
> >>Luca Martini; Titles are not consistent. Most say
> >>  MPLS/IP, some say just MPLS.... Want comments on
> >>  changing all of the titles and making them
> >>  consistent.
> >>
> >>Danny: take to list.
> >>
> >>Mustapha: is CW is informational, why not just
> >>  merge back to the architecture draft.
> >>
> >>Danny agrees that this is an issue that needs
> >>  to be addressed.  Will take offline.
> >>
> >>
> >>
> >>PW CW - Stewart & Danny
> >>-----------------------
> >>http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-00.txt
> >>
> >>
> >>There was lots of work after last IETF. Introduced associated
> >>  channel concept. Only use of 001 encapsualtion is for associated
> >>  channel for OAM traffic. This needs a formal definition for
> >>  associated channel. Suggestions to the list on this. Other
> >>  format ID values are available for additional purposes.
> >>
> >>Yakov Stein: word channel clashes with the use in the
> >>  architecture draft Stewart: propose some text to the
> >>  mailing list.
> >>
> >>Channel type will have its own registry. Plan is to grandfather
> >>  VCCV value (21). Some errors in the text around IANA
> >>  assignment.
> >>
> >>
> >>
> >>UDP Statement to ITU - Stewart
> >>------------------------------
> >>
> >>This is one of the most discussed issues. TDM encaps are
> >>  being pursued in SG13 as well. UDP encaps are only used by
> >>  low speed TDM.  IETF documents are vague on use of UDP.
> >>  Need to resolve this before we can go forward. The ITU
> >>  started to talk about introducing an expected mechanism
> >>  for handling the ports. 5 techniques proposed in
> >>  liaison. Extensive comment on this to the list. Unable
> >>  to reach consensus. Statement proopsed to the list.
> >>  Essentially says PWE3 deals with L2TP, and MPLS
> >>  tunnelled over IP. Unable to reach consensus on whether
> >>  we need a 3rd method, so unable to give advice to
> >>  ITU on where to go next. However, are willing to listen
> >>  to proposals on how to carry PW over UDP, but anyway
> >>  will need to consider issues such as congestion,
> >>  security, and specific application.
> >>
> >>
> >>UDP Encapsulation - Yaakov Stein
> >>--------------------------------
> >>
> >>Service provider model is presented. Emulation is PE to
> >>  PE. IWF is located in the PE. AC is natve service.  Encap
> >>  sits at the PE. Becomes MPLS at the PE. However, another
> >>  model is that the iwf is at the CE. The AC does not
> >>  run the native circuit. 3 possibilities:
> >>
> >>- MPLS AC
> >>- UDP/IP AC
> >>- other AC possibilities (L2TP, MPLS over IP, native
> >>    service over IP using GRE, etc)
> >>
> >>Lively thread on the list. Over 50 emails from 16 participants.
> >>Advantages: UDP/IP familiar to customer base, PW label as UDP
> >>  port no. reduces overhead, already extensively deployed 
> for TDM PWs,
> >>  reuse of AVT protocols, simplify NAT traversal.
> >>
> >>Disadvantages: had to provide QoS without c/o pt-pt trail.
> >>  Cannot be layer network above UDP. UDP doesn't scale, not
> >>  enough port numbers and increases NAT/firewall state. Need
> >>  protocol for UDP port signalling. UDP checksum needs to be
> >>  calculated. Why a new PW type at a late stage? Security
> >>  and congestion control
> >>
> >>Other comments: need to reply to ITU liaison, PWE charter
> >>  aimed at operators, not enterprise customers, wrong, but
> >>  how to stop enterprise using it, no consensus, should
> >>  divert to AVT, but CE-CE PWs not in AVT charter, UDP
> >>  OK for VoIP since adapts an application, some comments
> >>  seem to rule out MPLS
> >>
> >>Presents an rebuttal:
> >>- QoS similar to LDP based MPLS or L2TP
> >>- Enterprises don't need large number of UDP ports
> >>- Scales better than VoIP today
> >>- can use manual port provisioning
> >>- UDP checksum can simply be set to 0
> >>- PW type has been in the charter from day 1
> >>- Security: LDP and L2TP protocols are similarly unsafe
> >>- Congestion similar to L2TP
> >>
> >>Proposal:
> >>Explicitly limit UDP/IP to enterprises (CE-CE case)
> >>- only allow manual provisioning
> >>- enterprise responsible to security, congestion avoidance
> >>- MPLS should be used if large numberof PWs needed.
> >>
> >>Stewart: would like comments to help draft ITU response
> >>
> >>Sahsa: Agrees that there is no sense in developing a
> >>  control protocol for UDP PWs. Don't understand what
> >>  enterprise PWs means.  If it connects to a class 5
> >>  switch, what is it? ALso not sure that admission
> >>  control should be up to the customer.
> >>
> >>Yakov Stein: On congestion avoidance, that link that
> >>  is UDP will sufer. SP can discard excess traffic.
> >>  The access PW is the point from the CE to the core
> >>  network.
> >>
> >>Sasha: Confused. Are UDP PWs aonly a part of Multi
> >>  hop PWs?
> >>
> >>Yakov: yes
> >>
> >>Sasha: don't know what to do with MH PWs
> >>
> >>Eric Rosen: is is too late to remove this TDM from
> >>  charter entirely?
> >>
> >>Stewart: many people want to work on this
> >>
> >>Eric: if you want to get this though, stop drawing
> >>  attention to the problems e.g. NAT, signalling, how
> >>  you do multiplexing, seems to need to be manually
> >>  configured to interoperate. Solution is to take UDP
> >>  out and leave up to SG13, or only have manual
> >>  configuration. IESG may still notice this. Better
> >>  to leave this in the hands of the ITU.
> >>
> >>Luca Martini: Be careful and write a good security
> >>  section. You are mixing control protocol with data
> >>  planes. We are very exposed here.
> >>
> >>Danny: We are trying to define protocols, not how
> >>  and where they are deployed. A lot of concern on
> >>  how to scope enterprise vs. service provider here.
> >>  We need to assume the protocols defined here will
> >>  be deployed in the Internet.
> >>
> >>
> >>Stewart: can either:
> >>- not respond
> >>- say unable to reach consesus
> >>- say we recognise that there are limited cases where
> >>UDP would be appropriate, supported by manual
> >>  configuration
> >>
> >>Scott Bradner: You have about a week to honor
> >>  tradition and not respond, but it would be
> >>  better to send them a response
> >>
> >>Thomas Narten: be pragmatic and reasonable. If we
> >>  don't respond, what will happen?
> >>Stewart: we have an opinion as to how UDP is correctly
> >>  operated. We have a duty of care.
> >>Yakov Stein: reason this was sent was that this was
> >>  going to be progressed in SG13. If we cannot reach
> >>  consensus, SG13 wil l do what it wants.
> >>Scott Bradner: ITU is trying to work with us. We
> >>  should cooperate going forward, even if it is to
> >>  say that we don't have an opinion. We must not
> >>  ignore them.
> >>Thomas Narten: AGrees. We can give our thoughts.
> >>  We may not like what they want to do, but ghould
> >>  explain why.
> >>Mark Townsley: could say PWE3 doesn't care. Is there
> >>  some work to do at an IAB level on what you do with UDP?
> >>
> >>Craig White: We do need to send a fairly strong
> >>  statement similar to what eric expressed, but
> >>  need to be cognisant of the fact that they have
> >>  implementations. Need to say that on the Internet,
> >>  this is not an appropriate use, but may be
> >>  appropriate in a private network. be aware of
> >>  issues if it gets connected to Internet at any
> >>  time.
> >>Scott Bradner: What is magic about UDP in this
> >>  context?
> >>Stewart: this was not an issue until it was noticed
> >>  that we needed a port assignment protocol
> >>Scott Bradner: This working group was formed with
> >>  the assumption of UDP and MPLS
> >>Craig: congestion avoidance problem with UDP
> >>Scott: no real difference
> >>Yakov Stein: ITU would be happy to hear that we only
> >>  want manual configuration.
> >>Luca Martini: We also have an implementation of this.
> >>  Bottom line is that a better design is L2TPv3 and
> >>  this should be used instead. IETF thinks this is
> >>  a better idea.
> >>Eric Rosen: 2 issues: signalling. Suggestion that
> >>  you could use LDP, with port numbers instead of
> >>  labels. DO you use source or destination port?
> >>  What about NATs? not sure we can come to
> >>  consensus, except you need to manually configure
> >>  it.
> >>
> >>Stewart: We do not recommend UDP, but L2TP. If
> >>  you use UDP, you so manual config.
> >>
> >>Yakov Stein: why?
> >>
> >>Stewart: Responds saying we recommend that you
> >>  only do manual configuration of the ports.
> >>
> >>Mark Townsley: ...and if you want to do
> >>  automatic configuration, use L2TPv3 Issue with
> >>  UDP is that it can cause problems for NATs. Some
> >>  of the arguments made on the list are significant.
> >>
> >>Yakov Stein: why does RTP group get away with this?
> >>
> >>Shasha: Neither MPLS nor L2TP are suitable for
> >>  NAT traversal. Could say: No signalling protocol,
> >>  should not be used in NAT environment. Agree
> >>  that there is substantially more VoIP and so
> >>  we could say that UDP already used for VoIP
> >>  sessions with operational success.
> >>
> >>Mark Townsley: L2TPv3 deigned to run over UDP.
> >>  Every NAT knows how to do L2TPv3 as in RFC2661
> >>Thomas Narten: Liaison doesn't ask if it is a
> >>  good or a bad thing. It asks how to do port
> >>  number stuff. We should answer the question.
> >>
> >>Stewart: Our advice is that this is only done
> >>  in a manually configured mode, and anything
> >>  more advanced should be made as a proposal
> >>  to the PWE3 group.
> >>
> >>Yakov Stein: pick one and send it back already!
> >>  Pick manually configured, but use L2TPv3 for
> >>  signalled
> >>
> >>Consensus around this. Propose to the mailing
> >>  list by Friday afternoon.
> >>
> >>
> >>
> >>PW Multi-Hop Requirements - Luca Martini
> >>----------------------------------------
> >>
> >>Presents the outcome of the requirements team.
> >>
> >>Last IETF was a discussion about PW stitching. Since
> >>  then, we had a long drawn out email thread. Concluded
> >>  we needed a requirement document.
> >>
> >>Document not achieved by this IETF deadline.
> >>
> >>Met face to face. We are regrouping, and trying to
> >>  produce a draft by the end of november
> >>  concentrating on requirements for this technology.
> >>  This will guide if we need to do any more protocol
> >>  work.
> >>
> >>
> >>Open Microphone
> >>---------------
> >>
> >>Luca Martini: What is the state of the rechartering?
> >>Danny: Will provide an update on the charter, goals
> >>  and milestones on the mailing list.
> >>
> >>Meeting Adjourned
> >>
> >>
> >>_______________________________________________
> >>pwe3 mailing list
> >>pwe3@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/pwe3
> >>
> > 
> > 
> > 
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> > 
> > 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 14:47:08 -0500
Lines: 31
References: <41BE1581.4050902@cisco.com>
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Fri Dec 17 20:51:16 2004
Return-path: <pwe3-bounces@ietf.org>
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: Message from lmartini@cisco.com
	of "Mon, 13 Dec 2004 15:19:45 MST." <41BE1581.4050902@cisco.com> 
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

> Thomas Narten, our sponsoring AD, has asked me to change the IANA 
> allocation document to reflect only two kind of allocations:
> IETF consensus , and Expert review.

Well, I wouldn't put it quite this way... At the IETF meeting, I had a
conversation with the chairs after having skimmed the IANA
document. What is currently in the document made little sense
(IMO). E.g., it mentions "vendor-specific" ranges, but I don't know
what that means. And stuff like:

     PW Type values 1 through 63 are to be assigned by IANA using the
     "IETF Consensus" policy defined in RFC2434. PW Type values 64
     through 127 are to be assigned by IANA,

also made little sense to me. What is the point of having an "IETF
Consensus" range if one could also just get a code point via FCFS?

After some discussion, we came around to "expert review" providing the
most reasonable balance between "some review needed, to prevent
completely bogus assignments" vs. "expert can quickly say OK for
reasonable requests".

In anycase, I think the WG should discuss and decide what the right
thing to do here is.

Indeed, one of the things that might be good to have words about in
the IANA document (if Expert Review is chosen) is what type of
requests are expected to be approved, and what sort of review is
needed prior to granting a request.

Thomas


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 15:03:08 -0500
Lines: 41
References: <200412171947.iBHJl8rQ025212@rotala.raleigh.ibm.com>
X-From: pwe3-bounces@ietf.org Fri Dec 17 21:09:14 2004
Return-path: <pwe3-bounces@ietf.org>
To: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
In-Reply-To: Message from narten@us.ibm.com of "Fri, 17 Dec 2004 14:47:08 EST."
	<200412171947.iBHJl8rQ025212@rotala.raleigh.ibm.com> 
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

> Indeed, one of the things that might be good to have words about in
> the IANA document (if Expert Review is chosen) is what type of
> requests are expected to be approved, and what sort of review is
> needed prior to granting a request.

To followup, e.g., it wouldn't be unreasonable for the expert to ask
the WG and for the WG to have to agree to an assignment (if that is
what the WG wants).

For another perspective,  look at RFC 3575 "IANA Considerations for
RADIUS", section 2.1, which says: 

2.1.  Recommended Registration Policies

   For registration requests where a Designated Expert should be
   consulted, the responsible IESG area director should appoint the
   Designated Expert.  The intention is that any allocation will be
   accompanied by a published RFC.  However, the Designated Expert can
   approve allocations once it seems clear that an RFC will be
   published, allowing for the allocation of values prior to the
   document being approved for publication as an RFC.  The Designated
   Expert will post a request to the AAA WG mailing list (or a successor
   designated by the Area Director) for comment and review, including an
   Internet-Draft.  Before a period of 30 days has passed, the
   Designated Expert will either approve or deny the registration
   request, publish a notice of the decision to the AAA WG mailing list
   or its successor, and inform IANA of its decision.  A denial notice
   must be justified by an explanation and, in the cases where it is
   possible, concrete suggestions on how the request can be modified so
   as to become acceptable.

The point is, it would be good to provide some general guidelines for
what is an acceptable request and what is not, so both the requestor
and the expert are on the same page. But it is also best not to get
too explicit, since flexibility is needed to handle each request on a
case-by-case basis and to deal with things that come up that might not
have been thought through at the time the document was written. That
is, give the expert general guidelines, but then give him/her the
authority to do the right thing.

Thomas


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 15:27:06 -0500
Lines: 58
References: <200412172003.iBHK38Es025294@rotala.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Fri Dec 17 21:37:24 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
In-Reply-To: <200412172003.iBHK38Es025294@rotala.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.619)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


On Dec 17, 2004, at 3:03 PM, Thomas Narten wrote:

>> Indeed, one of the things that might be good to have words about in
>> the IANA document (if Expert Review is chosen) is what type of
>> requests are expected to be approved, and what sort of review is
>> needed prior to granting a request.
>
> To followup, e.g., it wouldn't be unreasonable for the expert to ask
> the WG and for the WG to have to agree to an assignment (if that is
> what the WG wants).

	What happens if no working group exists at that time?

	--Tom



> For another perspective,  look at RFC 3575 "IANA Considerations for
> RADIUS", section 2.1, which says:
>
> 2.1.  Recommended Registration Policies
>
>    For registration requests where a Designated Expert should be
>    consulted, the responsible IESG area director should appoint the
>    Designated Expert.  The intention is that any allocation will be
>    accompanied by a published RFC.  However, the Designated Expert can
>    approve allocations once it seems clear that an RFC will be
>    published, allowing for the allocation of values prior to the
>    document being approved for publication as an RFC.  The Designated
>    Expert will post a request to the AAA WG mailing list (or a 
> successor
>    designated by the Area Director) for comment and review, including 
> an
>    Internet-Draft.  Before a period of 30 days has passed, the
>    Designated Expert will either approve or deny the registration
>    request, publish a notice of the decision to the AAA WG mailing list
>    or its successor, and inform IANA of its decision.  A denial notice
>    must be justified by an explanation and, in the cases where it is
>    possible, concrete suggestions on how the request can be modified so
>    as to become acceptable.
>
> The point is, it would be good to provide some general guidelines for
> what is an acceptable request and what is not, so both the requestor
> and the expert are on the same page. But it is also best not to get
> too explicit, since flexibility is needed to handle each request on a
> case-by-case basis and to deal with things that come up that might not
> have been thought through at the time the document was written. That
> is, give the expert general guidelines, but then give him/her the
> authority to do the right thing.
>
> Thomas
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 15:32:12 -0500
Lines: 15
References: <054B7244-506A-11D9-B1D3-000D93AD480A@cisco.com>
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Fri Dec 17 22:26:52 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
In-Reply-To: Message from tnadeau@cisco.com of "Fri, 17 Dec 2004 15:27:06 EST."
	<054B7244-506A-11D9-B1D3-000D93AD480A@cisco.com> 
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

> 	What happens if no working group exists at that time?

The expert then decides is one answer. But in practice, the mailing
list may be around, in which case asking the list would presumably
still be reasonable.

Having an expert allows for flexibility to handle cases like the WG
going away.

The bottom line is that the expert is supposed to be responsive to the
community and deal with requests in a timely fashion. If that isn't
working (for whatever reason), one can raise the issue with the IESG
so that corrective steps can be taken (e.g., find a new expert).

Thomas


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Eric Rosen <erosen@cisco.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 15:38:11 -0500
Lines: 27
References: <200412171947.iBHJl8rQ025212@rotala.raleigh.ibm.com>
Reply-To: erosen@cisco.com
Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	"'W. Mark Townsley'" <townsley@cisco.com>,
	Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Fri Dec 17 22:46:44 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
To: Thomas Narten <narten@us.ibm.com>
In-reply-to: Your message of Fri, 17 Dec 2004 14:47:08 -0500.
	<200412171947.iBHJl8rQ025212@rotala.raleigh.ibm.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Thomas> What is the  point of having an "IETF Consensus"  range if one could
Thomas> also just get a code point via FCFS? 

That's a good  question.  What it means in practice  is that assignments are
made FCFS until the FCFS space  gets used up; thereafter assignments need to
be made  via IETF  consensus.  New developments  generally get  shipped with
codepoints from this  space, and then keep those  codepoints even after they
get standardized.

Thomas> it  mentions "vendor-specific" ranges,  but I  don't know  what that
Thomas> means

I think  most documents refer to  this as "private use",  i.e., it basically
means "not  to be  assigned by IANA".   In general,  this only gets  used if
there  is no FCFS  space.  However,  values in  this space  may also  end up
becoming  de facto  standards.  Private  use values  could also  be  used if
someone  wanted to  deploy  a proprietary  and non-interoperable  extension,
though I'm sure that no one would ever want to do that.

One thing that might be rational would be to make the FCFS space bigger, but
to also leave a reserved space.  If  at some point we actually look to be in
danger of  running out of FCFS space,  we can then decide  whether to extend
the FCFS space. 

I do not  at all like the idea  of "expert review", as it  creates a process
which  is all too  easily subverted  by cronyism  and political  agendas, or
which might just fail to deliver results.


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 14:49:18 -0500
Lines: 48
References: <6.2.0.14.2.20041215105159.044603c0@mail.comcast.net>
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	Luca Martini <lmartini@cisco.com>, "PWE3 WG \(E-mail\)" <pwe3@ietf.org>,
	Stewart Bryant <stbryant@cisco.com>
X-From: pwe3-bounces@ietf.org Fri Dec 17 22:47:03 2004
Return-path: <pwe3-bounces@ietf.org>
To: "Andrew G. Malis" <andymalis@comcast.net>
In-Reply-To: Message from andymalis@comcast.net of "Wed,
	15 Dec 2004 10:59:52 EST."
	<6.2.0.14.2.20041215105159.044603c0@mail.comcast.net> 
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

"Andrew G. Malis" <andymalis@comcast.net> writes:

> Yes, I do have a strong feeling about this.  As a prior "victim" of the 
> IANA expert review process, it needs to work much better in practice than 
> it has in the past in order for this to be practical.  How are the 
> following issues to be addressed:

I'll agree that the review process has not always worked as it should
in the past. But I think things are better now.

> - Naming the expert or experts

IESG names them (per RFC 2434). In practice, we ask the WG chairs and
after some discussion, someone gets picked, typically by mutual
agreement.

> - Replacing the experts following retirement, death, boredom, WG
    shutdown, etc.

IESG can replace at anytime (per 2434). Bottom line: if the expert
isn't being responsive, someone needs to raise the issue (i.e., to
make us aware) and then appropriate followup is needed.

> - Assuring timely response from the experts, who after all are volunteers 
> and presumably have revenue responsibilities

Same as above. Unresponsive experts should get replaced.

> I would also like to hear more about the supposed evils of FCFS registry 
> ranges.  There are many existing IANA registries with FCFS ranges.  Are 
> there problems associated with these registries?

It really depends on the registry. For some, FCFS is really fine. For
others, you really want some  review, to pushback on requests that
aren't appropriate. There are lots of reasons (bad idea, damaging to
the protocol or internet, duplicates existing work, etc.)

Some of this is discussed in RFC 2434 (actually,
draft-narten-iana-considerations-rfc2434bis-01.txt would be a better
starting point).

Also, there is much discussion on the problem of "unreviewed
extensions" (which can be a problem with FCFS registries) discussed in
draft-iesg-vendor-extensions-02.txt.

Comments/discussion on either draft would of course be most welcome.

Thomas


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: IANA document allocation
Date: Fri, 17 Dec 2004 21:46:37 +0000
Lines: 21
References: <200412171949.iBHJnIK7025225@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Fri Dec 17 23:18:22 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200412171949.iBHJnIK7025225@rotala.raleigh.ibm.com>
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

The text that we put in the latest version of CW

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-cw-01.txt

was

 >5.   IANA considerations
 >
 >   IANA needs to set up a registry of "PW Associated Channel Type".
 >   These are 16-bit values. IANA requests for the allocation of values
 >   from the PW Associated Channel Type REQUIRE expert review.
 >
 >   Initial PW Associated Channel Type value allocations are specified
 >   in "IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)"
 >   [IANA], and should be incorporated by IANA into the registry.


The draft will be updated, if necessary, to reflect the
consensus at the end of this discussion.

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-0
	0.txt
Date: Fri, 17 Dec 2004 15:39:31 +0200
Lines: 110
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "'jdrake@calient.net '" <jdrake@calient.net>,
	"'philippe.niger@francetelecom.com '" <philippe.niger@francetelecom.com>,
	"'ckoc@zteusa.com '" <ckoc@zteusa.com>,
	"'yaakov_s@rad.com '" <yaakov_s@rad.com>,
	Alik Shimelmits <alik@AXERRA.com>,
	"'busschbach@lucent.com '" <busschbach@lucent.com>,
	"'nabil.n.bitar@verizon.com '" <nabil.n.bitar@verizon.com>,
	''Luca Martini' ' <lmartini@cisco.com>,
	"'peter.j.willis@bt.com '" <peter.j.willis@bt.com>,
	"'richard.spencer@bt.com '" <richard.spencer@bt.com>,
	"'dimitri.papadimitriou@alcatel.be '" <dimitri.papadimitriou@alcatel.be>,
	"'simon.delord@francetelecom.com '" <simon.delord@francetelecom.com>,
	"'PWE3 WG \(E-mail\) '" <pwe3@ietf.org>,
	"'rahul@juniper.net '" <rahul@juniper.net>,
	"'neil.2.harrison@bt.com '" <neil.2.harrison@bt.com>,
	Sharon Galtzur <sharon@AXERRA.com>,
	'Ping Pan ' <ppan@hammerheadsystems.com>,
	"'dbrungard@att.com '"
X-From: pwe3-bounces@ietf.org Sat Dec 18 16:08:35 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'Peter Willis '" <pjw@ip-engineering.bt.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
X-Mailman-Approved-At: Sat, 18 Dec 2004 10:00:48 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Peter and all,
Please see a brief comment inline below.
Regards,
               Sasha

-----Original Message-----
From: Peter Willis
To: Sasha Vainshtein
Cc: 'Luca Martini'; philippe.niger@francetelecom.com; ckoc@zteusa.com;
yaakov_s@rad.com; Alik Shimelmits; busschbach@lucent.com; dbrungard@att.com;
nabil.n.bitar@verizon.com; peter.j.willis@bt.com; richard.spencer@bt.com;
dimitri.papadimitriou@alcatel.be; simon.delord@francetelecom.com; PWE3 WG
(E-mail); rahul@juniper.net; neil.2.harrison@bt.com; Sharon Galtzur; Ping
Pan; jdrake@calient.net; Matthew.Bocci@alcatel.co.uk
Sent: 12/16/2004 7:05 PM
Subject: Re: [PWE3] Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-0
0.txt 


> 2. Requirement (mentioned by several people in the discussion on the
DT
> list)
> for "one-touch single-ended provisioning of an MH-PE". The draft in
question
> presents a weaker form of this requirement (Section 6.5., item ii),
speaking
> about
> an option to signal a MH-PW using a minimal number of OSS touches,
where 
> the minimal number" may be greater than 1. But if we tend for
single-touch
> provisioning, the following logic looks correct to me:
> * The device to be touched MUST be one of the U-PEs
> * It MUST receive the information containg unambiguous identification
of the
> remote 
> peer end point, including unambiguous identification of the remote
U-PE
> 
> Of course, one could argue that unambiguous identification of the
remote
> U-PE
> does not have to be its IP address. But in real life, what other
unambiguous
> identification of devices do we have? Phone numbers?
> >

We should be clear whether the 1 touch single-ended provisioning of
an MH-PW applies to both the intra-operator & inter-operator cases? 
If it only applied to the intra-operator case then the solution may be
simpler.

[Sasha] I agree. And it seems to me that the one-touch single-ended
provisioning has been mentioned wrt the intra-provider use case
(cannot check that since I cannot access my archive at the moment).

If we want 1 touch single-ended provisioning for the inter-operator case
then I think we would want an AAA mechanism on the S-PEs (but we can
abstract that and just say the S-PEs have a policy mechanism for 
policing the set-up of MH-PWs) and then I'm not sure whether 
authentication of the signalling entities between operators is sufficient
or whether each MH-PW needs its own AAA. I suspect the latter makes reusing
PPP/radius like mechanisms easier?

[Sasha] A nice touch - on at least two counts:
- seems like we need an AAA section in the requirements document, and
  this was not touched so far
- I would expect the SPs to push strongly for reuse of the existing
  AAA architecture and methods; but then I do not work for an SP.
  
If you look at PSTN style VoIP interconnects (see
http://www.msforum.org/) 
you'll see examples of how IP connections are set-up between operators
where 
the IP addresses of the infrastructures are hidden and a common
identifier 
(the telephone number) is used to set-up the connection. I can see
similar 
requirements for inter-operator MH-PWs, i.e. Operators will want to hide
the 
IP addresses of their infrastructure (signalling & media connection
points) 
from each other. Of course there is no reason why the MH-PW attachement
points 
could not use IP addresses (I'd be ambitious and suggest IPv6 addresses)
that 
have nothing to do with the IP addresses used for the control planes &
the 
network infrastructure. The solution here will look very complex
(something 
like the MSF solution?) so the requirement for single-ended provisioning
of 
PWs inter-operator must be really strong to justify this.

[Sasha] I am not sure this example is valid - for two reasons:
- U-PEs are not (or not always) part of the operators' infrastructure,
  so hiding their IP addresses may be not really necessary
- Telephony has its own identification (phone numbers) already
  in place,and this identification is essentialfor the service (you
  do not dial an IP address, at least not today!), so the justtification
  for the translation mechanism between two identifications is easy.
  Such a system does not exist in the case of MH-PWs, and developing it
  involves,IMHO, substantial cost...
But I agree that the requirement level for one-touch single-ended
provisioning probably differs for the intra-operator and inter-operator
cases.

Regards,
Peter Willis,
Office of the BT Group CTO.


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Chris Metz <chmetz@cisco.com>
Subject: Re: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Sun, 19 Dec 2004 11:01:59 -0800
Lines: 13
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1> <41BF6E7F.6080108@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: jdrake@calient.net, philippe.niger@francetelecom.com, ckoc@zteusa.com,
	yaakov_s@rad.com, Alik Shimelmits <alik@AXERRA.com>,
	busschbach@lucent.com, dbrungard@att.com,
	nabil.n.bitar@verizon.com, peter.j.willis@bt.com,
	richard.spencer@bt.com, dimitri.papadimitriou@alcatel.be,
	simon.delord@francetelecom.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, rahul@juniper.net,
	neil.2.harrison@bt.com, Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>,
	Sasha Vainshtein <Sasha@AXERRA.com>, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Sun Dec 19 21:16:02 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-Sender: chmetz@mail1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <41BF6E7F.6080108@cisco.com>
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
X-Mailman-Approved-At: Sun, 19 Dec 2004 15:08:42 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi-
I think we are missing a specific USE CASE from section 5.
Consider the case where we have each PE pair
run a client control plane function. This control plane
function drives creation (and deletion) of corresponding PW segments
between each PE pair. Rather then terminate
and process the PW payload at each intermediate PE
(between the source and target U-PEs),
we splice the preceding and succeeding PW segments
together ... so that the data plane at the intermediate
PE(s) becomes a PW label swap operation.

Cheers ...


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Chris Metz <chmetz@cisco.com>
Subject: Re: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Sun, 19 Dec 2004 11:26:25 -0800
Lines: 24
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1> <41BF6E7F.6080108@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: jdrake@calient.net, philippe.niger@francetelecom.com, ckoc@zteusa.com,
	yaakov_s@rad.com, Alik Shimelmits <alik@AXERRA.com>,
	busschbach@lucent.com, dbrungard@att.com,
	nabil.n.bitar@verizon.com, peter.j.willis@bt.com,
	richard.spencer@bt.com, dimitri.papadimitriou@alcatel.be,
	simon.delord@francetelecom.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, rahul@juniper.net,
	neil.2.harrison@bt.com, Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>,
	Sasha Vainshtein <Sasha@AXERRA.com>, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Sun Dec 19 21:17:11 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-Sender: chmetz@mail1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Luca Martini <lmartini@cisco.com>
In-Reply-To: <41BF6E7F.6080108@cisco.com>
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
X-Scan-Signature: 93238566e09e6e262849b4f805833007
X-Mailman-Approved-At: Sun, 19 Dec 2004 15:09:01 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

At 03:51 PM 12/14/2004 -0700, Luca Martini wrote:
<snip>


>>    1. I think that the following statement in the "Use Cases" section
>>       requires clarification: "*At a minimum PW control
>>       channel establishment requires knowledge of and reachability to
>>       the remote (ultimate) PE IP address*". I understand that
>>       *reachability* of the remote ultuimate PE IP address may be
>>       problematic in some cases; but do we really envision the case
>>       when a PE can be set up without the one of the ultimate PEs
>>       possessing any *knowledge* about IP address of its remote peer?

Yes ... especially if the MH-PW setup scheme is created in such a way
so that the source U-PE does not need to know the IP address of the
remote U-PE. This may be for variety of reasons including security, scale, 
etc.

We would need to include TAI that identifies the desired AC on the remote
U-PE.

Cheers ...

<snip>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: dimitri papadimitriou <dpapadimitriou@psg.com>
Subject: Re: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Mon, 20 Dec 2004 00:09:14 +0100
Lines: 40
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<4.3.2.7.2.20041219105919.029da370@mail1.cisco.com>
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel.be
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: philippe.niger@francetelecom.com, ckoc@zteusa.com, yaakov_s@rad.com,
	Alik Shimelmits <alik@AXERRA.com>, busschbach@lucent.com,
	nabil.n.bitar@verizon.com, Luca Martini <lmartini@cisco.com>,
	peter.j.willis@bt.com, richard.spencer@bt.com,
	Sasha Vainshtein <Sasha@AXERRA.com>,
	dimitri.papadimitriou@alcatel.be, simon.delord@francetelecom.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, rahul@juniper.net,
	neil.2.harrison@bt.com, Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>, jdrake@calient.net,
	dbrungard@att.com, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Mon Dec 20 14:21:04 2004
Return-path: <pwe3-bounces@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
To: Chris Metz <chmetz@cisco.com>
In-Reply-To: <4.3.2.7.2.20041219105919.029da370@mail1.cisco.com>
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 20 Dec 2004 08:18:58 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


PW segment definition (which is not a SH-PW) was meant to deliver such 
capability since S-PE are agnostic to both PW payload its associated 
control so that only ingress/egress U-PEs have to terminate and process 
such payload

note: the confusion comes from the following sentence where (SH-PW) 
appears in parenthis
"     - Multi-hop PW (MH-PW).  A static or dynamically configured set of
        two or more contiguous PW segments (SH-PW) that behave and
        function as a single point-to-point PW. Each end of a MH-PW by
        definition MUST terminate on a U-PE."

also a SH-PW is constituted by a single PW segment and a MH-PW is 
constituted by more than one PW segment (one between the ingress U-PE 
and the S-PE, one between each S-PE pair and one between the last S-PE 
and the egress U-PE)

Chris Metz wrote:
> Hi-
> I think we are missing a specific USE CASE from section 5.
> Consider the case where we have each PE pair
> run a client control plane function. This control plane
> function drives creation (and deletion) of corresponding PW segments
> between each PE pair. Rather then terminate
> and process the PW payload at each intermediate PE
> (between the source and target U-PEs),
> we splice the preceding and succeeding PW segments
> together ... so that the data plane at the intermediate
> PE(s) becomes a PW label swap operation.
> 
> Cheers ...
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> .
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: dimitri papadimitriou <dpapadimitriou@psg.com>
Subject: Re: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Mon, 20 Dec 2004 00:34:24 +0100
Lines: 46
References: <AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>	<AF5018AC03D1D411ABB70002A5091326015E1960@TLV1>
	<4.3.2.7.2.20041219110918.01f9c4b0@mail1.cisco.com>
Reply-To: dpapadimitriou@psg.com, dimitri.papadimitriou@alcatel.be
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: philippe.niger@francetelecom.com, ckoc@zteusa.com, yaakov_s@rad.com,
	Alik Shimelmits <alik@AXERRA.com>, busschbach@lucent.com,
	nabil.n.bitar@verizon.com, Luca Martini <lmartini@cisco.com>,
	peter.j.willis@bt.com, richard.spencer@bt.com,
	Sasha Vainshtein <Sasha@AXERRA.com>,
	dimitri.papadimitriou@alcatel.be, simon.delord@francetelecom.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, rahul@juniper.net,
	neil.2.harrison@bt.com, Sharon Galtzur <sharon@AXERRA.com>,
	Ping Pan <ppan@hammerheadsystems.com>, jdrake@calient.net,
	dbrungard@att.com, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Mon Dec 20 14:22:04 2004
Return-path: <pwe3-bounces@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
To: Chris Metz <chmetz@cisco.com>
In-Reply-To: <4.3.2.7.2.20041219110918.01f9c4b0@mail1.cisco.com>
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 20 Dec 2004 08:19:17 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

per section 5.2.1. of PW control: "The Attachment Identifier must be 
unique in the context of the PE router in which the Forwarder resides. 
The combination <PE router, AI> must be globally unique."

therefore, either the PE router is used (leaving AC selection being a 
local process) or both are explicitly specified as part of the request 
or one identifies the ACs using their mapping in the CP as IP addresses 
since a reachable point can be translated with an IP prefix (at the 
control plane level) whereas the corr. data plane end-point does not 
have to terminate IP packets

Chris Metz wrote:

> At 03:51 PM 12/14/2004 -0700, Luca Martini wrote:
> <snip>
> 
> 
>>>    1. I think that the following statement in the "Use Cases" section
>>>       requires clarification: "*At a minimum PW control
>>>       channel establishment requires knowledge of and reachability to
>>>       the remote (ultimate) PE IP address*". I understand that
>>>       *reachability* of the remote ultuimate PE IP address may be
>>>       problematic in some cases; but do we really envision the case
>>>       when a PE can be set up without the one of the ultimate PEs
>>>       possessing any *knowledge* about IP address of its remote peer?
> 
> 
> Yes ... especially if the MH-PW setup scheme is created in such a way
> so that the source U-PE does not need to know the IP address of the
> remote U-PE. This may be for variety of reasons including security, 
> scale, etc.
> 
> We would need to include TAI that identifies the desired AC on the remote
> U-PE.
> 
> Cheers ...
> 
> <snip>
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> .
> 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Sun, 19 Dec 2004 21:38:30 -0000
Lines: 85
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: jdrake@calient.net, philippe.niger@francetelecom.com, ckoc@zteusa.com,
	yaakov_s@rad.com, alik@AXERRA.com, busschbach@lucent.com,
	nabil.n.bitar@verizon.com, peter.j.willis@bt.com,
	richard.spencer@bt.com, dimitri.papadimitriou@alcatel.be,
	simon.delord@francetelecom.com, pwe3@ietf.org, rahul@juniper.net,
	dbrungard@att.com, sharon@AXERRA.com, ppan@hammerheadsystems.com,
	Sasha@AXERRA.com, Matthew.Bocci@alcatel.co.uk
X-From: pwe3-bounces@ietf.org Mon Dec 20 14:24:25 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Re: I-D
	ACTION:draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTl/W7+SgqrueL/RpikMBwm5ZBU2AACB6Fg
To: <chmetz@cisco.com>, <lmartini@cisco.com>
X-OriginalArrivalTime: 19 Dec 2004 21:38:32.0116 (UTC)
	FILETIME=[16012F40:01C4E613]
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 20 Dec 2004 08:19:45 -0500
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Chris,
>=20
> Hi-
> I think we are missing a specific USE CASE from section 5.=20
> Consider the case where we have each PE pair run a client=20
> control plane function. This control plane function drives=20
> creation (and deletion) of corresponding PW segments between=20
> each PE pair. Rather then terminate and process the PW=20
> payload at each intermediate PE (between the source and=20
> target U-PEs), we splice the preceding and succeeding PW=20
> segments together ... so that the data plane at the intermediate
> PE(s) becomes a PW label swap operation.
>=20
I believe you are, perhaps not intentionally, raising a very important
point here that has troubled me and many folks in BT for a long time.  I
can summarise this as follows:

When we have a topology of nodes and links in some layer network that we
wish to route a path across, there is an (unconscious?) assumption that
the link-connections (ie the 'things' that connect adjacent nodes
together) in THIS layer network really exist, ie they are ALREADY
provisioned in some manner between the nodes in THIS layer network.
However, these link-connections are provided by trails (ie end-end
paths) in some LOWER layer network (eg E1 PDH or VC12 SDH trails).  In
turn, the link connections of this lower layer network are provided by
trails in an EVEN LOWER lower layer layer network (eg SDH VC4).  This
behaviour (ie a client layer link-connection is provided by a server
layer trail) recurses until we hit the duct.

We can restate this in a different way (and I am tailoring this for the
PW case, but it can be generalised to any case of nested layer
networks):

-	For the client of the PW to work it requires a level N (MH PW)
LSP to be in place
-	For the level N (MH PW) LSP to work it requires a level N-1 LSP
to be in place (for EACH link/segment of the MH PW LSP as per the
recursion principle noted previously)
-	For the level N-1 LSP to work it requires a level N-2 LSP to be
in place (for EACH link/segment of the level N-1 LSP).....this can
continue for as many LSPs as there are nested, but let's stop the LSP
nesting here
-	For the level N-2 LSP to work it requires a (let's say) SDH VC4
path to be in place...again for EACH of its link connections, but let's
take this recursive/general requirement to be as-read from now on
-	For the SDH VC4 path to work its requires a STM MS/RS path to be
in place
-	For the STM MS/RS path to work it requires a fiber to be in
place
-	For the fiber to work it requires a duct to be in place.
-	For the duct to be in place it requires we get a back-hoe out
and dig some trenches!

In other words we cannot create 'topology on the fly'......a level or
pre-provisioning is a key requirement/assumption here.  But yet in MPLS
this assumes this is indeed possible (a similar issue occurs in GMPLS
when folks talk of 'TE links' and 'FAs').  Clearly this is a nonsense.
It's not a problem in MPLS as-is *provided* we only ever have 2 levels
of LSP AND  the top level LSP is not actually a true networked LSP but
merely a p2p 1-hop entity where the label proxies for a client
identifier function (which is precisely what we find with rfc2547 VPNs
and SH PWs).  However, for MH PWs each link-connection here (ie between
PW switching capable nodes) requires a 'regular' lower level LSP to be
in place before traffic can be sent, or indeed MH PW LSP routes to be
calculated with any valid sense...and this requires even lower level
trails to be in place, etc, etc, until we get to the duct.

I think you are assuming here Chris that the (PW) client control-plane
(or more accurately the client layer network across ALL planes) is
independent of the server MPLS (PW) control-plane (network)....and this
is a 'good thing' as one can can now functionally decouple the client
(whatever it is) and server (MPLS) layer networks.  Can't do this in
MPLS per se however......currently there is no good way of creating a
'functional breakwater' between 2 MPLS layer networks except by PWs and
some other technology.  As I noted, this is not a problem when we only
have a single layer network in MPLS and a higher level LSP is not really
a 'networked LSP' but a 1-hop client ID proxy.  MH PWs start to change
this picture however.....and so does client/server i/w between 2
operators A and B say, who both have MPLS networks and where operator A
wants to lease transport capacity off operator B but neither operator
wants to functionally peer with each other.

I think we have some interesting issues brewing here.

regards, Neil


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Thomas Narten <narten@us.ibm.com>
Subject: Re: IANA document allocation
Date: Mon, 20 Dec 2004 10:53:23 -0500
Lines: 48
References: <200412172038.iBHKcBHS017601@rtp-core-1.cisco.com>
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Mon Dec 20 17:03:52 2004
Return-path: <pwe3-bounces@ietf.org>
To: erosen@cisco.com
In-Reply-To: Message from erosen@cisco.com of "Fri, 17 Dec 2004 15:38:11 EST."
	<200412172038.iBHKcBHS017601@rtp-core-1.cisco.com> 
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

> I think  most documents refer to  this as "private use",  i.e., it basically
> means "not  to be  assigned by IANA".

"Private use" is a defined term in 2434. If that is what is meant, it
is better to use standard terminology.

> In general, this only gets used if there is no FCFS space.  However,
> values in this space may also end up becoming de facto standards.
> Private use values could also be used if someone wanted to deploy a
> proprietary and non-interoperable extension, though I'm sure that no
> one would ever want to do that.

"private use" is also not really for deploying proprietary stuff, at
least not for a _vendor_ to do so. It is intended that an end-user can
do this (within an environment they do control, so they can assure
that numbers won't conflict). (If a vendor needs to deploy something,
we need to make sure that they use unique numbers so that the numbers
don't conflict with those used by some other vendor/purpose.)

> One thing that might be rational would be to make the FCFS space
> bigger, but to also leave a reserved space.  If at some point we
> actually look to be in danger of running out of FCFS space, we can
> then decide whether to extend the FCFS space.

I think one really needs to look at each name space individually and
consider such things as:

 - is the space large enough to accomodate likely usage?

Separately, one needs to consider how much review is necessary. For
some name spaces, I agree that little or no review is needed. But for
others, it is. Again, please have a look at
draft-iesg-vendor-extensions-02.txt, as there is much experience with
problems caused by unreviewed extensions.

> I do not at all like the idea of "expert review", as it creates a
> process which is all too easily subverted by cronyism and political
> agendas, or which might just fail to deliver results.

Well, if you are not willing to have _any_ review, there is a risk
that bogus extensions will get defined and deployed that negatively
impact other deployments, the overall pwe3 architecture, etc. IMO,
expert review provides the reasonable balance between no review (which
has caused significant problems with some protocols) vs. an even
higher bar, such as requiring an RFC publication, (or even higher,
requiring a standards track document).

Thomas


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: LDP Signalling for PWs
Date: Mon, 20 Dec 2004 10:01:18 -0700
Organization: Cisco Systems
Lines: 409
References: <9671A92C3C8B5744BC97F855F7CB646502835E26@zcarhxm1.corp.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Cheng-Yin Lee <Cheng-Yin.Lee" <Cheng-Yin.Lee@alcatel.com>, pwe3@ietf.org,
	Sasha Vainshtein <Sasha@AXERRA.com>, hshah@ciena.com, stbryant@cisco.com
X-From: pwe3-bounces@ietf.org Mon Dec 20 18:24:40 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Florin Balus <balus@nortelnetworks.com>
In-Reply-To: <9671A92C3C8B5744BC97F855F7CB646502835E26@zcarhxm1.corp.nortel.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 819069d28e3cfe534e22b502261ce83f
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

There is only one possible LDP session between 2 PEs.
Basic discovery does not apply to PWs. The PW end point MUST be known 
and configured, there therefore is no advantage in having basic discovery.

This is my last e-mail on this thread.
Luca


Florin Balus wrote:

>
> Before discussing whether or not it is worthwhile to support signaling 
> PW over LDP interfaces supported on top of PSN tunnels (using basic 
> discovery): it's worthwhile to keep LDP basic discovery option in 
> scope for the PW signaling even if it is just for the case of directly 
> connected PEs!
>
> Why open up a new LDP session using targeted discovery between 
> directly connected PEs that already discovered each other using a 
> basic discovery phase?
>
> Florin
>
> > -----Original Message-----
> > From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On
> > Behalf Of Sasha Vainshtein
> > Sent: Wednesday, December 15, 2004 3:16 AM
> > To: 'Diego Caviglia'; Cheng-Yin Lee <Cheng-Yin.Lee
> > Cc: lmartini@cisco.com; pwe3@ietf.org; hshah@ciena.com;
> > stbryant@cisco.com
> > Subject: RE: [PWE3] LDP Signalling for PWs
> >
> >
> > Diego, Che-Yin and all,
> > Please see a brief comment inline.
> >
> > Regards,
> >                                   Sasha Vainshtein
> > email:                         sasha@axerra.com
> > <mailto:sasha@axerra.com>
> > phone:                       +972-3-7569993 (office)
> > fax:                            +972-3-6487779
> > mobile:                      +972-52-8674833
> >
> >
> > > -----Original Message-----
> > > From: Diego Caviglia [mailto:Diego.Caviglia@marconi.com]
> > > Sent: Wednesday, December 15, 2004 9:27 AM
> > > To: Cheng-Yin Lee <Cheng-Yin.Lee
> > > Cc: pwe3@ietf.org; lmartini@cisco.com; hshah@ciena.com;
> > > stbryant@cisco.com
> > > Subject: Re: [PWE3] LDP Signalling for PWs
> > >
> > >
> > >
> > > Hi Cheng-Yin,
> > >                               yes that was I had in mind.
> > >
> > > Regards.
> > >
> > > Diego
> > >
> > >
> > >
> > > Cheng-Yin Lee <Cheng-Yin.Lee@alcatel.com> on 14/12/2004 21.57.59
> > >
> > > To:    "Shah, Himanshu" <hshah@ciena.com>
> > > cc:    "'Luca Martini'" <lmartini@cisco.com>, "'Diego Caviglia'"
> > >        <Diego.Caviglia@marconi.com>, "'pwe3 <pwe3'" <pwe3@ietf.org>,
> > >        "'Stewart Bryant <stbryant'" <stbryant@cisco.com>
> > >
> > > Subject:    Re: [PWE3] LDP Signalling for PWs
> > >
> > >
> > > Himanshu,
> > >
> > > "Shah, Himanshu" wrote:
> > >
> > > > Granted that one could very well do basic
> > > > discovery using multicast IP address
> > >
> > > over a tunnel/logical IP interface.
> > > Agree with the above and I believe it is what Diego suggested.
> > >
> > > There seems to be some advantage in using basic discovery
> > > over a tunnel in
> > > that it is not necessary to configure a PE with the remote PE
> > > addresses for
> > > PW signaling ...
> > >
> > [Sasha] I do not see any advantage here.
> > You know (one of) the IP address(es) of the remote PE
> > because you need it to configure the tunnel first.
> > And then you must configure the PE to use a specific
> > tunnel LSP leading to the specific peer PE instead.
> > >
> > > > and
> > > > then exchange PW FECs over this tunnel.
> > > >
> > > > The only reason for still doing extended
> > > > discovery using targetted hello is to
> > > > remain interoperable with tons of those PEs
> > > > out there who specifically support extended
> > > > discovery even when a remote PE is directly
> > > > connected via a "tunnel" or a direct link.
> > > >
> > >
> > > Agree there is no need to change this feature for interoperablility
> > > purposes, as long as the draft does not preclude other options.
> > >
> > > Thanks
> > > Cheng-Yin
> > >
> > > >
> > > > IMO.
> > > >
> > > > himanshu
> > > >
> > > > > -----Original Message-----
> > > > > From: Shah, Himanshu
> > > > > Sent: Tuesday, December 14, 2004 12:09 PM
> > > > > To: 'Luca Martini'; Diego Caviglia
> > > > > Cc: Stewart Bryant <stbryant; pwe3 <pwe3
> > > > > Subject: RE: [PWE3] LDP Signalling for PWs
> > > > >
> > > > >
> > > > > Nope.
> > > > >
> > > > > I meant that router intelligently recognizes that
> > > > > logical IP interface is a "tunnel" and hence for targetted LDP
> > > > > purposes, send targetted hello to unicast IP address
> > (which is the
> > > > > tunnel endpoint's IP address).
> > > > >
> > > > > So if you are doing, topology LDP, you would send
> > > > > link hello (a way to have LDP work across RSVP-TE
> > > > > cloud using this tunnel) and at the same time if you
> > > > > are doing PWE3 signaling, you would also send targetted
> > hello for
> > > > > extended discovery (using unicast IP address).
> > > > >
> > > > > Hope this clears up.
> > > > >
> > > > > Either way, I don't think there is any need to change
> > pwe3-control
> > > > > draft, because this would either be an implementation
> > detail or a
> > > > > suggested possibility in applicability draft as Stewart
> > suggested.
> > > > >
> > > > > /himanshu
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Luca Martini [mailto:lmartini@cisco.com]
> > > > > > Sent: Tuesday, December 14, 2004 11:36 AM
> > > > > > To: Diego Caviglia
> > > > > > Cc: Stewart Bryant <stbryant; Shah, Himanshu; pwe3 <pwe3
> > > > > > Subject: Re: [PWE3] LDP Signalling for PWs
> > > > > >
> > > > > >
> > > > > > Diego,
> > > > > >
> > > > > > What Himanshu described still involves putting multicast into
> > > > > > the rsvp tunnel. I do not believe that this is the practice
> > > > > > today. It can be done , but there is no significant
> > advantage to
> > > > > > just using the
> > > > > > extended discovery mechanism. You should keep in mind
> > > that normal
> > > > > > behavior is to actually put all the LDP packets into
> > > the MPLS LSP
> > > > > > between the 2 PEs. ( regardless if it is RSVP sin
> > galled or LDP
> > > > > > signaled ).
> > > > > >
> > > > > > Luca
> > > > > >
> > > > > >
> > > > > > Diego Caviglia wrote:
> > > > > >
> > > > > > >Stewart,
> > > > > > >                   no problem from my side I see that the ID
> > > > > > is number 13
> > > > > > >and thus is better to restrict the modify.
> > > > > > >
> > > > > > >Purpose of my proposal is to state somewhere, an
> > > > > > applicability ID could be
> > > > > > >good, that is possible, using the procedure Shah depicted in
> > > > > > his mail, to
> > > > > > >use a tunnel to transport the Hello messages.
> > > > > > >
> > > > > > >Regards
> > > > > > >
> > > > > > >Diego
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >Stewart Bryant <stbryant@cisco.com> on 14/12/2004 12.21.51
> > > > > > >
> > > > > > >To:    Diego Caviglia <Diego.Caviglia@marconi.com>
> > > > > > >cc:    hshah@ciena.com, pwe3 <pwe3@ietf.org>, " <lmartini"
> > > > > > >       <lmartini@cisco.com>
> > > > > > >
> > > > > > >Subject:    Re: [PWE3] LDP Signalling for PWs
> > > > > > >
> > > > > > >
> > > > > > >We are really trying to get the control draft to RFC, and
> > > > > > >therefore to restrict the changes, and that means
> > taking a hard
> > > > > > >line on anything except protocol design errors.
> > > > > > >
> > > > > > >This looks more like an applicability issue than a
> > correctness
> > > > > > >issue, and as perhaps we should put it in an applicability
> > > > > > >draft?
> > > > > > >
> > > > > > >- Stewart
> > > > > > >
> > > > > > >Diego Caviglia wrote:
> > > > > > >
> > > > > > >
> > > > > > >>Shah,
> > > > > > >>              thank for your replay, I agree with you.
> > > > > > >>
> > > > > > >>May be could be useful to state that in the LDP
> > > signalling draft.
> > > > > > >>
> > > > > > >>What is the feeling of the list on that matter?
> > > > > > >>
> > > > > > >>Diego
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>"Shah, Himanshu" <hshah@ciena.com> on 13/12/2004 23.41.52
> > > > > > >>
> > > > > > >>To:    "'Luca Martini'" <lmartini@cisco.com>, Diego Caviglia
> > > > > > >>       <Diego.Caviglia@marconi.com>
> > > > > > >>cc:    pwe3@ietf.org
> > > > > > >>
> > > > > > >>Subject:    RE: [PWE3] LDP Signalling for PWs
> > > > > > >>
> > > > > > >>
> > > > > > >>If you allow tunnel (lets say RSVP-TE based) to be
> > > > > > >>a logical IP i/f, one could conceivably send
> > > > > > >>regular LDP hello to discover the remote PE.
> > > > > > >>
> > > > > > >>This would be no different than if the target
> > > > > > >>LDP peer were to be on the direct link (adjacent).
> > > > > > >>
> > > > > > >>However, in order to differentiate topology based
> > > > > > >>LDP (link hello) from PWE3 signaling LDP (targetted),
> > > you have to
> > > > > > >>set the LDP Hello with t-bit set and send it
> > > > > > >>on unicast LDP Peer ID.
> > > > > > >>
> > > > > > >>Unless of course, you recognize the i/f as tunnel
> > > > > > >>and
> > > > > > >>1) use the tunnel end-point address as the unicast address
> > > > > > >>2) send targetted hello
> > > > > > >>
> > > > > > >>then you achieve what you intended.
> > > > > > >>
> > > > > > >>/himanshu
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>>-----Original Message-----
> > > > > > >>>From: Luca Martini [mailto:lmartini@cisco.com]
> > > > > > >>>Sent: Monday, December 13, 2004 5:08 PM
> > > > > > >>>To: Diego Caviglia
> > > > > > >>>Cc: pwe3@ietf.org
> > > > > > >>>Subject: Re: [PWE3] LDP Signalling for PWs
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>Diego,
> > > > > > >>>
> > > > > > >>>Extended discovery means that the UDP hello packets to
> > > > > > port 646 will
> > > > > > >>>have a destination IP address that is the remote
> > > PE's address.
> > > > > > >>>Basic discovery involves sending the UDP hello packets to
> > > > > > port 646 to
> > > > > > >>>destination address 224.0.0.2 ( the all routers multicast
> > > > > > address ).
> > > > > > >>>Packets to address 224.0.0.2 will not travel any
> > > further then the
> > > > > > >>>immediate neighbors.
> > > > > > >>>Normally there is not MPLS FEC for 224.0.0.2
> > > > > > >>>
> > > > > > >>>Luca
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>Diego Caviglia wrote:
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>Hi all,
> > > > > > >>>>            ID draft-ietf-pwe3-control-protocol-13 states
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>that ...The PEs
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>will establish an LDP session using the Extended Discovery
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>.." it is not
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>clear to me why I can't use basic discovery
> > mechansim given
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>that I have
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>e.g. an MPLS tunnel between the two PEs and thus a can
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>tunnel Hello packets
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>>between the LSP peers.
> > > > > > >>>>
> > > > > > >>>>What am I missing?
> > > > > > >>>>
> > > > > > >>>>Thanks.
> > > > > > >>>>
> > > > > > >>>>Regards
> > > > > > >>>>
> > > > > > >>>>Diego
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>_______________________________________________
> > > > > > >>>>pwe3 mailing list
> > > > > > >>>>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>>
> > > > > > >>>_______________________________________________
> > > > > > >>>pwe3 mailing list
> > > > > > >>>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>_______________________________________________
> > > > > > >>pwe3 mailing list
> > > > > > >>pwe3@ietf.org https://www1.ietf.org/mailman/listinfo/pwe3
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > pwe3 mailing list
> > > > pwe3@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pwe3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > pwe3 mailing list
> > > pwe3@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pwe3
> > >
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >
> >
>
>------------------------------------------------------------------------
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: benjamin.niven-jenkins@bt.com
Subject: Editorial review of
	draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Tue, 21 Dec 2004 15:08:20 -0000
Lines: 67
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Tue Dec 21 16:14:48 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: Editorial review of draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTnbrduC552AFNVEdm5TAAwBQ7M6w==
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 21 Dec 2004 15:08:20.0207 (UTC)
	FILETIME=[E83EDFF0:01C4E76E]
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Colleagues,

Below are some editorial nits/issues I found while reviewing =
draft-martini-pwe3-MH-PW-requirements-00.txt:

General (related to consistency throughout the document):
Throughout the documents sometimes terms like thousands/hundreds etc are =
used and sometimes 1000s/100s.  I think there should be some consistency =
and my vote would be to use the english word (i.e. thousands).

There is a mixture of US & British English - e.g. in some places =
'signaling' is used in others 'signalling' is used.

Is the expansion of PW 'pseudo-wire' or 'pseudowire'?  the document uses =
both.


Specific:
Page 7, paragrpah 1:
"Moreover, a SH-PW would require the existing of a PSN tunnel between =
the local U-PE and the remote U-PE." should probably read "Moreover, a =
SH-PW would require the existence of a PSN tunnel between the local U-PE =
and the remote U-PE."

Page 7, paragraph 4:
"at least N2" should read "at least N^2"

Page 8, paragraphs 3 & 4:
These are missing colons after the title - i.e.
"PSN Internetworking PWE3 signaling..." =3D> "PSN Internetworking: PWE3 =
signaling..." and
"Pseudo-Wires in Access and Metro networks Service providers..." =3D> =
"Pseudo-Wires in Access and Metro networks: Service providers..."

The sentence "The objective is to increase the gain OBfrom packet =
statistical multiplexing at an earlier point in the network" - I can see =
what is trying to be said but it isn't good english and doesn't read =
very well.=20

Page 8, paragraph 5:
Several spelling mistakes - i.e. 'beome' =3D> 'become', 'increaing' =3D> =
'increasing' and 'aggrvating' =3D> 'aggravating'.

Page 10, section 6.2, requirement -i:
"Ppon setting us a pseudowire, S-PEs" =3D> "Upon setting up a MH-PW, =
S-PEs".

Page 10, section 6.2, requirement -ii:
"When seitting up a MH-PW" =3D> "When setting up a MH-PW".

Page 12, paragraph 1 (section 6.4):
"MH-PWs MUST provide the following support national and international =
connections:" =3D> "MH-PWs MUST provide the following support {for,of} =
national and international connections:"


Ben

--=20
Ben Niven-Jenkins
Networking Specialist, BT Exact

e-mail: benjamin.niven-jenkins@bt.com
tel: +44(0) 1473 648225

pp34/161 B81 Callisto House, Adastral Park, Martlesham, Ipswich IP5 3RE, =
UK


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: benjamin.niven-jenkins@bt.com
Subject: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Tue, 21 Dec 2004 15:08:33 -0000
Lines: 136
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-bounces@ietf.org Tue Dec 21 16:16:53 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTnbr/PC552BFNVEdm5TAAwBQ7M6w==
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 21 Dec 2004 15:08:33.0464 (UTC)
	FILETIME=[F025BB80:01C4E76E]
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Colleagues,

I've just read draft-martini-pwe3-MH-PW-requirements-00.txt and have =
several technical questions/observations, so here goes...

1) Section 3.2 Figure 2:
The diagram shows 'Native Layer2 Service (AC)", ignoring the fact (IMO) =
that terms like Layer 2 aren't particularly meaningful, does this =
implicitly exclude non-layer 2 access circuits (e.g. TDM PWs, IP PWs =
etc.)

What does "Optional PW adaptation function" mean? [I know what an =
adaptation function is but I'm not sure what this adaptation function =
will be adapting if you see what I mean].


2) In Section 3.2:
It states "PE2 is therefore the PW switching point and will be referred =
to as the PW switching provider edge (S-PE)". Under Section 4 =
(Terminology) S-PE is defined as a PW Switching Point not a PW switching =
provider edge (incidentally PW switching provider edge is never used =
after Section 3.2).  I assume this is just a editorial mix up?

Also under the definition for PW Switching Point it states "A PW =
switching point is never the S-PE and the U-PE for a MH-PW"  I'm not =
saure what this means - is it trying to say that a PW switching point =
can never simultaneously be a S-PE and a U-PE for a single (same) PW.  =
If so I think it needs to be stated a bit more clearly.


3) Section 4:
The definition of PW access point address - I can see what this trying =
to be achieved with this definition but I don't think the wording is =
very clear and will lead to confusion, particularly what does it =
actually mean for a 'client layer service access the server layer at the =
access point address'?


4) Section 6.1:
Requirement -i starts "Client-server transparency MUST be maintained at =
each layer" - This implies that the current 'defaults' for some PWs may =
need changing in the MH-PW case - e.g. the current default for Eth PWs =
is to strip the FCS, so if I understand correctly for a MH-PW to achieve =
requirement -i then the default for Eth MH-PWs must be FCS retention?

Requirement -i seems to conflict with requirement -iv (MH-PWs MUST use =
the same encapsulation modes specified for SH-PWs) - what if the modes =
specified for SH-PWs do not allow transparent transfer of the client?  =
Is this just a matter of subtle interpretation? - i.e. the mode is the =
same for SH-PWs and MH-PWs but the 'options' chosen may be different.

Requirement -i suggests "S-PEs MAY only support PWs of the same type" =
and requirement -v "S-PEs MAY change the type or encapsulation mode of a =
PW." - IMO allowing S-PEs to stitch a PW of type A onto a PW of type B =
is likely to lead to a whole raft of potential interworking issues.

Requirement -ii, I'm not sure what this means - what's a SH-PW PSN?  Is =
it saying that you could use SH-PWs as a server layer for MH-PWs?


5) Section 6.3, 3rd paragrah:
"Ideally the PSN tunnel SHOULD have better QoS or same QoS =
characteristics as the carried PW.  However, in certain cases, an =
operator may need to bind a PW to a PSN tunnel with nominally lower QoS =
characteristics.

Is this saying that it is ok for a PW to expect a QoS of X (which a =
customer is presumably paying for) and for that PW to be transported =
over a PSN tunnel with QoS of Y (where Y<X) - doesn't seem right to me?


6) Section 6.3, 6th paragraph:
"If the PW signalling protocol signals PW traffic parameters in-band, it =
MUST enable separate traffic parameter values to be specified for the =
forward and reverse direction."

Why does this only apply to in-band signalling, should it also apply to =
out of band signalling (I think it should).  In fact IMO this is =
agnostic - i.e. separate traffic parameter values should be supported =
for the forward and reverse directions regardless of the method used to =
instantiate the MH-PW)?


7) Section 6.4, Requirement -iv
"MH-PWs SHOULD be routed across multiple S-PEs without the need to =
explicitly specify or configure the S-PEs that a PW uses."

This implies to me that a PW routing instance/database is required =
(analagous to the TE routing instance/link state database that can be =
used in GMPLS), which also implies that PW nodes must be capable of =
advertising their PW capabilities (which ACs, PWs, PSNs, OAM mechanisms, =
signalling mechanism etc. they support) and maintaining PW routing =
adjacencies with other PW nodes?.  Is this conclusion correct?


8) Section 6.5, requirement -ii
"MH-PWs MAY be set up dynamically end-to-end with a minimal number of =
OSS touches."

I assume this really means "MH-PWs MAY be set up dynamically and when =
they are set up dynamically they MUST be set up using a minimal number =
of OSS touches"?

I think it would be worthwhile defining what an OSS touch is in the =
terminology section - For example does a single OSS touch mean only one =
OSS is used, only one 'box' is touched, only one MIB is touched or what? =



9) Section 6.6., requirement -vii
"To avoid complex OAM interworking at the S-PE, the same PW OAM =
mechanisms MUST be used on both the ingress and egress sides of an S-PE"

I can see what this is trying to achieve and tend to agree (i.e. let's =
try and interwork as little as possible and just use best of breed =
functional components) but it somewhat contradicts section 5, use case =
-iii (PSN Internetworking - leaving aside that PSN interworking using =
MH-PWs is likely IMO to be a something of a nightmare) - i.e. it's OK to =
use MH-PWs to interwork between different PWE3 signalling protocols and =
PSN types but not different OAM types/mechanisms?  Is section 6.6., =
requirement -vii actually achieveable when PSN internetworking is being =
performed (e.g. is it possible to use the same OAM mechanism (VCCV?!?) =
over both LDP and L2TPv3 PWs)


Ben

--=20
Ben Niven-Jenkins
Networking Specialist, BT Exact

e-mail: benjamin.niven-jenkins@bt.com
tel: +44(0) 1473 648225

pp34/161 B81 Callisto House, Adastral Park, Martlesham, Ipswich IP5 3RE, =
UK


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Tue, 21 Dec 2004 18:16:33 +0200
Lines: 176
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Tue Dec 21 17:38:33 2004
Return-path: <pwe3-bounces@ietf.org>
To: "'benjamin.niven-jenkins@bt.com'" <benjamin.niven-jenkins@bt.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Ben and all,
Please see some comments inline.
I have snipped the parts that I do not comment upon.
Regards,
                                  Sasha Vainshtein
email:                         sasha@axerra.com <mailto:sasha@axerra.com> 
phone:                       +972-3-7569993 (office)
fax:                            +972-3-6487779
mobile:                      +972-52-8674833 


> -----Original Message-----
> From: benjamin.niven-jenkins@bt.com 
> [mailto:benjamin.niven-jenkins@bt.com]
> Sent: Tuesday, December 21, 2004 5:09 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Review of draft-martini-pwe3-MH-PW-requirements-00.txt
> 
> 
> Colleagues,
> 
> I've just read draft-martini-pwe3-MH-PW-requirements-00.txt 
> and have several technical questions/observations, so here goes...
> 
... snipped ...
> 
> What does "Optional PW adaptation function" mean? [I know 
> what an adaptation function is but I'm not sure what this 
> adaptation function will be adapting if you see what I mean].
> 
[Sasha] I'd say that the draft requires some clean-up regarding the style
and usage of terms:
- IMO, consistent usage of one set of terms and notions is preferable to
mixing existing PWE3
  terms with ITU-T G.805/G.809 ones. If necessary (and I agree that it would
be beneficial),
  a "translation" could be provided, but it should be localized (e.g., in an
Annex).
  (And, yest,I fully understand that this would be at quite a cost to the
Editors. But
  the current mix comes at a price for the readers:-)
- terms that are used must be defined, preferably once and all in one place
- terms that are NOT USED should be removed from the "Terminology" section
- Different things should be called by different names. E.g., either an
SH-PW and 
  a PW segment are different, or there is no such term as a PW segment (I
assume
  that SH-PWs exist, since that is what this WG has been dealing with for
the last
  3+ years, right?:-)
> 
> 2) In Section 3.2:
> It states "PE2 is therefore the PW switching point and will 
> be referred to as the PW switching provider edge (S-PE)". 
> Under Section 4 (Terminology) S-PE is defined as a PW 
> Switching Point not a PW switching provider edge 
> (incidentally PW switching provider edge is never used after 
> Section 3.2).  I assume this is just a editorial mix up?
>
[Sasha] While the terms U-PE and S-PE are very convenient, they
carry a certain connotation that requires, IMO, clarification. Namely,
is an S-PE really a "provider edge" device? Because, IMO, "provider edge"
is something well understood and does not depend upon existence or
non-existence of MH-PWs... In other words: can any router on the path
between a pair of U-PEs become an S-PE, or is this functionality limited to
routers that belong to some well-defined borders?  
>
... snipped ...
> 
> 3) Section 4:
> The definition of PW access point address - I can see what 
> this trying to be achieved with this definition but I don't 
> think the wording is very clear and will lead to confusion, 
> particularly what does it actually mean for a 'client layer 
> service access the server layer at the access point address'?
> 
[Sasha] This is a good example of a term defined but never used.
(So I am not sure it is worth clarifying what the Editors try to achieve
with this definition:-)
> 
> 4) Section 6.1:
> Requirement -i starts "Client-server transparency MUST be 
> maintained at each layer" - This implies that the current 
> 'defaults' for some PWs may need changing in the MH-PW case - 
> e.g. the current default for Eth PWs is to strip the FCS, so 
> if I understand correctly for a MH-PW to achieve requirement 
> -i then the default for Eth MH-PWs must be FCS retention?
> 
> Requirement -i seems to conflict with requirement -iv (MH-PWs 
> MUST use the same encapsulation modes specified for SH-PWs) - 
> what if the modes specified for SH-PWs do not allow 
> transparent transfer of the client?  Is this just a matter of 
> subtle interpretation? - i.e. the mode is the same for SH-PWs 
> and MH-PWs but the 'options' chosen may be different.
>
[Sasha] This is a good example of the style mixture.
The current (SH) PWE3 Architecture has its "Principle of Minimum
Intervention"
which presumably is equivalent to the client/server transparency. 
>
> Requirement -i suggests "S-PEs MAY only support PWs of the 
> same type" and requirement -v "S-PEs MAY change the type or 
> encapsulation mode of a PW." - IMO allowing S-PEs to stitch a 
> PW of type A onto a PW of type B is likely to lead to a whole 
> raft of potential interworking issues.
>
[Sasha] I agree that this can become a nightmare both for the operators
and for the vendors. On the other hand, can we really prohibit any
kind of interworking at S-PEs without serios impact on the desired
functionality? Or should we restrict interworking to a few
well-understood use cases? 
>
> Requirement -ii, I'm not sure what this means - what's a 
> SH-PW PSN?  Is it saying that you could use SH-PWs as a 
> server layer for MH-PWs?
> 
[Sasha] I could not say it better!
> 
... snipped ...
> 
> 6) Section 6.3, 6th paragraph:
> "If the PW signalling protocol signals PW traffic parameters 
> in-band, it MUST enable separate traffic parameter values to 
> be specified for the forward and reverse direction."
> 
> Why does this only apply to in-band signalling, should it 
> also apply to out of band signalling (I think it should).  In 
> fact IMO this is agnostic - i.e. separate traffic parameter 
> values should be supported for the forward and reverse 
> directions regardless of the method used to instantiate the MH-PW)?
> 
[Sasha] I agree. 
> 
> 7) Section 6.4, Requirement -iv
> "MH-PWs SHOULD be routed across multiple S-PEs without the 
> need to explicitly specify or configure the S-PEs that a PW uses."
> 
> This implies to me that a PW routing instance/database is 
> required (analagous to the TE routing instance/link state 
> database that can be used in GMPLS), which also implies that 
> PW nodes must be capable of advertising their PW capabilities 
> (which ACs, PWs, PSNs, OAM mechanisms, signalling mechanism 
> etc. they support) and maintaining PW routing adjacencies 
> with other PW nodes?.  Is this conclusion correct?
> 
[Sasha] It looks correct to me, and leads me to a conclusion that
this requirement cannot be realistically met.
> 
> 8) Section 6.5, requirement -ii
> "MH-PWs MAY be set up dynamically end-to-end with a minimal 
> number of OSS touches."
> 
> I assume this really means "MH-PWs MAY be set up dynamically 
> and when they are set up dynamically they MUST be set up 
> using a minimal number of OSS touches"?
> 
> I think it would be worthwhile defining what an OSS touch is 
> in the terminology section - For example does a single OSS 
> touch mean only one OSS is used, only one 'box' is touched, 
> only one MIB is touched or what? 
> 
[Sasha] Assuming that zero OSS touches (whatever an OSS touch means)
presumably cannot result in setup of an MH-PW, 1 (one) seems like
the lower limit for this number. And, as mentioned already on this
list, it is important to understand whether the requirement for minimal
number of OSS touches means "a single OSS touch" (in which case it
can be easily verified), or someting else -in which case it is not clear
to me that it can be verified: how do you prove that a specific MH-PW
set up with N>1 OSS touches cannot be set up with (N-1) touches?
> 
> 9) Section 6.6., requirement -vii
> "To avoid complex OAM interworking at the S-PE, the same PW 
> OAM mechanisms MUST be used on both the ingress and egress 
> sides of an S-PE"
> 
... snipped to the end ...


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Peter Willis <pjw@ip-engineering.bt.com>
Subject: Re: Re: I-D ACTION:draft-martini-pwe3-MH-PW-requirements-0
	0.txt
Date: Tue, 21 Dec 2004 16:43:57 +0000
Lines: 29
References: <AF5018AC03D1D411ABB70002A5091326015E1991@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-From: pwe3-bounces@ietf.org Tue Dec 21 17:51:46 2004
Return-path: <pwe3-bounces@ietf.org>
X-Mailer: exmh version 2.5 07/13/2001 with version: MH 6.8.3 #11[UCI]
To: Sasha Vainshtein <Sasha@AXERRA.com>, pwe3@ietf.org
In-reply-to: Your message of "Fri, 17 Dec 2004 15:39:31 +0200."
	<AF5018AC03D1D411ABB70002A5091326015E1991@TLV1> 
X-OriginalArrivalTime: 21 Dec 2004 16:45:24.0078 (UTC)
	FILETIME=[778B10E0:01C4E77C]
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

The other advantage of AAAing each MH-PW and reusing existing RADIUS 
infrastructure is that the FQDN could be used to identify the U-PE attchement 
circuit. We can hide the IP addresses of the operators' infrastructure from each other and use FQDN
 without resorting to using "phone numbers".

Did someone did say we should look at lessons learnt from L2TP for MH-PW?

AAAing each PW also solves my business processes of how I'm going to trust 
the other operator to authenticate their attached customers and it could 
solve the problem of ensuring that PW provisioning does not get PWs 
crossed over.

So dynamically signalling inter-operator PWs might not be that difficult if 
we're willing to think "outside the box".

> I'm not sure whether 
> authentication of the signalling entities between operators is sufficient
> or whether each MH-PW needs its own AAA. I suspect the latter makes reusing
> PPP/radius like mechanisms easier?
> 
> [Sasha] A nice touch - on at least two counts:
> - seems like we need an AAA section in the requirements document, and
>   this was not touched so far
> - I would expect the SPs to push strongly for reuse of the existing
>   AAA architecture and methods; but then I do not work for an SP.

Regards,

Peter.


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Wed, 22 Dec 2004 06:16:58 -0000
Lines: 212
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Wed Dec 22 07:25:27 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTne9owIr23HwAuTUWeaKsmBVIxmgAaF5VA
To: <Sasha@AXERRA.com>, <benjamin.niven-jenkins@bt.com>
X-OriginalArrivalTime: 22 Dec 2004 06:16:59.0442 (UTC)
	FILETIME=[D83DF120:01C4E7ED]
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Sasha,  Largely agree with all your points...a few observations
below.
> Ben and all,
> Please see some comments inline.

> I have snipped the parts that I do not comment upon.

> ... snipped ...
> >=20
> > What does "Optional PW adaptation function" mean? [I know
> > what an adaptation function is but I'm not sure what this=20
> > adaptation function will be adapting if you see what I mean].
> >=20
> [Sasha] I'd say that the draft requires some clean-up=20
> regarding the style and usage of terms:
> - IMO, consistent usage of one set of terms and notions is=20
> preferable to mixing existing PWE3
>   terms with ITU-T G.805/G.809 ones. If necessary (and I=20
> agree that it would be beneficial),
NH=3D> I know the guys who started the G.805 func arch stuff and I also
know why they did it, ie to create a consistent language to describe
networks, esp for the folks who then need to create equipement
specifications and management information models.  The key point about
this stuff is that it captures 'discovered truths' about
networking.....so, irrespective of whether one likes or dislikes the
actual vocabulary used, the underlying concepts are invariant of this.
Its a pity more folks are not familar with these concepts as I think
they help provide insight and clarity.
=20
>   a "translation" could be provided, but it should be=20
> localized (e.g., in an Annex).
>   (And, yest,I fully understand that this would be at quite a=20
> cost to the Editors. But
>   the current mix comes at a price for the readers:-)
> - terms that are used must be defined, preferably once and=20
> all in one place
> - terms that are NOT USED should be removed from the=20
> "Terminology" section
> - Different things should be called by different names. E.g.,=20
> either an SH-PW and=20
>   a PW segment are different, or there is no such term as a=20
> PW segment (I assume
>   that SH-PWs exist, since that is what this WG has been=20
> dealing with for the last
>   3+ years, right?:-)
> >=20
> > 2) In Section 3.2:
> > It states "PE2 is therefore the PW switching point and will
> > be referred to as the PW switching provider edge (S-PE)".=20
> > Under Section 4 (Terminology) S-PE is defined as a PW=20
> > Switching Point not a PW switching provider edge=20
> > (incidentally PW switching provider edge is never used after=20
> > Section 3.2).  I assume this is just a editorial mix up?
> >
> [Sasha] While the terms U-PE and S-PE are very convenient,=20
> they carry a certain connotation that requires, IMO,=20
> clarification. Namely, is an S-PE really a "provider edge"=20
> device? Because, IMO, "provider edge" is something well=20
> understood and does not depend upon existence or=20
> non-existence of MH-PWs... In other words: can any router on=20
> the path between a pair of U-PEs become an S-PE, or is this=20
> functionality limited to routers that belong to some=20
> well-defined borders? =20
NH=3D> This is an excellent example of why using func arch helps one
see/describe things in a consistent way, ie irrespective of the 'names'
one gives to devices it is only the functions they contain that are of
any real importance.
> >
> ... snipped ...
> >=20
> > 3) Section 4:
> > The definition of PW access point address - I can see what
> > this trying to be achieved with this definition but I don't=20
> > think the wording is very clear and will lead to confusion,=20
> > particularly what does it actually mean for a 'client layer=20
> > service access the server layer at the access point address'?
> >=20
> [Sasha] This is a good example of a term defined but never=20
> used. (So I am not sure it is worth clarifying what the=20
> Editors try to achieve with this definition:-)
NH=3D> I think the whole area of addressing is a bit of mess.  And one
reason for this IMO is that we have not used a func arch approach to
describing the networks we are dealing with.....this does not only apply
to MPLS but also GMPLS (ie the co-cs mode networks).  If one makes a
mistake with layer network addressing at t=3D0 it is very hard to go =
back
and sort it out later. =20

One thing that has bothered me for a long time in MPLS is that the
trails (ie LSPs) do not have a consistent method of access point
addressing.  The traffic data-plane addresses should be independent of
the control-plane, ie whether a trail is created by signalling protocol
X, Y or Z or by network management provisioning the access point
addresses should be the same.  However, in MPLS these addresses take
their format from the signalling protocol used.  This is wrong.  When
one considers OAM requirements (and downstream NMS/OSS impact) this
issue comes into focus.  That is, a CV function is a common OAM theme
across all 3 network modes.....in the cl-ps mode this 'comes for free'
as each pkt contains a SA, but in the co modes we have to consciously
add this function.  So if we want a simple, consistent and unambiguous
method of defect detection/handling across the whole population of
trails we need a consistent method of inserting the trail's SA in the CV
function.  Further, this has to be unidirectional with processing at the
trail sink....else things will not work well/simply, and we can't have a
common approach across p2p and p2mp constructions.  For those reading
the MPLS WG list, you will also note I am also trying to get this point
across here because folks are currently discussing p2mp OAM
requirements.
> >=20
> > 4) Section 6.1:
> > Requirement -i starts "Client-server transparency MUST be
> > maintained at each layer" - This implies that the current=20
> > 'defaults' for some PWs may need changing in the MH-PW case -=20
> > e.g. the current default for Eth PWs is to strip the FCS, so=20
> > if I understand correctly for a MH-PW to achieve requirement=20
> > -i then the default for Eth MH-PWs must be FCS retention?
> >=20
> > Requirement -i seems to conflict with requirement -iv (MH-PWs
> > MUST use the same encapsulation modes specified for SH-PWs) -=20
> > what if the modes specified for SH-PWs do not allow=20
> > transparent transfer of the client?  Is this just a matter of=20
> > subtle interpretation? - i.e. the mode is the same for SH-PWs=20
> > and MH-PWs but the 'options' chosen may be different.
> >
> [Sasha] This is a good example of the style mixture.
> The current (SH) PWE3 Architecture has its "Principle of=20
> Minimum Intervention" which presumably is equivalent to the=20
> client/server transparency.
NH=3D> Yes it is Sasha.  I think it was a really big mistake to start =
this
client layer compression stuff as its creates (per case) functional
dependancies between the client and the server. =20
> >
> > Requirement -i suggests "S-PEs MAY only support PWs of the
> > same type" and requirement -v "S-PEs MAY change the type or=20
> > encapsulation mode of a PW." - IMO allowing S-PEs to stitch a=20
> > PW of type A onto a PW of type B is likely to lead to a whole=20
> > raft of potential interworking issues.
> >
> [Sasha] I agree that this can become a nightmare both for the=20
> operators and for the vendors. On the other hand, can we=20
> really prohibit any kind of interworking at S-PEs without=20
> serios impact on the desired functionality? Or should we=20
> restrict interworking to a few well-understood use cases?
NH=3D> This is an example of what happens downstream if if you don't =
keep
the client/server case functionally decoupled.  Of course one can't stop
folks doing crazy things (like client compression between layer
networks) but the default behaviour should be to sound arch principles.
> >
> > Requirement -ii, I'm not sure what this means - what's a
> > SH-PW PSN?  Is it saying that you could use SH-PWs as a=20
> > server layer for MH-PWs?
> >=20
> [Sasha] I could not say it better!
NH=3D> I agree with both of you.....but if you think about it then why
not?  I mean, if folks think things like client compression and
SDHoverIP are 'good ideas' then one can have any XoverY and recurse this
as many times as one likes....whether the resultant HRX (Hypothetical
Reference Connection) constructions will 'work' for some end-system
application and/or can be meaningfully apportioned (wrt impairment
objectives) across a set of tamdemed operator domains is yet another
complex problem that has been created and is waiting in the wings for
future discovery.
> >=20
> ... snipped ...
> >=20
> > 6) Section 6.3, 6th paragraph:
> > "If the PW signalling protocol signals PW traffic parameters
> > in-band, it MUST enable separate traffic parameter values to=20
> > be specified for the forward and reverse direction."
> >=20
> > Why does this only apply to in-band signalling, should it
> > also apply to out of band signalling (I think it should).  In=20
> > fact IMO this is agnostic - i.e. separate traffic parameter=20
> > values should be supported for the forward and reverse=20
> > directions regardless of the method used to instantiate the MH-PW)?
> >=20
> [Sasha] I agree.=20
NH=3D> I agree too.  The requirement for OOB control/management is an
issue that should be adressed in its own right.
> >=20
> > 7) Section 6.4, Requirement -iv
> > "MH-PWs SHOULD be routed across multiple S-PEs without the
> > need to explicitly specify or configure the S-PEs that a PW uses."
> >=20
> > This implies to me that a PW routing instance/database is
> > required (analagous to the TE routing instance/link state=20
> > database that can be used in GMPLS), which also implies that=20
> > PW nodes must be capable of advertising their PW capabilities=20
> > (which ACs, PWs, PSNs, OAM mechanisms, signalling mechanism=20
> > etc. they support) and maintaining PW routing adjacencies=20
> > with other PW nodes?.  Is this conclusion correct?
> >=20
> [Sasha] It looks correct to me, and leads me to a conclusion=20
> that this requirement cannot be realistically met.
NH=3D> This is where I came in on the topic when I observed right at the
outset that moving from SH to MH LSPs is starting to look like creating
a new layer network to me (and all this implies as Ben noted above).
MPLS is a digital wrapper and this has a 'topology of the fly' issue
(see my response to Chris Metz of recent).  MPLS degenerates to a proper
layer network iff the top level LSPs are span-congruent with their
server (true networked) LSPs, ie the 1-hop top level LSPs are acting as
some form of 'session' IDs for the client payload....which is the case
with SH PWs and rfc2547 (the latter resolves to (at least) a VPN/VRF in
a PE).

I'm not sure how this issue is going to get resolved (or if it can get
resolved). =20

regards, Neil
<snipped to end>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: benjamin.niven-jenkins@bt.com
Subject: RE: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Wed, 22 Dec 2004 17:08:12 -0000
Lines: 49
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org
X-From: pwe3-bounces@ietf.org Wed Dec 22 18:26:57 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTneW3Kf31NJkcvT/SO9/qJqHmr1gAw/J9w
To: <Sasha@AXERRA.com>
X-OriginalArrivalTime: 22 Dec 2004 17:08:12.0818 (UTC)
	FILETIME=[D1C9F720:01C4E848]
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Sasha, Colleagues,

See in-line.  I have snipped where appropriate

Ben

> -----Original Message-----
> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]
> Sent: 21 December 2004 16:17
> To: Niven-jenkins,B,Ben,XGH5 R
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Review of
> draft-martini-pwe3-MH-PW-requirements-00.txt
>=20
> Ben and all,
> Please see some comments inline.
> I have snipped the parts that I do not comment upon.
> Regards,
>
> > 4) Section 6.1:
> > Requirement -i starts "Client-server transparency MUST be=20
> > maintained at each layer" - This implies that the current=20
> > 'defaults' for some PWs may need changing in the MH-PW case -=20
> > e.g. the current default for Eth PWs is to strip the FCS, so=20
> > if I understand correctly for a MH-PW to achieve requirement=20
> > -i then the default for Eth MH-PWs must be FCS retention?
> >=20
> > Requirement -i seems to conflict with requirement -iv (MH-PWs=20
> > MUST use the same encapsulation modes specified for SH-PWs) -=20
> > what if the modes specified for SH-PWs do not allow=20
> > transparent transfer of the client?  Is this just a matter of=20
> > subtle interpretation? - i.e. the mode is the same for SH-PWs=20
> > and MH-PWs but the 'options' chosen may be different.
> >
> [Sasha] This is a good example of the style mixture.
> The current (SH) PWE3 Architecture has its "Principle of Minimum
> Intervention"
> which presumably is equivalent to the client/server transparency.=20

I do not believe that the PWE3 'Principle of Minimum intervention' is =
exactly equivalent to client/server transparency which is what prompted =
the observation/query above.

My understanding is that the 'Principle of Minimum intervention' means =
that 'the payload should be transported as received with as few =
modifications as possible' whereas transparent transfer of a client =
means that 'the client must be transported as received with no =
modifications'.  So in my understanding client/server transparency is =
equivalent to a 'principle of no intervention'.


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: IANA document allocation
Date: Wed, 22 Dec 2004 10:36:32 -0700
Organization: Cisco Systems
Lines: 87
References: <200412201553.iBKFrNew016250@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'W. Mark Townsley'" <townsley@cisco.com>, erosen@cisco.com,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-bounces@ietf.org Wed Dec 22 18:47:35 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20040620
X-Accept-Language: en-us, en, fr, it
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200412201553.iBKFrNew016250@rotala.raleigh.ibm.com>
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.241.115]
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Thomas,

I think that the private use terminology is better , and I will change 
the "vendor specific" range to "private use".
I do like the expert allocation method, but to support some of the 
objections made here, I think it should be a "light" expert review.
I would put forward that the expert should be required to present strong 
proof why a particular value should not be allocated.
For values allocated in the data plane ( like for the CW ) I think we 
should probably only have a "IETF consensus" section. The potential for 
abuse in this area is significant.
However, things like error status codes are probably ok with a FCFS 
section. The PW type should probably be expert review, and private use. 
PW type may be  easily converted from one to another, so even if 
something starts out into private use, and equivalent code point can be 
allocated by expert review,

Luca


Thomas Narten wrote:

>>I think  most documents refer to  this as "private use",  i.e., it basically
>>means "not  to be  assigned by IANA".
>>    
>>
>
>"Private use" is a defined term in 2434. If that is what is meant, it
>is better to use standard terminology.
>
>  
>
>>In general, this only gets used if there is no FCFS space.  However,
>>values in this space may also end up becoming de facto standards.
>>Private use values could also be used if someone wanted to deploy a
>>proprietary and non-interoperable extension, though I'm sure that no
>>one would ever want to do that.
>>    
>>
>
>"private use" is also not really for deploying proprietary stuff, at
>least not for a _vendor_ to do so. It is intended that an end-user can
>do this (within an environment they do control, so they can assure
>that numbers won't conflict). (If a vendor needs to deploy something,
>we need to make sure that they use unique numbers so that the numbers
>don't conflict with those used by some other vendor/purpose.)
>
>  
>
>>One thing that might be rational would be to make the FCFS space
>>bigger, but to also leave a reserved space.  If at some point we
>>actually look to be in danger of running out of FCFS space, we can
>>then decide whether to extend the FCFS space.
>>    
>>
>
>I think one really needs to look at each name space individually and
>consider such things as:
>
> - is the space large enough to accomodate likely usage?
>
>Separately, one needs to consider how much review is necessary. For
>some name spaces, I agree that little or no review is needed. But for
>others, it is. Again, please have a look at
>draft-iesg-vendor-extensions-02.txt, as there is much experience with
>problems caused by unreviewed extensions.
>
>  
>
>>I do not at all like the idea of "expert review", as it creates a
>>process which is all too easily subverted by cronyism and political
>>agendas, or which might just fail to deliver results.
>>    
>>
>
>Well, if you are not willing to have _any_ review, there is a risk
>that bogus extensions will get defined and deployed that negatively
>impact other deployments, the overall pwe3 architecture, etc. IMO,
>expert review provides the reasonable balance between no review (which
>has caused significant problems with some protocols) vs. an even
>higher bar, such as requiring an RFC publication, (or even higher,
>requiring a standards track document).
>
>Thomas
>
>  
>


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Eric Rosen <erosen@cisco.com>
Subject: Re: IANA document allocation
Date: Wed, 22 Dec 2004 15:30:49 -0500
Lines: 53
References: <200412201553.iBKFrNew016250@rotala.raleigh.ibm.com>
Reply-To: erosen@cisco.com
Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
	"PWE3 WG \(E-mail\)" <pwe3@ietf.org>, Luca Martini <lmartini@cisco.com>
X-From: pwe3-bounces@ietf.org Wed Dec 22 21:44:25 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
To: Thomas Narten <narten@us.ibm.com>
In-reply-to: Your message of Mon, 20 Dec 2004 10:53:23 -0500.
	<200412201553.iBKFrNew016250@rotala.raleigh.ibm.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
	(=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3
	(sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


Thomas> "private use" is also not really for deploying proprietary stuff, at
Thomas> least not for  a _vendor_ to do so. It is  intended that an end-user
Thomas> can  do this (within  an environment  they do  control, so  they can
Thomas> assure that numbers won't conflict).

This is not very realistic. 

Thomas> If a  vendor needs to  deploy something, we  need to make  sure that
Thomas> they  use unique  numbers so  that the  numbers don't  conflict with
Thomas> those used by some other vendor/purpose.

That's why FCFS  is really better; otherwise "private  use" becomes "defacto
FCFS by the largest vendors". 

Thomas> please have a  look at draft-iesg-vendor-extensions-02.txt, as there
Thomas> is much experience with problems caused by unreviewed extensions

That  document  is  woefully  incomplete,  as it  neglects  to  catalog  the
following situations:

- problems caused by reviewed extensions
- unreviewed extensions that don't cause problems
- problems caused by the inability to get an allocation in a timely manner
-  problems caused  because the  "expert review"  was  insufficiently expert
  (perhaps it  was political  rather than technical,  or perhaps  the expert
  simply did not appreciate the valid need for the extension). 

and my favorite: 

- problems  caused  when  unreviewed  extensions are  made  by  overloading
  existing codepoints. 

I can  think of a  couple of cases  of the latter where  existing codepoints
were simply reinterpreted  to have a different meaning  in certain contexts.
(For instance,  a 32-bit  field may be  reinterpreted as two  16-bit fields,
even if everyone really knows that at  least one of the 16-bit fields is too
short. "We can't make it any larger, that would require a new code point".)
This enables  the protocol to be  extended without need of  a new codepoint,
but it usually causes a number of undesirable side-effects. 

IMHO, draft-iesg-vendor-extensions-02.txt  does not present  a very balanced
analysis. 

Luca> I do  like the expert  allocation method, but  to support some  of the
Luca> objections made here, I think it should be a "light" expert review.  I
Luca> would put forward that the expert should be required to present strong
Luca> proof why a particular value should not be allocated. 

The fact  of the matter  is that there  is no process  in the IETF  which is
known  to  provide  timely   and  objective  results  here.   Modifying  our
description of the  non-existent process to make it  sound better doesn't do
anything but make it sound better. 


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Fri, 24 Dec 2004 11:01:25 +0000
Lines: 60
References: <B1F38D7B53615140BCEA6677DF9F2F8C0643538D@i2km11-ukbr.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, Sasha@AXERRA.com
X-From: pwe3-bounces@ietf.org Fri Dec 24 12:08:31 2004
Return-path: <pwe3-bounces@ietf.org>
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
To: benjamin.niven-jenkins@bt.com
In-Reply-To: <B1F38D7B53615140BCEA6677DF9F2F8C0643538D@i2km11-ukbr.domain1.systemhost.net>
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org


>>>4) Section 6.1:
>>>Requirement -i starts "Client-server transparency MUST be 
>>>maintained at each layer" - This implies that the current 
>>>'defaults' for some PWs may need changing in the MH-PW case - 
>>>e.g. the current default for Eth PWs is to strip the FCS, so 
>>>if I understand correctly for a MH-PW to achieve requirement 
>>>-i then the default for Eth MH-PWs must be FCS retention?

I don't think that changing the PWE3 defaults is viable, because
the IETF tries very hard to maintain backwards compatibility.
Ideally the two outer ends of a MH-PW don't (or shouldn't) know
that they are part of a MH-PW.

However the above does not stop some "enhanced" mode such as FCS
retention becoming the industry norm.

>>>
>>>Requirement -i seems to conflict with requirement -iv (MH-PWs 
>>>MUST use the same encapsulation modes specified for SH-PWs) - 
>>>what if the modes specified for SH-PWs do not allow 
>>>transparent transfer of the client?  Is this just a matter of 
>>>subtle interpretation? - i.e. the mode is the same for SH-PWs 
>>>and MH-PWs but the 'options' chosen may be different.
>>>
>>
>>[Sasha] This is a good example of the style mixture.
>>The current (SH) PWE3 Architecture has its "Principle of Minimum
>>Intervention"
>>which presumably is equivalent to the client/server transparency. 
> 
> 
> I do not believe that the PWE3 'Principle of Minimum intervention' 
is exactly equivalent to client/server transparency which is what
prompted the observation/query above.
> 
> My understanding is that the 'Principle of Minimum intervention' 
means that 'the payload should be transported as received with as
few modifications as possible' whereas transparent transfer of a
client means that 'the client must be transported as received
with no modifications'.  So in my understanding client/server
transparency is equivalent to a 'principle of no intervention'.
> 

Unless you have a real piece of wire, then you always have
some changes - and even then there it depends on the wire.

There has been a consistent focus on Ethernet FCS (and we have
a draft to allow an FCS retention mode). FCS retention is a
relatively simple operation. However that is only part of the
story. For full transparency you also need to carry the
preamble bits, and maybe you need to propagate some timing
info as well.

So do we really want a complete absence of intervention - with
all the assocated hardware, bandwidth and deployment delay costs,
or is it that we need minimum intervention and are really just
discussing the extent of the emulation?

- Stewart


From pwe3-bounces@ietf.org  Wed Dec 27 15:58:27 2006
From: neil.2.harrison@bt.com
Subject: RE: Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Date: Fri, 24 Dec 2004 15:48:32 -0000
Lines: 129
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: pwe3@ietf.org, Sasha@AXERRA.com
X-From: pwe3-bounces@ietf.org Fri Dec 24 16:52:26 2004
Return-path: <pwe3-bounces@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Review of draft-martini-pwe3-MH-PW-requirements-00.txt
Thread-Index: AcTpqUHBQtJ5v/JzQKG8JjtOF5MahgAHizhQ
To: <stbryant@cisco.com>, <benjamin.niven-jenkins@bt.com>
X-OriginalArrivalTime: 24 Dec 2004 15:48:32.0985 (UTC)
	FILETIME=[059CD490:01C4E9D0]
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org

Hi Stewart,

> >>>4) Section 6.1:
> >>>Requirement -i starts "Client-server transparency MUST be
> >>>maintained at each layer" - This implies that the current=20
> >>>'defaults' for some PWs may need changing in the MH-PW case -=20
> >>>e.g. the current default for Eth PWs is to strip the FCS, so=20
> >>>if I understand correctly for a MH-PW to achieve requirement=20
> >>>-i then the default for Eth MH-PWs must be FCS retention?
>=20
> I don't think that changing the PWE3 defaults is viable,=20
> because the IETF tries very hard to maintain backwards=20
> compatibility.
NH=3D> I think we must always strive for adherence to correct
architectural practice....and in a client/server case (which is what PWs
are) the most fundamantal architectural requirement is functional
decoupling between the client and the server.  But when that is violated
(eg client compression) saying we should maintain backwards
compatibility with that is hardly good practice IMO.

> Ideally the two outer ends of a MH-PW don't=20
> (or shouldn't) know that they are part of a MH-PW.
NH=3D> I fully agree.  And that is precisely what we would have now if:
-	we had adhered to the arch principle noted above of client and
server layer decoupling;
-	we had not forced an artifical requirement that XoverMPLS be
treated the same as XoverIP.....indeed, its already clear this is
untenable anyway.  The differences get even more obvious when one
considers the co-cs mode as in GMPLS, eg here control/management must be
OOB, but that is not the only difference.

I won't bore folks with a long explanation of why the 3 modes are
different and all that entails, but its this sort of stuff that has lead
to the current situation....which is a pity IMO as I think we could have
avoided many of the complexities/problems we now are encountering had we
used the correct arch principles from the outset.
=20
> However the above does not stop some "enhanced" mode such as=20
> FCS retention becoming the industry norm.
NH=3D> This spin on client compression is almost unforgiveable IMO.  If =
we
apply func arch principles to the IEEE specification of ethernet the FCS
is part of the link-connection adaptation and should be checked on each
link connection.  It is not part of the CI (characteristic information)
however (like the SA/DA is for example).  However, it should never be
removed if the traffic units then get switched across a series of
nodes/links and then re-inserted at some downstream point.....that is
clearly wrong.
>=20
> >>>
> >>>Requirement -i seems to conflict with requirement -iv (MH-PWs
> >>>MUST use the same encapsulation modes specified for SH-PWs) -=20
> >>>what if the modes specified for SH-PWs do not allow=20
> >>>transparent transfer of the client?  Is this just a matter of=20
> >>>subtle interpretation? - i.e. the mode is the same for SH-PWs=20
> >>>and MH-PWs but the 'options' chosen may be different.
> >>>
> >>
> >>[Sasha] This is a good example of the style mixture.
> >>The current (SH) PWE3 Architecture has its "Principle of Minimum=20
> >>Intervention" which presumably is equivalent to the client/server=20
> >>transparency.
> >=20
> >=20
> > I do not believe that the PWE3 'Principle of Minimum intervention'
> is exactly equivalent to client/server transparency which is=20
> what prompted the observation/query above.
> >=20
> > My understanding is that the 'Principle of Minimum intervention'
> means that 'the payload should be transported as received=20
> with as few modifications as possible' whereas transparent=20
> transfer of a client means that 'the client must be=20
> transported as received with no modifications'.  So in my=20
> understanding client/server transparency is equivalent to a=20
> 'principle of no intervention'.
> >=20
>=20
> Unless you have a real piece of wire, then you always have
> some changes - and even then there it depends on the wire.
NH=3D> True....and this is why it is important to be very clear on the
difference between section layer protocols that do not get
networked/switched (ie those that are media specific on links, like
optical line codes or indeed ethernet's preamble) and the CI of layer
network protocols (ie the traffic units that are switched/networked and
that remain constant over various electrical/optical/radio section layer
types).  This is a key purpose of defining layer networks according to
the functional arch principles of G.805 and G.809, ie to avoid any
ambiguity.
>=20
> There has been a consistent focus on Ethernet FCS (and we=20
> have a draft to allow an FCS retention mode). FCS retention=20
> is a relatively simple operation. However that is only part=20
> of the story. For full transparency you also need to carry=20
> the preamble bits, and maybe you need to propagate some=20
> timing info as well.
NH=3D> If one was truly emulating the section layer behaviour I'd
agree.....but this makes very little sense.  A section layer protocol,
almost by definition, lies at the bottom of the networked stack, ie
there is nothing below it.  The thing we must convey transparently
however is the CI.  Indeed, the name 'PW' can be seen as a pretty poor
choice because this is NOT what we are doing or what is required.
>=20
> So do we really want a complete absence of intervention -=20
> with all the assocated hardware, bandwidth and deployment=20
> delay costs, or is it that we need minimum intervention and=20
> are really just discussing the extent of the emulation?
NH=3D> What we really want is actually very simple....and if we do this
things are going to work as best they can (the limit here is how well
each technology has been functionally specified in the first place):
-	client/server decoupling (all planes)
-	correct mapping of defects detected at the server layer to the
client layer FDI (if the client belongs to the co mode).....the nature
of defect detection/handling in the server is dependent on the mode of
the server, its different in all 3 cases.
-	the adaptation between the client and server layers is a
function of the mode of both the client and the server...1 size does not
fit all here.

regards, Neil
>=20
> - Stewart
>=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


