From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architectu
	re]
Date: Tue, 23 Mar 2004 18:37:09 +0200
Lines: 152
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, Ron Cohen <ronc@lyciumnetworks.com>,
        Yaakov Stein
	 <yaakov_s@rad.com>
X-From: pwe3-admin@ietf.org Tue Mar 23 17:43:13 2004
Return-path: <pwe3-admin@ietf.org>
To: "'stbryant@cisco.com'" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart and all,
I think that once references to the appropriate protocol specs
to go with each explicitly mentioned type of PW demultiplexing 
are added, the text is OK.

Sorry for complicating things, but how, hopefully, my position
is clear.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Tuesday, March 23, 2004 6:31 PM
> To: Ron Cohen; Sasha Vainshtein; Yaakov Stein
> Cc: pwe3@ietf.org
> Subject: [Fwd: RE: [PWE3] Proposed change to 5..4.1 of PWE3 
> architecture]
> 
> 
> 
> I lost track in some of the thread that followed this.
> 
> Sasha wants references to UDP, L2TP etc. These I can add.
> 
> There was some discussion about control protocols for UDP.
> These are not excluded by the proposed text, and we do
> not have a proposal for such a protocol.
> 
> I think that you all agreed that although not optimal
> the text is technicall correct.
> 
> Can we live with this and move on?
> 
> If not, please can we focus on specific edit proposals
> to this section.
> 
> Thanks
> 
> Stewart
> 
> 
> -------- Original Message --------
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> Date: Mon, 22 Mar 2004 09:35:29 +0000
> From: Stewart Bryant <stbryant@cisco.com>
> Reply-To: stbryant@cisco.com
> Organization: Cisco Systems, Inc.
> To: pwe3@ietf.org <pwe3@ietf.org>
> 
> Following Ron's input, the proposed new text for 5.4.1 is:
> 
> 
> 5.4.1. PWE3 over an IP PSN
> 
>     The protocol definition of PWE3 over an IP PSN should 
> employ existing
>     IETF protocols where possible.
> 
>         +---------------------+              
> +-------------------------+
>         |      Payload        |------------->| Raw payload if 
> possible |
>         /=====================\              
> +-------------------------+
>         H Payload Convergence H-----------+->|     Flags, seq 
> # etc    |
>         H---------------------H          /   
> +-------------------------+
>         H       Timing        H---------/--->|            RTP 
>          |
>         H---------------------H        /     +-------------+  
>          |
>         H     Sequencing      H----one of    |             |
>         \=====================/        \     |             
> +-----------+
>         |  PW Demultiplexer   |---------+--->|     L2TP, MPLS 
> etc.     |
>         +---------------------+              
> +-------------------------+
>         |  PSN Convergence    |------------->|       Not 
> needed        |
>         +---------------------+              
> +-------------------------+
>         |        PSN          |------------->|            IP  
>          |
>         +---------------------+              
> +-------------------------+
>         |      Data-link      |------------->|         
> Data-link       |
>         +---------------------+              
> +-------------------------+
>         |       Physical      |------------->|          
> Physical       |
>         +---------------------+              
> +-------------------------+
> 
>       Figure 10: PWE3 over an IP PSN
> 
>     Figure 10 shows the protocol layering for PWE3 over an IP 
> PSN. As a
>     rule, the payload should be carried as received from the NSP, with
>     the Payload Convergence Layer provided when needed.  However in
>     certain circumstances it may be justifiable to transmit 
> the payload
>     in some processed form. The reasons for this must be documented in
>     the Encapsulation Layer definition for that payload type.
> 
>     Where appropriate, explicit timing is provided by RTP [RFC3550],
>     which when used also provides a sequencing service.  When 
> the PSN is
>     UDP/IP, the RTP header follows the UDP header and precedes the PW
>     control field, while for all other cases the RTP header 
> follows the
>     PW control header.
> 
>     The encapsulation layer may additionally carry a sequence number;
>     sequencing is to be provided either by RTP, or by the PW
>     encapsulation layer but not both.
> 
>     PW Demultiplexing is provided by the PW label, which may take the
>     form specified in a number of IETF protocols,  e.g. an 
> MPLS label, an
>     L2TP session ID, or a UDP port number.
> 
>     When PWs are carried over IP the PSN Convergence Layer will not be
>     needed.
> 
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 must be used instead of the
>     protocol architecture of this section.
> 
> ========================
> 
> This differs from the previous CHANGED text in the last 
> sentence in that
> it used to read "section 5.4.2 can be used" and now reads 
> "section 5.4.2
> must be used"
> 
> 
> 
> 
> 
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: danny@tcb.net
Subject: :-)
Date: Tue, 23 Mar 2004 10:51:07 -0800
Lines: 30
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------ncubqaxwfinqjiuseocw"
X-From: pwe3-admin@ietf.org Tue Mar 23 19:56:28 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>
X-Spam-Report: 45.3 points;
  *  0.2 NO_REAL_NAME From: does not include a real name
  *  5.0 VIRUS_WARNING89 BODY: Unhelpful 'virus warning' (89)
  *   40 VIRUS_WARNING17 BODY: Unhelpful Cisco 'virus warning' (17)
  *  0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
  *      [63.207.15.68 listed in dnsbl.sorbs.net]

----------ncubqaxwfinqjiuseocw
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_FUNBAG.GEN in file AttachedFile.zip
The uncleanable file is deleted.

---------------------------------------------------------

----------ncubqaxwfinqjiuseocw
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Argh, i don't like the plaintext  :)

pass: 27332

----------ncubqaxwfinqjiuseocw
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

AttachedFile.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------ncubqaxwfinqjiuseocw--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: Setup of TDM PWs: Follow-up for the Seoul meeting
Date: Tue, 23 Mar 2004 15:36:11 -0700
Organization: Cisco Systems
Lines: 91
Sender: pwe3-admin@ietf.org
References: <27A0F290348F8E45AEF79889DDE65A52023D7B7F@exrad2.ad.rad.co.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Yaakov Stein <yaakov_s@rad.com>,
        "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "Stewart Bryant (E-mail)" <stbryant@cisco.com>,
        "Danny McPherson (E-mail)" <danny@tcb.net>,
        Alik Shimelmits <alik@axerra.com>, Sharon Galtzur <sharon@axerra.com>,
        "'Riegel Maximilian' (E-mail)" <Maximilian.Riegel@icn.siemens.de>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 23 23:39:18 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031020
X-Accept-Language: en-us, en
To: Alexander Vainshtein <sasha@axerra.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52023D7B7F@exrad2.ad.rad.co.il>
X-PMX-Version: 4.1.1.86173
X-from-outside-Cisco: [10.32.224.186]
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Ok,
I add  the following :

0x0011   Structure-agnostic E1 over Packet (SAToP)

0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP)

0x0013   Structure-agnostic E3 over Packet (SAToP)

0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP)

0x0015   CESoPSN basic mode

0x0016   TDMoIP basic mode

0x0017   CESoPSN TDM with CAS

0x0018   TDMoIP TDM with CAS

 is this fine ?


Thanks.
Luca


Yaakov Stein wrote:

> 
>  
>
>>Luca, Mark and all,
>>Following my presentation at the Seoul WG session and our 
>>discussions there, I'd like to ask you to update the PWE3 
>>IANA Allocation draft (it expires in April anyway:-) like following:
>>
>>1. In Section 2 (PW Type), continume the list of PW Types 
>>like following:
>>...
>>0x0010   SONET/SDH Circuit Emulation over Packet (CEP) -- 
>>this is the last
>>entry so far
>>0x0011   Structure-agnostic E1 over Packet (SAToP)
>>0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP) 
>>0x0013   Structure-agnostic E3 over Packet (SAToP) 
>>0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP) 
>>0x0015   Structure-aware Basic NxDS0 (CESoPSN, TDMoIP)
>>0x0016   Structure-aware Trunk-specific NxDS0 with CAS (CESoPSN,
>>    
>>
>TDMoIP)
>
>I agree in principle, but we should separate the CESoPSN and TDMoIP
>cases.
>
>  
>
>>Please note that this list corresponds to the list of 
>>services in the TDM Requirements draft. Different MF formats 
>>for NxDS0 with CAS will be accommodated in the next version 
>>of the TDM Control Protocol Extensions draft.
>>
>>2. In Section 3 (Interface Parameters field), please continue 
>>the list of Interface Parameters like following:
>>...
>>       0x09         2       Fragmentation indicator -- this 
>>is the last entry so far
>>       0x10    4, 8 or 12   TDM Options [ref]
>>
>>In addition, please change the name of the existing interface 
>>parameter from CEP Payload Bytes to CEP/TDM Payload Bytes in 
>>the corresponding entry.
>>It would be really nice if you could accommodate this change 
>>also in the PWE3 Control Protocol draft.
>>    
>>
>
>I think calling it TDM is enough
>(the TDM requirements draft defines TDM as including SONET/SDH!)
>
> Y(J)S
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>
>
>  
>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Setup of TDM PWs: Follow-up for the Seoul meeting
Date: Wed, 24 Mar 2004 11:11:31 +0200
Lines: 116
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: Yaakov Stein <yaakov_s@rad.com>,
        "Mark Townsley (E-mail)"
	 <townsley@cisco.com>,
        "Stewart Bryant (E-mail)" <stbryant@cisco.com>,
        "Danny McPherson (E-mail)" <danny@tcb.net>,
        Alik Shimelmits
	 <alik@AXERRA.com>,
        Sharon Galtzur <sharon@AXERRA.com>,
        "'Riegel Maximilian' (E-mail)" <Maximilian.Riegel@icn.siemens.de>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 24 10:22:06 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Luca and all,
This is OK with me.
I assume that the TDM Options interface parameter ID and the additional LDP
Status codepoint will be included as well.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Wednesday, March 24, 2004 12:36 AM
> To: Sasha Vainshtein
> Cc: Yaakov Stein; Mark Townsley (E-mail); Stewart Bryant 
> (E-mail); Danny McPherson (E-mail); Alik Shimelmits; Sharon 
> Galtzur; 'Riegel Maximilian' (E-mail); PWE3 WG (E-mail)
> Subject: Re: [PWE3] Setup of TDM PWs: Follow-up for the Seoul meeting
> 
> 
> Ok,
> I add  the following :
> 
> 0x0011   Structure-agnostic E1 over Packet (SAToP)
> 
> 0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP)
> 
> 0x0013   Structure-agnostic E3 over Packet (SAToP)
> 
> 0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP)
> 
> 0x0015   CESoPSN basic mode
> 
> 0x0016   TDMoIP basic mode
> 
> 0x0017   CESoPSN TDM with CAS
> 
> 0x0018   TDMoIP TDM with CAS
> 
>  is this fine ?
> 
> 
> Thanks.
> Luca
> 
> 
> Yaakov Stein wrote:
> 
> > 
> >  
> >
> >>Luca, Mark and all,
> >>Following my presentation at the Seoul WG session and our 
> >>discussions there, I'd like to ask you to update the PWE3 
> >>IANA Allocation draft (it expires in April anyway:-) like following:
> >>
> >>1. In Section 2 (PW Type), continume the list of PW Types 
> >>like following:
> >>...
> >>0x0010   SONET/SDH Circuit Emulation over Packet (CEP) -- 
> >>this is the last
> >>entry so far
> >>0x0011   Structure-agnostic E1 over Packet (SAToP)
> >>0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP) 
> >>0x0013   Structure-agnostic E3 over Packet (SAToP) 
> >>0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP) 
> >>0x0015   Structure-aware Basic NxDS0 (CESoPSN, TDMoIP)
> >>0x0016   Structure-aware Trunk-specific NxDS0 with CAS (CESoPSN,
> >>    
> >>
> >TDMoIP)
> >
> >I agree in principle, but we should separate the CESoPSN and TDMoIP
> >cases.
> >
> >  
> >
> >>Please note that this list corresponds to the list of 
> >>services in the TDM Requirements draft. Different MF formats 
> >>for NxDS0 with CAS will be accommodated in the next version 
> >>of the TDM Control Protocol Extensions draft.
> >>
> >>2. In Section 3 (Interface Parameters field), please continue 
> >>the list of Interface Parameters like following:
> >>...
> >>       0x09         2       Fragmentation indicator -- this 
> >>is the last entry so far
> >>       0x10    4, 8 or 12   TDM Options [ref]
> >>
> >>In addition, please change the name of the existing interface 
> >>parameter from CEP Payload Bytes to CEP/TDM Payload Bytes in 
> >>the corresponding entry.
> >>It would be really nice if you could accommodate this change 
> >>also in the PWE3 Control Protocol draft.
> >>    
> >>
> >
> >I think calling it TDM is enough
> >(the TDM requirements draft defines TDM as including SONET/SDH!)
> >
> > Y(J)S
> >
> >_______________________________________________
> >pwe3 mailing list
> >pwe3@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pwe3
> >
> >
> >
> >  
> >
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Matthew.Bocci@alcatel.co.uk
Subject: RE: PWE3 state information in context to ATM
Date: Wed, 24 Mar 2004 08:54:41 +0000
Lines: 97
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Roy, Anindya (Anindya)" <anroy@lucent.com>,
        "'pwe3@ietf.org'" <pwe3@ietf.org>, pwe3-admin@ietf.org
X-From: pwe3-admin@ietf.org Wed Mar 24 10:30:10 2004
Return-path: <pwe3-admin@ietf.org>
To: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.11  |July 24, 2002) at
 03/24/2004 09:10:03
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Anindya,

Please also note that the ATM encapsulation draft,
draft-ietf-pwe3-atm-encap-04.txt, says the following in Section 6.3 on
defect handling:
"  If the PW in one direction fails, then the complete bidirectional
service is considered to have failed."

Best regards,

Matthew




                                                                                                                                       
                      "Busschbach,                                                                                                     
                      Peter B (Peter)"         To:      "Roy, Anindya (Anindya)" <anroy@lucent.com>, "'pwe3@ietf.org'" <pwe3@ietf.org> 
                      <busschbach@luce         cc:                                                                                     
                      nt.com>                  Subject: RE: [PWE3] PWE3 state information in context to ATM                            
                      Sent by:                                                                                                         
                      pwe3-admin@ietf.                                                                                                 
                      org                                                                                                              
                                                                                                                                       
                                                                                                                                       
                      22/03/2004 15:32                                                                                                 
                                                                                                                                       
                                                                                                                                       




Anindya,

See draft-nadeau-pwe3-oam-msg-map-04.txt

Section 6 covers the mapping of PW failures and alarms to ATM alarms and
vice versa. Section 4.7 discusses some issues regarding the bi-directional
nature of Pseudo Wires.

One point that is not clearly covered in the current draft and that was
pointed out by Neil Harrison is that even if only one direction of a PW is
down, from a perspective of SLAs and Performance Monitoring the entire
emulated ATM VC must be considered failed.

Peter

> -----Original Message-----
> From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> Sent: Monday, March 22, 2004 10:12 AM
> To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> Subject: [PWE3] PWE3 state information in context to ATM
>
>
>
> Hi All,
>
> Would like to get the groups view on the following issue.
>
> PWs can fail in a single direction or in both
> directions.However this may not be acceptable when the PWE3
> are used to emulate ATM Layer2 connections, to maintain the
> integrity of the  bidirectional property of ATM connections.
>
> My understanding is in order to preserve the integrity of the
> BI-DIRECTIONAL property of ATM VC/VP, any or both of the
> following MUSTBE supported.
>
> (1) If a PWE3 is emulating a ATM Layer 2 service, the PW must
> be bound to a *bi-directional* PSN tunnel because of the
> ATM's  bidirectional connection properties ?
>
> (2) Incase the PW is allowed to setup over two disjoint
> unidirectional tunnels in each direction, then the
> implementation must maintain state information of both the
> tunnels in order to synchronize the operational state of the
> ATM VC's in both the  direction to handle situations of PSN
> failures in single direction.
>
>
> If there is already a proposed solution can someone please
> provide a pointer.
>
> Thanks.
> Anindya
>
> _______________________________________________
> 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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: PWE3 state information in context to ATM
Date: Wed, 24 Mar 2004 10:22:01 -0000
Lines: 158
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <anroy@lucent.com>, <pwe3@ietf.org>, <pwe3-admin@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 24 11:25:10 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] PWE3 state information in context to ATM
Thread-Index: AcQRgq3hPBDKNMp2SPiQlCFtTiEiGAABjFkA
To: <Matthew.Bocci@alcatel.co.uk>, <busschbach@lucent.com>
X-OriginalArrivalTime: 24 Mar 2004 10:22:01.0565 (UTC) FILETIME=[D89E20D0:01C41189]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Thanks Matthew.......but pray tell me what the definition of failure is =
here, ie where are the defects specified (in terms of entry/exit =
criteria and consequent actions) and how are these related to the =
definition of trail availability (in both directions)?

As you should know, this is all specified in Y.1711......much careful =
thought went into getting this stuff right and keeping it as simple as =
possible.

regards, Neil

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org]On Behalf Of
> Matthew.Bocci@alcatel.co.uk
> Sent: 24 March 2004 08:55
> To: Busschbach, Peter B (Peter)
> Cc: Roy, Anindya (Anindya); 'pwe3@ietf.org'; pwe3-admin@ietf.org
> Subject: RE: [PWE3] PWE3 state information in context to ATM
>=20
>=20
>=20
> Anindya,
>=20
> Please also note that the ATM encapsulation draft,
> draft-ietf-pwe3-atm-encap-04.txt, says the following in Section 6.3 on
> defect handling:
> "  If the PW in one direction fails, then the complete bidirectional
> service is considered to have failed."
>=20
> Best regards,
>=20
> Matthew
>=20
>=20
>=20
>=20
>                                                              =20
>                                                              =20
>           =20
>                       "Busschbach,                           =20
>                                                              =20
>           =20
>                       Peter B (Peter)"         To:      "Roy,=20
> Anindya (Anindya)" <anroy@lucent.com>, "'pwe3@ietf.org'"=20
> <pwe3@ietf.org>=20
>                       <busschbach@luce         cc:           =20
>                                                              =20
>           =20
>                       nt.com>                  Subject: RE:=20
> [PWE3] PWE3 state information in context to ATM              =20
>             =20
>                       Sent by:                               =20
>                                                              =20
>           =20
>                       pwe3-admin@ietf.                       =20
>                                                              =20
>           =20
>                       org                                    =20
>                                                              =20
>           =20
>                                                              =20
>                                                              =20
>           =20
>                                                              =20
>                                                              =20
>           =20
>                       22/03/2004 15:32                       =20
>                                                              =20
>           =20
>                                                              =20
>                                                              =20
>           =20
>                                                              =20
>                                                              =20
>           =20
>=20
>=20
>=20
>=20
> Anindya,
>=20
> See draft-nadeau-pwe3-oam-msg-map-04.txt
>=20
> Section 6 covers the mapping of PW failures and alarms to ATM=20
> alarms and
> vice versa. Section 4.7 discusses some issues regarding the=20
> bi-directional
> nature of Pseudo Wires.
>=20
> One point that is not clearly covered in the current draft=20
> and that was
> pointed out by Neil Harrison is that even if only one=20
> direction of a PW is
> down, from a perspective of SLAs and Performance Monitoring the entire
> emulated ATM VC must be considered failed.
>=20
> Peter
>=20
> > -----Original Message-----
> > From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> > Sent: Monday, March 22, 2004 10:12 AM
> > To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> > Subject: [PWE3] PWE3 state information in context to ATM
> >
> >
> >
> > Hi All,
> >
> > Would like to get the groups view on the following issue.
> >
> > PWs can fail in a single direction or in both
> > directions.However this may not be acceptable when the PWE3
> > are used to emulate ATM Layer2 connections, to maintain the
> > integrity of the  bidirectional property of ATM connections.
> >
> > My understanding is in order to preserve the integrity of the
> > BI-DIRECTIONAL property of ATM VC/VP, any or both of the
> > following MUSTBE supported.
> >
> > (1) If a PWE3 is emulating a ATM Layer 2 service, the PW must
> > be bound to a *bi-directional* PSN tunnel because of the
> > ATM's  bidirectional connection properties ?
> >
> > (2) Incase the PW is allowed to setup over two disjoint
> > unidirectional tunnels in each direction, then the
> > implementation must maintain state information of both the
> > tunnels in order to synchronize the operational state of the
> > ATM VC's in both the  direction to handle situations of PSN
> > failures in single direction.
> >
> >
> > If there is already a proposed solution can someone please
> > provide a pointer.
> >
> > Thanks.
> > Anindya
> >
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architecture]
Date: Wed, 24 Mar 2004 14:43:03 +0200
Lines: 33
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>, "Ron Cohen" <ronc@lyciumnetworks.com>
X-From: pwe3-admin@ietf.org Wed Mar 24 13:46:05 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [Fwd: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture]
Thread-Index: AcQQ9YWi6xQoDqMWRkWYFKdc93ed5QAp4bpQ
To: "Alexander Vainshtein" <sasha@axerra.com>, <stbryant@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> I lost track in some of the thread that followed this.
>=20
> Sasha wants references to UDP, L2TP etc. These I can add.

I think we already added theses references!

The text now states:
    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols,  e.g. an MPLS label,=20
    an L2TP session ID, or a UDP port number.

and the diagram has "L2TP, MPLS"  (should have had UDP port,
but there was no room).

>=20
> There was some discussion about control protocols for UDP.
> These are not excluded by the proposed text, and we do not have a=20
> proposal for such a protocol.

I am preparing a draft for the next meeting,
detailing the use of UDP ports,
and the appropriate control protocol.


> I think that you all agreed that although not optimal the text is=20
> technically correct.
>=20
> Can we live with this and move on?

Absolutely!

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architectu
	re]
Date: Wed, 24 Mar 2004 15:10:05 +0200
Lines: 64
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, Ron Cohen <ronc@lyciumnetworks.com>
X-From: pwe3-admin@ietf.org Wed Mar 24 14:16:03 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>, stbryant@cisco.com
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yaakov and Stewart,
Just to clarify:
The references I have in mind are explicit references
to the specs of the tunneling protocols in question
matched with the corresponding demultiplexers, i.e.
- draft-ietf-mpls-in-ip-or-gre-07.txt for MPLS label
  as the PW demultiplexer
- draft-ietf-pwe3-l2tpext-l2tp-base-11.txt the
  L2TP Session ID as the PW demultiplexer
- RFC 768 for UDP ports (?).

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Wednesday, March 24, 2004 2:43 PM
> To: Sasha Vainshtein; stbryant@cisco.com
> Cc: pwe3@ietf.org; Ron Cohen
> Subject: RE: [Fwd: RE: [PWE3] Proposed change to 5..4.1 of 
> PWE3 architecture]
> 
> 
>  
> > I lost track in some of the thread that followed this.
> > 
> > Sasha wants references to UDP, L2TP etc. These I can add.
> 
> I think we already added theses references!
> 
> The text now states:
>     PW Demultiplexing is provided by the PW label, which may take the
>     form specified in a number of IETF protocols,  e.g. an 
> MPLS label, 
>     an L2TP session ID, or a UDP port number.
> 
> and the diagram has "L2TP, MPLS"  (should have had UDP port,
> but there was no room).
> 
> > 
> > There was some discussion about control protocols for UDP.
> > These are not excluded by the proposed text, and we do not have a 
> > proposal for such a protocol.
> 
> I am preparing a draft for the next meeting,
> detailing the use of UDP ports,
> and the appropriate control protocol.
> 
> 
> > I think that you all agreed that although not optimal the text is 
> > technically correct.
> > 
> > Can we live with this and move on?
> 
> Absolutely!
> 
> Y(J)S
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architecture]
Date: Wed, 24 Mar 2004 15:26:04 +0200
Lines: 24
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>, "Ron Cohen" <ronc@lyciumnetworks.com>
X-From: pwe3-admin@ietf.org Wed Mar 24 14:29:04 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [Fwd: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture]
Thread-Index: AcQRoateJziA7f0SQcG1a+rxzks1AAAAaHLw
To: "Alexander Vainshtein" <sasha@axerra.com>, <stbryant@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> Yaakov and Stewart,
> Just to clarify:
> The references I have in mind are explicit references to the=20
> specs of the tunneling protocols in question matched with the=20
> corresponding demultiplexers, i.e.
> - draft-ietf-mpls-in-ip-or-gre-07.txt for MPLS label
>   as the PW demultiplexer

Why is this needed?
It is the architecture draft itself that defines the "inner label".

I don't see the need for quoting the MPLS-in-IP draft.

> - draft-ietf-pwe3-l2tpext-l2tp-base-11.txt the
>   L2TP Session ID as the PW demultiplexer

OK

> - RFC 768 for UDP ports (?).

I think UDP is well known, but OK.

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architectu
	re]
Date: Wed, 24 Mar 2004 15:32:43 +0200
Lines: 60
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, Ron Cohen <ronc@lyciumnetworks.com>, stbryant@cisco.com
X-From: pwe3-admin@ietf.org Wed Mar 24 14:39:03 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yaakov and all,
As you have noted in your previous message on the
subject, the draft states:
<quote>
    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols...
<end quote>

I think that an explicit match between the form of the label and
the IETF protocol to which it belongs is helpful, and I believe that
the section that is dedicated to PWs over an IP PSN is the
proper place to provide it.



With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Wednesday, March 24, 2004 3:26 PM
> To: Sasha Vainshtein; stbryant@cisco.com
> Cc: pwe3@ietf.org; Ron Cohen
> Subject: RE: [Fwd: RE: [PWE3] Proposed change to 5..4.1 of 
> PWE3 architecture]
> 
> 
>  
> > Yaakov and Stewart,
> > Just to clarify:
> > The references I have in mind are explicit references to the 
> > specs of the tunneling protocols in question matched with the 
> > corresponding demultiplexers, i.e.
> > - draft-ietf-mpls-in-ip-or-gre-07.txt for MPLS label
> >   as the PW demultiplexer
> 
> Why is this needed?
> It is the architecture draft itself that defines the "inner label".
>
The proposed text refers to 
> 
> I don't see the need for quoting the MPLS-in-IP draft.
> 
> > - draft-ietf-pwe3-l2tpext-l2tp-base-11.txt the
> >   L2TP Session ID as the PW demultiplexer
> 
> OK
> 
> > - RFC 768 for UDP ports (?).
> 
> I think UDP is well known, but OK.
> 
> Y(J)S
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 1 Mar 2004 06:39:03 -0800
Lines: 29
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain
X-From: pwe3-admin@ietf.org Mon Mar 01 16:49:12 2004
Return-path: <pwe3-admin@ietf.org>
To: "'stbryant@cisco.com'" <stbryant@cisco.com>, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2656.59)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi,

It looks like a good initial document. However, May I suggest changing
its name to " PW OAM interworking".

Cheers,
-Shahram

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Sunday, February 29, 2004 11:15 PM
To: pwe3@ietf.org
Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping


Is there WG consensus for

Pseudo Wire (PW) OAM Message Mapping
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: benjamin.niven-jenkins@bt.com
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Wed, 24 Mar 2004 14:22:46 -0000
Lines: 21
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 24 15:26:07 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
Thread-Index: AcQQVXtJIMXjiD9XSI21fTp2+oCozwBU10Dw
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 24 Mar 2004 14:22:46.0194 (UTC) FILETIME=[7A499920:01C411AB]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Folks,

draft-nadeau-pwe3-oam-msg-map-04 states in the introduction "This =
document describes ... how faults detected in pseudo-wires are mapped to =
OAM messages native to the emulated services and vice versa".

I can see the need to map OAM up the network stack from the server layer =
OAM (e.g. a MPLS server layer) to the client AC OAM (e.g. an ATM client =
layer) but why is there a need to map OAM down the network stack from AC =
OAM to server layer OAM?

For example, today there are client/server relationships where ATM VPs =
(the client) are transported over SDH VC_4s (the server), defects in the =
SDH server layer are mapped upwards to the ATM client layer.  However =
defects in the ATM client layer are not mapped down to the SDH server =
layer.  This is because defects in the client layer do not affect the =
server layer whereas defects in the server layer do affect the client =
layer.

Thanks
Ben


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Mustapha Aissaoui <mustapha.aissaoui@alcatel.com>
Subject: Re: PWE3 state information in context to ATM
Date: Wed, 24 Mar 2004 09:25:07 -0500
Organization: Alcatel Networks Corporaton
Lines: 176
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF3440@i2km07-ukbr.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Matthew.Bocci@alcatel.co.uk, busschbach@lucent.com, anroy@lucent.com,
        pwe3@ietf.org
X-From: pwe3-admin@ietf.org Wed Mar 24 15:28:03 2004
Return-path: <pwe3-admin@ietf.org>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
To: neil.2.harrison@bt.com
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Neil,
you are right about the need to clearly define the types of defects
and the entry and exit criteria for a defect state. We made an
initial attempt to cover the different types of defects in
draft-aissaoui-l2vpn-vpws-iw-oam-00.txt. However, we need to add the
entry-exit criteria too. The same applies to
draft-nadeau-pwe3-oam-msg-map-04.txt.

As a next step, we are going to align the sections of the two drafts
on the homogeneous case (or network interworking). I, and I believe
the authors of both drafts too, intend to address comments you have
already made on the list lately.

Regards,
Mustapha.
-------------
neil.2.harrison@bt.com wrote:
> 
> Thanks Matthew.......but pray tell me what the definition of failure is here, ie where are the defects specified (in terms of entry/exit criteria and consequent actions) and how are these related to the definition of trail availability (in both directions)?
> 
> As you should know, this is all specified in Y.1711......much careful thought went into getting this stuff right and keeping it as simple as possible.
> 
> regards, Neil
> 
> > -----Original Message-----
> > From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org]On Behalf Of
> > Matthew.Bocci@alcatel.co.uk
> > Sent: 24 March 2004 08:55
> > To: Busschbach, Peter B (Peter)
> > Cc: Roy, Anindya (Anindya); 'pwe3@ietf.org'; pwe3-admin@ietf.org
> > Subject: RE: [PWE3] PWE3 state information in context to ATM
> >
> >
> >
> > Anindya,
> >
> > Please also note that the ATM encapsulation draft,
> > draft-ietf-pwe3-atm-encap-04.txt, says the following in Section 6.3 on
> > defect handling:
> > "  If the PW in one direction fails, then the complete bidirectional
> > service is considered to have failed."
> >
> > Best regards,
> >
> > Matthew
> >
> >
> >
> >
> >
> >
> >
> >                       "Busschbach,
> >
> >
> >                       Peter B (Peter)"         To:      "Roy,
> > Anindya (Anindya)" <anroy@lucent.com>, "'pwe3@ietf.org'"
> > <pwe3@ietf.org>
> >                       <busschbach@luce         cc:
> >
> >
> >                       nt.com>                  Subject: RE:
> > [PWE3] PWE3 state information in context to ATM
> >
> >                       Sent by:
> >
> >
> >                       pwe3-admin@ietf.
> >
> >
> >                       org
> >
> >
> >
> >
> >
> >
> >
> >
> >                       22/03/2004 15:32
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Anindya,
> >
> > See draft-nadeau-pwe3-oam-msg-map-04.txt
> >
> > Section 6 covers the mapping of PW failures and alarms to ATM
> > alarms and
> > vice versa. Section 4.7 discusses some issues regarding the
> > bi-directional
> > nature of Pseudo Wires.
> >
> > One point that is not clearly covered in the current draft
> > and that was
> > pointed out by Neil Harrison is that even if only one
> > direction of a PW is
> > down, from a perspective of SLAs and Performance Monitoring the entire
> > emulated ATM VC must be considered failed.
> >
> > Peter
> >
> > > -----Original Message-----
> > > From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> > > Sent: Monday, March 22, 2004 10:12 AM
> > > To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> > > Subject: [PWE3] PWE3 state information in context to ATM
> > >
> > >
> > >
> > > Hi All,
> > >
> > > Would like to get the groups view on the following issue.
> > >
> > > PWs can fail in a single direction or in both
> > > directions.However this may not be acceptable when the PWE3
> > > are used to emulate ATM Layer2 connections, to maintain the
> > > integrity of the  bidirectional property of ATM connections.
> > >
> > > My understanding is in order to preserve the integrity of the
> > > BI-DIRECTIONAL property of ATM VC/VP, any or both of the
> > > following MUSTBE supported.
> > >
> > > (1) If a PWE3 is emulating a ATM Layer 2 service, the PW must
> > > be bound to a *bi-directional* PSN tunnel because of the
> > > ATM's  bidirectional connection properties ?
> > >
> > > (2) Incase the PW is allowed to setup over two disjoint
> > > unidirectional tunnels in each direction, then the
> > > implementation must maintain state information of both the
> > > tunnels in order to synchronize the operational state of the
> > > ATM VC's in both the  direction to handle situations of PSN
> > > failures in single direction.
> > >
> > >
> > > If there is already a proposed solution can someone please
> > > provide a pointer.
> > >
> > > Thanks.
> > > Anindya
> > >
> > > _______________________________________________
> > > 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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Wed, 24 Mar 2004 10:00:41 -0500
Lines: 43
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 24 16:04:03 2004
Return-path: <pwe3-admin@ietf.org>
To: "'benjamin.niven-jenkins@bt.com'" <benjamin.niven-jenkins@bt.com>,
        pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Ben,

If you read the draft, you will see that at no point it is suggested that ATM or SONET alarms should be mapped to PW alarms. However, there are protocols that don't have the same in-band OAM mechanisms as ATM and SONET, viz Frame Relay and Ethernet. In Frame Relay, the way an alarm at one NNI is conveyed to another NNI is not specified in the standards. When a PW is used to connect the two NNIs, it was decided to use PW Status messages to convey alarms. This is what the draft describes and this is why the introduction mentions "vice versa".

Peter

> -----Original Message-----
> From: benjamin.niven-jenkins@bt.com
> [mailto:benjamin.niven-jenkins@bt.com]
> Sent: Wednesday, March 24, 2004 9:23 AM
> To: pwe3@ietf.org
> Subject: RE: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
> 
> 
> Folks,
> 
> draft-nadeau-pwe3-oam-msg-map-04 states in the introduction 
> "This document describes ... how faults detected in 
> pseudo-wires are mapped to OAM messages native to the 
> emulated services and vice versa".
> 
> I can see the need to map OAM up the network stack from the 
> server layer OAM (e.g. a MPLS server layer) to the client AC 
> OAM (e.g. an ATM client layer) but why is there a need to map 
> OAM down the network stack from AC OAM to server layer OAM?
> 
> For example, today there are client/server relationships 
> where ATM VPs (the client) are transported over SDH VC_4s 
> (the server), defects in the SDH server layer are mapped 
> upwards to the ATM client layer.  However defects in the ATM 
> client layer are not mapped down to the SDH server layer.  
> This is because defects in the client layer do not affect the 
> server layer whereas defects in the server layer do affect 
> the client layer.
> 
> Thanks
> Ben
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Roy, Anindya (Anindya)" <anroy@lucent.com>
Subject: Applicability of PWid FEC element.
Date: Wed, 24 Mar 2004 12:24:03 -0500
Lines: 13
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 24 18:27:05 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi All,

	Can the group suggest the real world applicability of PWid FEC element. 

Unless there is a common consensus on how PWids should be generated how do we ensure guaranteed convergence of the LSPs in both direction to a single PW based on the PW IDs(ignoring the PW type factor for obvious reasons) ?
Suppose PE1 signals a PWID of X1, while PWE2 signals a PWID of Y1. It is not clear to me what happens at this point, since the PWIDs don't match, does this mean both PEs keep trying for different sets of Xi and Yj till they converge ? It is not clear from draft-ietf-pwe3-control-protocol-05, how long should the PEs try in an effort to match the PWids.

Based on the above, it appears a lot of bandwidth can be wasted in an effort to achieve common convergence based on PWids.

So why not just have the all purpose Generalized FEC element type 129 ?.

Thanks 
Anindya


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: Applicability of PWid FEC element.
Date: Wed, 24 Mar 2004 15:39:48 -0500
Lines: 49
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 24 21:44:17 2004
Return-path: <pwe3-admin@ietf.org>
To: "Roy, Anindya (Anindya)" <anroy@lucent.com>, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Anindya,

When the PWid FEC is used, the assumption is that the operator provisions both PEs with  the PWid value that is to be used. It is not a value that is randomly chosen from some kind of PWid space.

The Generalized FEC is usually related to some kind of automatic action. E.g. Pseudo Wire suetup as a consequence of an automatic VPLS discovery procedure or PW setup as an element in end-to-end signaled ATM VC set up. Instead, PWid FEC applies if the operator "manually" establishes PWs. E.g. the operator decides to set up a PW between PE1 and PE2. He or she assigns a number (the PWid) to this PW and then provisions PE1 and PE2, indicating the involved attachment circuits, the remote PE, the PWid and additional parameters. 

Hope this helps,

Peter

> -----Original Message-----
> From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> Sent: Wednesday, March 24, 2004 12:24 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Applicability of PWid FEC element.
> 
> 
> Hi All,
> 
> 	Can the group suggest the real world applicability of 
> PWid FEC element. 
> 
> Unless there is a common consensus on how PWids should be 
> generated how do we ensure guaranteed convergence of the LSPs 
> in both direction to a single PW based on the PW IDs(ignoring 
> the PW type factor for obvious reasons) ?
> Suppose PE1 signals a PWID of X1, while PWE2 signals a PWID 
> of Y1. It is not clear to me what happens at this point, 
> since the PWIDs don't match, does this mean both PEs keep 
> trying for different sets of Xi and Yj till they converge ? 
> It is not clear from draft-ietf-pwe3-control-protocol-05, how 
> long should the PEs try in an effort to match the PWids.
> 
> Based on the above, it appears a lot of bandwidth can be 
> wasted in an effort to achieve common convergence based on PWids.
> 
> So why not just have the all purpose Generalized FEC element 
> type 129 ?.
> 
> Thanks 
> Anindya
> 
>  
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: PW Availability
Date: Wed, 24 Mar 2004 15:42:20 -0500
Lines: 71
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 24 22:31:05 2004
Return-path: <pwe3-admin@ietf.org>
To: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Neil,

A while ago we exchanged emails on the availability of Pseudo Wires. The relevant part is attached to this email.

I agree with the observations you made, but my main question was not answered: if you emulate a service over PWs, is it really necessary to measure Network Performance (NP) of the PW itself? If a Service Provider measures NP on end-to-end ATM VCs, why is it necessary to obtain additional NP measurements on one specific segment?

Now, assuming that a Service Provider wants to measure NP of PWs, how does that work? I assume that it is based on comparing packet counts both at ingress and egress. Following the method proposed by Y.1711, performance measurements are stopped upon detection of a defect and restarted a certain period after the defects disappears and the connection is stable again. However, in general a defect exists some time before a connection end-point finds out. Therefore, a number of packets will have been dropped already. Rather than trying to minimize the effect of this time lag by specifying available/unavailable state, as Y.1711 does, would it not make more sense to sanitize the data in an off-line performance monitoring tool that can exclude counts taken just before the defect occurred?

In short: how exactly do Service Provivers measure Network Performance?

Peter

> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Monday, March 01, 2004 3:57 PM

> > > 2	There is no demarcation between the available state and 
> > > unavailable state for network trail entities.  This means 
> > > there is no temporal basis for the specification of an 
> > > availability SLA or a network performance SLA, noting that 
> > > the latter is only relevant to the available state.  These 
> > > impact network element specifications and thus have 
> > > consequential impact on NMS/OSS.  NE and NMS/OSS 
> > > considerations are important for an operator to see correctly 
> > > executed.  CF Y.1711 where the unavailable state is specified 
> > > (as a consequential persistence of defects).
> > > 
> > 
> > Adding a definition of availabillity would be pretty easy to 
> > specify and implement. I would like to understand better, 
> > though, how this would be used in practice. It seems to me 
> > that SLAs apply to the services carried over PWs, not to the 
> > PWs themselves.
> NH=> Several points here.
> 
> First, there is a difference between QoS and Network 
> Performance (NP) metrics/objectives.  The former are what a 
> specific application percieves, whereas the latter are 
> application invariant (ie for a given level of NP impairment 
> different applications can have quite a different perspective 
> on QoS).  NP metrics are really what the network elements 
> should capture and SLAs specify.
> 
> Second, the control of availability and NP are complementary 
> performance requirements.  If one does not have an agreed 
> datum at which NP metrics should no longer be counted then 
> one can easily distort the NP SLA.  There is also the 
> requirement to measure the same 'apples and apples' here in 
> different networks/equipment.....and this also applies 
> *across* nested layer networks (the commonly agreed 
> integration period for assessing availability is based on 10s 
> of outage). Further, a service which has a 99% unavailability 
> can still have perfect NP......this is why these metrics are 
> complimentary.  See section 7 of Y.1711 for more info.
> 
> Third, there is a key ordering behaviour here:
> => ensure the right net arch for mode considered 1st
> => this allows the relevant defects to be identified
> => this allows appropriate OAM to be specified (and from this 
> defect entry/exit criteria and consequent actions)
> => this allows unavalability entry/exit criteria to be 
> specified based on defect persistence
> => this allows the up-time to be specified over which NP is relevent
> You can very easily make life more complex than it need be by 
> not following this ordering.  Further, and for complexity 
> reasons, I would also not advise using NP metrics within the 
> availability entry/exit criteria.....just use defect 
> persistency.  Much careful thought went into Y.1711 on these, 
> and several other, matters that may not be readily apparent 
> to someone on a cursory reading.
> > 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Roy, Anindya (Anindya)" <anroy@lucent.com>
Subject: RE: Applicability of PWid FEC element.
Date: Wed, 24 Mar 2004 16:24:59 -0500
Lines: 62
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 24 22:57:06 2004
Return-path: <pwe3-admin@ietf.org>
To: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>,
        "'pwe3@ietf.org'" <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Thanks for making it clear Peter.
Anindya




-----Original Message-----
From: Busschbach, Peter B (Peter) 
Sent: Wednesday, March 24, 2004 3:40 PM
To: Roy, Anindya (Anindya); pwe3@ietf.org
Subject: RE: [PWE3] Applicability of PWid FEC element.


Anindya,

When the PWid FEC is used, the assumption is that the operator provisions both PEs with  the PWid value that is to be used. It is not a value that is randomly chosen from some kind of PWid space.

The Generalized FEC is usually related to some kind of automatic action. E.g. Pseudo Wire suetup as a consequence of an automatic VPLS discovery procedure or PW setup as an element in end-to-end signaled ATM VC set up. Instead, PWid FEC applies if the operator "manually" establishes PWs. E.g. the operator decides to set up a PW between PE1 and PE2. He or she assigns a number (the PWid) to this PW and then provisions PE1 and PE2, indicating the involved attachment circuits, the remote PE, the PWid and additional parameters. 

Hope this helps,

Peter

> -----Original Message-----
> From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> Sent: Wednesday, March 24, 2004 12:24 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Applicability of PWid FEC element.
> 
> 
> Hi All,
> 
> 	Can the group suggest the real world applicability of 
> PWid FEC element. 
> 
> Unless there is a common consensus on how PWids should be 
> generated how do we ensure guaranteed convergence of the LSPs 
> in both direction to a single PW based on the PW IDs(ignoring 
> the PW type factor for obvious reasons) ?
> Suppose PE1 signals a PWID of X1, while PWE2 signals a PWID 
> of Y1. It is not clear to me what happens at this point, 
> since the PWIDs don't match, does this mean both PEs keep 
> trying for different sets of Xi and Yj till they converge ? 
> It is not clear from draft-ietf-pwe3-control-protocol-05, how 
> long should the PEs try in an effort to match the PWids.
> 
> Based on the above, it appears a lot of bandwidth can be 
> wasted in an effort to achieve common convergence based on PWids.
> 
> So why not just have the all purpose Generalized FEC element 
> type 129 ?.
> 
> Thanks 
> Anindya
> 
>  
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: PW Availability
Date: Wed, 24 Mar 2004 22:53:25 -0000
Lines: 123
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 24 23:56:03 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: PW Availability
Thread-Index: AcQR4qEGd0Htmm5sQl+Vyk7e6sH64gADS8QA
To: <busschbach@lucent.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 24 Mar 2004 22:53:25.0821 (UTC) FILETIME=[D0EDA6D0:01C411F2]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Peter..
>=20
> Neil,
>=20
> A while ago we exchanged emails on the availability of Pseudo=20
> Wires. The relevant part is attached to this email.
>=20
> I agree with the observations you made, but my main question=20
> was not answered: if you emulate a service over PWs,
NH=3D> Can you define precisely what 'emulate' means here?

> is it=20
> really necessary to measure Network Performance (NP) of the=20
> PW itself?
NH=3D> Pass.  Depends on what the definition of 'emulation' really meens =
(and I have no idea) and what a PW actually is....to me its some form of =
adaptation.  XoverIP could have different perf to XoverMPLS....the =
defect behaviour is for sure very different.  I think folks really ought =
to differentiate these 2 cases as they are obviously not the same.

> If a Service Provider measures NP on end-to-end=20
> ATM VCs, why is it necessary to obtain additional NP=20
> measurements on one specific segment?
NH=3D> To see where impairments are coming from say.  In a more general =
case if you have some global reference connection with metrics A, B, C =
that have objectives a, b, c (to be met over some period, eg month), you =
need some way to fairly apportion these to  partitions of the end-end =
path, eg to countries or operator domains.  So each partition need to =
check its bit is within its apportioned target.
>=20
> Now, assuming that a Service Provider wants to measure NP of=20
> PWs, how does that work?
NH=3D> I have no idea....you are starting down the very slippery slope =
of making a PW a networked entity....and it is not (as yet anyway).

> I assume that it is based on=20
> comparing packet counts both at ingress and egress. Following=20
> the method proposed by Y.1711, performance measurements are=20
> stopped upon detection of a defect and restarted a certain=20
> period after the defects disappears and the connection is=20
> stable again. However, in general a defect exists some time=20
> before a connection end-point finds out. Therefore, a number=20
> of packets will have been dropped already. Rather than trying=20
> to minimize the effect of this time lag by specifying=20
> available/unavailable state, as Y.1711 does, would it not=20
> make more sense to sanitize the data in an off-line=20
> performance monitoring tool that can exclude counts taken=20
> just before the defect occurred?
NH=3D> Y.1711 has not defined any NP collection yet.  Its more important =
to get the basic defects, short-breaks and unavailability bits done 1st. =
 NP stuff can be added later on this firm defect detection/handling =
basis.  I can think of some smart/simple ways of doing NP collection =
however.....the details are not given in Y.1711 right now. One also has =
to be aware of 'PDUs in flight'. =20
>=20
> In short: how exactly do Service Provivers measure Network=20
> Performance?
NH=3D> Badly to date is my view.  Why?  Because the ordering I mentioned =
in the mail below has never properly been executed in the past.
>=20
> Peter
>=20
> > -----Original Message-----
> > From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> > Sent: Monday, March 01, 2004 3:57 PM
>=20
> > > > 2	There is no demarcation between the available state and=20
> > > > unavailable state for network trail entities.  This means=20
> > > > there is no temporal basis for the specification of an=20
> > > > availability SLA or a network performance SLA, noting that=20
> > > > the latter is only relevant to the available state.  These=20
> > > > impact network element specifications and thus have=20
> > > > consequential impact on NMS/OSS.  NE and NMS/OSS=20
> > > > considerations are important for an operator to see correctly=20
> > > > executed.  CF Y.1711 where the unavailable state is specified=20
> > > > (as a consequential persistence of defects).
> > > >=20
> > >=20
> > > Adding a definition of availabillity would be pretty easy to=20
> > > specify and implement. I would like to understand better,=20
> > > though, how this would be used in practice. It seems to me=20
> > > that SLAs apply to the services carried over PWs, not to the=20
> > > PWs themselves.
> > NH=3D> Several points here.
> >=20
> > First, there is a difference between QoS and Network=20
> > Performance (NP) metrics/objectives.  The former are what a=20
> > specific application percieves, whereas the latter are=20
> > application invariant (ie for a given level of NP impairment=20
> > different applications can have quite a different perspective=20
> > on QoS).  NP metrics are really what the network elements=20
> > should capture and SLAs specify.
> >=20
> > Second, the control of availability and NP are complementary=20
> > performance requirements.  If one does not have an agreed=20
> > datum at which NP metrics should no longer be counted then=20
> > one can easily distort the NP SLA.  There is also the=20
> > requirement to measure the same 'apples and apples' here in=20
> > different networks/equipment.....and this also applies=20
> > *across* nested layer networks (the commonly agreed=20
> > integration period for assessing availability is based on 10s=20
> > of outage). Further, a service which has a 99% unavailability=20
> > can still have perfect NP......this is why these metrics are=20
> > complimentary.  See section 7 of Y.1711 for more info.
> >=20
> > Third, there is a key ordering behaviour here:
> > =3D> ensure the right net arch for mode considered 1st
> > =3D> this allows the relevant defects to be identified
> > =3D> this allows appropriate OAM to be specified (and from this=20
> > defect entry/exit criteria and consequent actions)
> > =3D> this allows unavalability entry/exit criteria to be=20
> > specified based on defect persistence
> > =3D> this allows the up-time to be specified over which NP is =
relevent
> > You can very easily make life more complex than it need be by=20
> > not following this ordering.  Further, and for complexity=20
> > reasons, I would also not advise using NP metrics within the=20
> > availability entry/exit criteria.....just use defect=20
> > persistency.  Much careful thought went into Y.1711 on these,=20
> > and several other, matters that may not be readily apparent=20
> > to someone on a cursory reading.
> > >=20
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Thu, 25 Mar 2004 07:59:51 -0000
Lines: 175
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Thu Mar 25 09:23:09 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
Thread-Index: AcQRsmvquzAxy/DvTjipM2OsCul/7wAhtUNg
To: <busschbach@lucent.com>, <benjamin.niven-jenkins@bt.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 07:59:52.0387 (UTC) FILETIME=[273E9930:01C4123F]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi Peter...a few observations below....
> Busschbach, Peter B (Peter) wrote 24 March 2004 15:01

> Ben,
>=20
> If you read the draft, you will see that at no point it is=20
> suggested that ATM or SONET alarms should be mapped to PW=20
> alarms.
NH=3D> I am being pedantic here, but one does not map 'alarms' between =
layer networks under any situations....even those where the func arch =
requirements of layer networks involved are not violated.  The only OAM =
semantic that should be passed between layer networks is the FDI (the =
purpose being to *suppress alarms*)....and then only in an arch valid =
client/server case, this should not passed *between* layer networks when =
operating in a peer-partition sense.  And to be clear why, I have =
attempted an expanation below:

Peer-partition interworking has very different architectural =
requirements to client/server interworking.

The only pair of technologies that have tried peer-partition =
interworking to date are FR and ATM (see FRF.8 for example). Several =
points are of immediate note:

- The basic premise here (for both FR and ATM) is that we are selling =
the technology as the service.....which is not really where we operators =
want to be in the future (as this leads to the 'technology=3Dservice' =
stovepipe problem and proliferates the interworking problem).

- It largely ignores the 'common thing' that goes end-end between =
end-systems, ie what is the common interworking entity that is =
transparently handed from one network partition to the next?  This is =
the really critical thing to get right up-front if possible.

- It assumes there is a correlation of the behaviour, functions and =
features in each of the peer network partitions.

Let us deal with the last point above first, as this most easily shows =
why a FRF.8-like mind-set for peer-partition interworking is wrong in =
general.

Firstly, there may be a subconscious acceptance that each partition =
belongs to the same mode.....and in the case of FR and ATM then both =
belong to the co-ps mode.  But what happens when we want to interwork =
MPLS(co-ps)/ethernet(cl-ps)/SDH(co-cs) as peer-partitions?

This makes no sense in a FRF.8-type of context.  Perhaps the most =
obvious reason it makes no sense is that the functions and features of =
the each of the different mode/technologies don't have any common =
meaning.  For example ethernet as-is has no signalling, but MPLS and SDH =
might have.  Further, the defects that affect different =
modes/technologies are usually different, and thus have different OAM =
functions.  Further still, there is a 'priority' feature in ATM and FR =
(ie CLP and DE flags) but this does not exist in SDH say.  Similarly we =
find congestion indicators in ATM (EFCI) that are different in FR (FECN =
and BECN) and these don't even exist in MPLS or ethernet......and =
clearly this would have no valid interpretation in SDH anyway.  Finally, =
note that all technologies that belong to the co-cs mode do not have any =
traffic/QoS classes but these can exist in the other modes/technologies.

So, as a general architectural goal, it is clear that the peer-partition =
interworking model of FRF.8 is wrong for many reasons.  This has led us =
to formulate the following architectural rules for peer-partition =
interworking of different modes/technologies:

- We should aim to be clear about the 'thing' that is the common client =
to all the (server) layer peer partitions. =20

- We must terminate all the CI (characteristic information, as defined =
in G.805/809) of the data-plane (at least) at the interworking point.

- Defects detected in a given peer-partition should be mapped to the =
appropriate FDI syntax of the 'thing' that is the common client.

There are many reasons why there is no point in trying to map some form =
of defect indication between the server peer partitions.  For example:
(i) the defects in each mode/technolgy can be quite different....so =
there may be no common semantic/syntax for the handling of defect =
indications in each technology partition;
(ii) it creates a 'defect relay-delay' and more chance to get this =
wrong;
(iii) it may create uncertainty of where the defect truly is and this =
may also cause defect handling problems (eg can't have CV and FDI say =
co-existing in a downstream partition that is not where the failure is);
(iv) it creates an N^2/2 mapping problem for all technologies that can =
form peer partition relationships;
(v) when one gets to the last peer partition technology in the sequence =
there is still a need to do something with the FDI indications at that =
point, ie tell the common client, so one might as well have done this at =
the peer partion where the defect originally occurred.

- There might be an opportunity to converge on some control-plane =
functions, eg same signalling......but this will depend of things like =
peer partition domain ownership (ie I-NNI vs E-NNI like issues), the =
commonality of the modes, etc.

=20
> However, there are protocols that don't have the same=20
> in-band OAM mechanisms as ATM and SONET, viz Frame Relay and=20
> Ethernet. In Frame Relay, the way an alarm at one NNI is=20
> conveyed to another NNI is not specified in the standards.
NH=3D> Excellent point.  But that is a failing of the FR layer network =
specifications.  And do not forget FR today can/is carried =
*transparently* on other server layer networks like ATM, PDH and SDH =
today.....the point being that it is the responsibility of the FR layer =
network here to 'look after itself'......so there should be no backwards =
implications on all other possible technologies that *could* be used to =
carry FR.  This is why layer network independence is so important in a =
client/server relationship.  So we should not compromise the =
specification of future generations of layer network technologies due to =
poor specifications of existing layer network technologies.  Sure, we =
can 'bend' the rules a bit, and when we do we should be clear of the =
consequences.....but the above mindset ought to be the goal.

> When a PW is used to connect the two NNIs, it was decided to=20
> use PW Status messages to convey alarms. This is what the=20
> draft describes and this is why the introduction mentions=20
> "vice versa".
NH=3D> This may be a reasonable 'bending of the rules' here.  However, =
as noted, we should be clear that this is an exception to cater for =
migration and network evolution....it is not a correct arch solution.  =
Note - In a client/server case if we can ensure that the stds we produce =
*always* allow for transparent client layer conveyance over some server =
layer then that will be the correct arch default case.  Folks who then =
want to try and compress a client layer can do so providing they =
understand the consequences of doing so......but this behaviour should =
not be forced on others.

regards, Neil
>=20
> Peter
>=20
> > -----Original Message-----
> > From: benjamin.niven-jenkins@bt.com
> > [mailto:benjamin.niven-jenkins@bt.com]
> > Sent: Wednesday, March 24, 2004 9:23 AM
> > To: pwe3@ietf.org
> > Subject: RE: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
> >=20
> >=20
> > Folks,
> >=20
> > draft-nadeau-pwe3-oam-msg-map-04 states in the introduction=20
> > "This document describes ... how faults detected in=20
> > pseudo-wires are mapped to OAM messages native to the=20
> > emulated services and vice versa".
> >=20
> > I can see the need to map OAM up the network stack from the=20
> > server layer OAM (e.g. a MPLS server layer) to the client AC=20
> > OAM (e.g. an ATM client layer) but why is there a need to map=20
> > OAM down the network stack from AC OAM to server layer OAM?
> >=20
> > For example, today there are client/server relationships=20
> > where ATM VPs (the client) are transported over SDH VC_4s=20
> > (the server), defects in the SDH server layer are mapped=20
> > upwards to the ATM client layer.  However defects in the ATM=20
> > client layer are not mapped down to the SDH server layer. =20
> > This is because defects in the client layer do not affect the=20
> > server layer whereas defects in the server layer do affect=20
> > the client layer.
> >=20
> > Thanks
> > Ben
> >=20
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Thu, 25 Mar 2004 10:05:26 -0500
Lines: 29
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Thu Mar 25 16:08:20 2004
Return-path: <pwe3-admin@ietf.org>
To: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>,
        benjamin.niven-jenkins@bt.com, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Thursday, March 25, 2004 3:00 AM
> To: busschbach@lucent.com; benjamin.niven-jenkins@bt.com; 
> pwe3@ietf.org
> Subject: RE: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
> 
> 
> Hi Peter...a few observations below....
> > Busschbach, Peter B (Peter) wrote 24 March 2004 15:01
> 
> > Ben,
> > 
> > If you read the draft, you will see that at no point it is 
> > suggested that ATM or SONET alarms should be mapped to PW 
> > alarms.
> NH=> I am being pedantic here, but one does not map 'alarms' 
> between layer networks under any situations....even those 
> where the func arch requirements of layer networks involved 
> are not violated.  The only OAM semantic that should be 
> passed between layer networks is the FDI 


Forgive me for being an unworthy ignoramus, but I thought that "alarm" and "defect indication" were synonomous. I must have missed the G.XXX spec that explains the exact definition of these terms and that - apparently - also states that those who are initiated in the wisdom of G.XXX should mercilessly crank down on any misuse of sacred terminology without showing willingness to focus on the spirit of someone's comments rather than the letter.


> [snipped to the end] 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: richard.spencer@bt.com
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 14:45:07 -0000
Lines: 9
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64
Cc: <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <benjamin.niven-jenkins@bt.com>, <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 16:49:11 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3LvgAKDCggAAsWmkAAAOOe6g==
To: <mmorrow@cisco.com>, <neil.2.harrison@bt.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 14:45:08.0533 (UTC) FILETIME=[CAE20650:01C3FF9B]
Content-Transfer-Encoding: base64
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

PiBJIGhhdmUgbm90IHNlZW4geW91ciBjb250cmlidXRpb24vZHJhZnQgcHJvcG9zYWwgaW4gdGhl
IElFVEYgeWV0DQo+IChob3BlZnVsbHkgdGhpcyBpcyBmb3J0aGNvbWluZykuDQoNClBsZWFzZSBj
YW4geW91IGV4cGxhaW4gd2h5IHlvdSBzZWUgdGhlIG5lZWQgZm9yIGEgY29udHJpYnV0aW9uL2Ry
YWZ0IHRvIGJlIHN1Ym1pdHRlZCB0byB0aGUgSUVURj8gWS4xNzExIGhhcyBiZWVuIGNsZWFybHkg
ZGVmaW5lZCBhbmQgc3RhbmRhcmRpc2VkIGJ5IHRoZSBJVFUuIElmIHlvdSBhcmUgYXNzZXJ0aW5n
IHRoYXQgc3RhbmRhcmRzIGFyZSBvbmx5IHZhbGlkIGlmIHRoZXkgaGF2ZSBiZWVuIHN1Ym1pdHRl
ZCB0byB0aGUgSUVURiwgYXJlIHlvdSBhbHNvIGV4cGVjdGluZyBjb250cmlidXRpb25zL2RyYWZ0
cyB0byBiZSBzdWJtaXR0ZWQgdG8gdGhlIElFVEYgZXhwbGFpbmluZyBob3cgQVRNLCBGUiwgVERN
LCBldGMuIHdvcms/DQogDQpSZWdhcmRzLA0KUmljaGFyZA0K


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Thu, 25 Mar 2004 10:28:22 -0500
Organization: Cisco Systems
Lines: 34
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF3453@i2km07-ukbr.domain1.systemhost.net>
Reply-To: <tnadeau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Thu Mar 25 16:44:36 2004
Return-path: <pwe3-admin@ietf.org>
To: <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-reply-to: <0536FC9B908BEC4597EE721BE6A3538904EF3453@i2km07-ukbr.domain1.systemhost.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


	One question inside. Forgive me for pruning out
most of your lengthy reply.

-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
neil.2.harrison@bt.com
Sent: Thursday, March 25, 2004 3:00 AM
To: busschbach@lucent.com; benjamin.niven-jenkins@bt.com; pwe3@ietf.org
Subject: RE: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt


Hi Peter...a few observations below....
> Busschbach, Peter B (Peter) wrote 24 March 2004 15:01

> Ben,
> 
> If you read the draft, you will see that at no point it is 
> suggested that ATM or SONET alarms should be mapped to PW 
> alarms.
NH=> I am being pedantic here, but one does not map 'alarms' between
layer networks under any situations....even those where the func arch
requirements of layer networks involved are not violated.  The only OAM
semantic that should be passed between layer networks is the FDI (the
purpose being to *suppress alarms*)....and then only in an arch valid
client/server case, this should not passed *between* layer networks when
operating in a peer-partition sense.  And to be clear why, I have
attempted an expanation below:

	Why should one "not map 'alarms' between layer networks"? It 
seems to me that this is done in a variety of contexts today. Can 
you justify why this is not a good idea. 

	--Tom


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Thu, 25 Mar 2004 17:54:17 -0000
Lines: 50
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Thu Mar 25 18:58:41 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt
Thread-Index: AcQSgJmV4suLtbORTlO3Ou4Ts9b6vgADgkgg
To: <tnadeau@cisco.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 25 Mar 2004 17:54:17.0742 (UTC) FILETIME=[3173E2E0:01C41292]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Tom...
> >=20
> > If you read the draft, you will see that at no point it is=20
> > suggested that ATM or SONET alarms should be mapped to PW=20
> > alarms.
> NH=3D> I am being pedantic here, but one does not map 'alarms' between
> layer networks under any situations....even those where the func arch
> requirements of layer networks involved are not violated. =20
> The only OAM
> semantic that should be passed between layer networks is the FDI (the
> purpose being to *suppress alarms*)....and then only in an arch valid
> client/server case, this should not passed *between* layer=20
> networks when
> operating in a peer-partition sense.  And to be clear why, I have
> attempted an expanation below:
>=20
> 	Why should one "not map 'alarms' between layer networks"? It=20
> seems to me that this is done in a variety of contexts today. Can=20
> you justify why this is not a good idea.=20
>=20
NH=3D> I will assume we are discussing the client/server case.  The part =
of the mail that was snipped explained why defect mapping indications in =
the peer-partition case was not generally a good idea.

An alarm should be strive to be singular in nature.  It should be raised =
by the 1st equipment downstream of the defect that is able to detect it. =
 This gives a localised indication of the where the problem is.  All =
client layers (see note) should be informed of the lower layer defect by =
sending them a FDI (and this ought to be done in the =
data-plane....depends on how well-specified the client layer is =
however).  The defect detected in the server layer, at its trail =
termination point, is the also the point associated with the alarm.  =
Above the server layer trail termination point there is a server->client =
adaptation function.....this is where the FDI (in terms of the client =
layer FDI syntax) is injected.

If you don't do something like this there could be a huge number of =
uncorrelated alarms raised at the trail termination points of the =
affected clients.  These may be in other operators networks, and maybe =
in other countries.

Note - This is only strictly true for the co-cs and co-ps =
clients....though some folks who working on ethernet (cl-ps) =
fault-management may disagree with this, as they are considering =
introducing a 'fixed' topology overlay of OAM insertion/extraction =
points. In a sense these can be considered to be a co-ps overlay.

Hope that helps explain what I meant by not 'mapping alarms'.

regards, Neil


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Thu, 25 Mar 2004 13:16:22 -0500
Organization: Cisco Systems
Lines: 67
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF3459@i2km07-ukbr.domain1.systemhost.net>
Reply-To: <tnadeau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Thu Mar 25 19:22:03 2004
Return-path: <pwe3-admin@ietf.org>
To: <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-reply-to: <0536FC9B908BEC4597EE721BE6A3538904EF3459@i2km07-ukbr.domain1.systemhost.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
neil.2.harrison@bt.com
Sent: Thursday, March 25, 2004 12:54 PM
To: tnadeau@cisco.com; pwe3@ietf.org
Subject: RE: [PWE3] draft-nadeau-pwe3-oam-msg-map-04.txt


Tom...
> > 
> > If you read the draft, you will see that at no point it is 
> > suggested that ATM or SONET alarms should be mapped to PW 
> > alarms.
> NH=> I am being pedantic here, but one does not map 'alarms' between
> layer networks under any situations....even those where the func arch
> requirements of layer networks involved are not violated.  
> The only OAM
> semantic that should be passed between layer networks is the FDI (the
> purpose being to *suppress alarms*)....and then only in an arch valid
> client/server case, this should not passed *between* layer 
> networks when
> operating in a peer-partition sense.  And to be clear why, I have
> attempted an expanation below:
> 
> 	Why should one "not map 'alarms' between layer networks"? It 
> seems to me that this is done in a variety of contexts today. Can 
> you justify why this is not a good idea. 
> 
NH=> I will assume we are discussing the client/server case.  The part
of the mail that was snipped explained why defect mapping indications in
the peer-partition case was not generally a good idea.

An alarm should be strive to be singular in nature.  It should be raised
by the 1st equipment downstream of the defect that is able to detect it.
This gives a localised indication of the where the problem is.  All
client layers (see note) should be informed of the lower layer defect by
sending them a FDI (and this ought to be done in the
data-plane....depends on how well-specified the client layer is
however).  The defect detected in the server layer, at its trail
termination point, is the also the point associated with the alarm.
Above the server layer trail termination point there is a server->client
adaptation function.....this is where the FDI (in terms of the client
layer FDI syntax) is injected.

If you don't do something like this there could be a huge number of
uncorrelated alarms raised at the trail termination points of the
affected clients.  These may be in other operators networks, and maybe
in other countries.

Note - This is only strictly true for the co-cs and co-ps
clients....though some folks who working on ethernet (cl-ps)
fault-management may disagree with this, as they are considering
introducing a 'fixed' topology overlay of OAM insertion/extraction
points. In a sense these can be considered to be a co-ps overlay.

Hope that helps explain what I meant by not 'mapping alarms'.

	Then I don't see why you think that what Peter was describing
is not what you describe above.  The msg mapping draft does describe
how to a) "gives a localised indication of the where the problem 
is.", and b) "Above the server layer trail termination point there 
is a server->client adaptation function.....this is where the FDI 
(in terms of the client layer FDI syntax) is injected." 

	--Tom


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-hdlc-ppp-encap-mpls-01.txt
Date: Thu, 25 Mar 2004 15:38:59 -0500
Lines: 82
Sender: pwe3-admin@ietf.org
Reply-To: Internet-Drafts@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Thu Mar 25 21:40:12 2004
Return-path: <pwe3-admin@ietf.org>
To: IETF-Announce: ;
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--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		: Encapsulation Methods for Transport of PPP/HDLC Frames Over IP and MPLS Networks
	Author(s)	: L. Martini, et al.
	Filename	: draft-ietf-pwe3-hdlc-ppp-encap-mpls-01.txt
	Pages		: 10
	Date		: 2004-3-25
	
A Pseudowire (PW) can be used to carry PPP, or HDLC Protocol Data
Units over an IP or MPLS network without terminating the PPP/HDLC
protocol. This enables service providers to offer 'emulated' HDLC, or
PPP link services over existing IP or MPLS networks. This document
specifies the encapsulation of PPP/HDLC PDUs within a pseudowire.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-hdlc-ppp-encap-mpls-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-hdlc-ppp-encap-mpls-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"

Content-Type: text/plain
Content-ID:	<2004-3-25154713.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-hdlc-ppp-encap-mpls-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-hdlc-ppp-encap-mpls-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-25154713.I-D@ietf.org>

--OtherAccess--

--NextPart--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-iana-allocation-03.txt
Date: Thu, 25 Mar 2004 15:39:07 -0500
Lines: 82
Sender: pwe3-admin@ietf.org
Reply-To: Internet-Drafts@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Thu Mar 25 21:40:16 2004
Return-path: <pwe3-admin@ietf.org>
To: IETF-Announce: ;
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--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		: IANA Allocations for pseudo Wire Edge to Edge Emulation (PWE3)
	Author(s)	: L. Martini, M. Townsley
	Filename	: draft-ietf-pwe3-iana-allocation-03.txt
	Pages		: 5
	Date		: 2004-3-25
	
The Control and maintenance protocol for providing various Layer 1
and Layer 2 services over a Packet Switched Network has been
described in [2]. This document pre-allocates the fixed Pseudo-wire
identifier , and other fixed protocol values that are to be assigned
by IANA using the 'IETF Consensus' policy defined in RFC2434

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-iana-allocation-03.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-iana-allocation-03.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"

Content-Type: text/plain
Content-ID:	<2004-3-25154724.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-iana-allocation-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-iana-allocation-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-25154724.I-D@ietf.org>

--OtherAccess--

--NextPart--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-control-protocol-06.txt
Date: Thu, 25 Mar 2004 15:39:13 -0500
Lines: 85
Sender: pwe3-admin@ietf.org
Reply-To: Internet-Drafts@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Thu Mar 25 21:40:22 2004
Return-path: <pwe3-admin@ietf.org>
To: IETF-Announce: ;
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--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		: Pseudowire Setup and Maintenance using LDP
	Author(s)	: L. Martini, et al. 
	Filename	: draft-ietf-pwe3-control-protocol-06.txt
	Pages		: 31
	Date		: 2004-3-25
	
Layer 2 services (such as Frame Relay, ATM, ethernet) can be
'emulated' over an IP and/or MPLS backbone by encapsulating the layer
2 PDUs and then transmitting them over 'pseudowires'.  It is also
possible to use pseudowires to provide SONET circuit emulation over
an IP and/or MPLS network. This document specifies a protocol for
establishing and maintaining the pseudowires, using extensions to
LDP.  Procedures for encapsulating layer 2 PDUs are specified in a
set of companion documents.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-control-protocol-06.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-control-protocol-06.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"

Content-Type: text/plain
Content-ID:	<2004-3-25154736.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-control-protocol-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-control-protocol-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-25154736.I-D@ietf.org>

--OtherAccess--

--NextPart--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-arch-07.txt
Date: Thu, 25 Mar 2004 15:39:19 -0500
Lines: 83
Sender: pwe3-admin@ietf.org
Reply-To: Internet-Drafts@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Thu Mar 25 21:40:22 2004
Return-path: <pwe3-admin@ietf.org>
To: IETF-Announce: ;
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--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 Architecture
	Author(s)	: S. Bryant, P. Pate
	Filename	: draft-ietf-pwe3-arch-07.txt
	Pages		: 44
	Date		: 2004-3-25
	
This document describes an architecture for Pseudo Wire Emulation
Edge-to-Edge (PWE3).  It discusses the emulation of services (such as
Frame Relay, ATM, Ethernet TDM and SONET/SDH) over packet switched
networks (PSNs) using IP or MPLS.  It presents the architectural
framework for pseudo wires (PWs), defines terminology, specifies the
various protocol elements and their functions.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-arch-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-arch-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

Content-Type: text/plain
Content-ID:	<2004-3-25154747.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-arch-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-arch-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-25154747.I-D@ietf.org>

--OtherAccess--

--NextPart--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: PW Availability
Date: Thu, 25 Mar 2004 15:49:17 -0500
Lines: 171
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-From: pwe3-admin@ietf.org Thu Mar 25 21:55:15 2004
Return-path: <pwe3-admin@ietf.org>
To: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>, pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Neil,

I would be happy to add to draft-nadeau-pwe3-oam-msg-map-04.txt that a PW is declared unavailable if a defect persists for more than 10 seconds. However, at this point I am not sure what that means since I don't know how it affects anything that goes on in the network.

You have mentioned that it is important to recognize such a state, because it determines when Performance Monitoring should be started and stopped. However, from your response to my last email, it appears that a clear and realistic approach to Performance Monitoring does not exist yet. Therefore, I wonder what the point is of introducing concepts that may or may not be relevant in the future.

Therefore, I propose that we add the following statements to draft-nadeau-pwe3-oam-msg-map-04.txt:

a) in general (i.e. for other technologies), operators consider a connection unavailable of a defect persists for more than 10 seconds

b) the interaction between PW fault management and Performance Monitoring is for further study.

Further comments in-line.

Peter

> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Wednesday, March 24, 2004 5:53 PM
> To: busschbach@lucent.com; pwe3@ietf.org
> Subject: RE: PW Availability
> 
> 
> Peter..
> > 
> > Neil,
> > 
> > A while ago we exchanged emails on the availability of Pseudo 
> > Wires. The relevant part is attached to this email.
> > 
> > I agree with the observations you made, but my main question 
> > was not answered: if you emulate a service over PWs,
> NH=> Can you define precisely what 'emulate' means here?
> 

I meant "emulate" in the same way as it is used in all WG drafts and emails on this mailing list: the encapsulation of client traffic so as to transport it over a PSN.

> > is it 
> > really necessary to measure Network Performance (NP) of the 
> > PW itself?
> NH=> Pass.  Depends on what the definition of 'emulation' 
> really meens (and I have no idea) and what a PW actually 
> is....to me its some form of adaptation.  XoverIP could have 
> different perf to XoverMPLS....the defect behaviour is for 
> sure very different.  I think folks really ought to 
> differentiate these 2 cases as they are obviously not the same.

I may be naive, but I would think that Network Performance to the extend that it relates to SLAs should be independent of the network layers over which the service is carried.

In fact, you assertion that defect behavior of IP and MPLS networks is so different that XoverIP and XoverMPLS should be considered as two totally different solutions suggests that NP measurements of X would yield completely different results in the two cases. I can't see why that would be desirable to Service Providers.
 
> 
> > If a Service Provider measures NP on end-to-end 
> > ATM VCs, why is it necessary to obtain additional NP 
> > measurements on one specific segment?
> NH=> To see where impairments are coming from say.  In a more 
> general case if you have some global reference connection 
> with metrics A, B, C that have objectives a, b, c (to be met 
> over some period, eg month), you need some way to fairly 
> apportion these to  partitions of the end-end path, eg to 
> countries or operator domains.  So each partition need to 
> check its bit is within its apportioned target.
> > 
> > Now, assuming that a Service Provider wants to measure NP of 
> > PWs, how does that work?
> NH=> I have no idea....you are starting down the very 
> slippery slope of making a PW a networked entity....and it is 
> not (as yet anyway).

I am  not sure who started down the slippery slope. I did not say there was a need for an availability state for PWs. You did. I am actually arguing for the position that it doesn't make sense to measure NP for Pseudo Wires.


> 
> > I assume that it is based on 
> > comparing packet counts both at ingress and egress. Following 
> > the method proposed by Y.1711, performance measurements are 
> > stopped upon detection of a defect and restarted a certain 
> > period after the defects disappears and the connection is 
> > stable again. However, in general a defect exists some time 
> > before a connection end-point finds out. Therefore, a number 
> > of packets will have been dropped already. Rather than trying 
> > to minimize the effect of this time lag by specifying 
> > available/unavailable state, as Y.1711 does, would it not 
> > make more sense to sanitize the data in an off-line 
> > performance monitoring tool that can exclude counts taken 
> > just before the defect occurred?
> NH=> Y.1711 has not defined any NP collection yet.  Its more 
> important to get the basic defects, short-breaks and 
> unavailability bits done 1st.  NP stuff can be added later on 
> this firm defect detection/handling basis.  I can think of 
> some smart/simple ways of doing NP collection however.....the 
> details are not given in Y.1711 right now. One also has to be 
> aware of 'PDUs in flight'.  
> > 
> > In short: how exactly do Service Prodivers measure Network 
> > Performance?
> NH=> Badly to date is my view.  Why?  Because the ordering I 
> mentioned in the mail below has never properly been executed 
> in the past.

I am not sure what point you are trying to make. Service Providers (BT being one of them) have large networks in which they run ATM over SDH or SONET. I was not asking a rhetorical question. I am genuinely interested to learn more about operator experiences.

However, if you say that even ATM-over-SDH is such a mess that decent Performance Monitoring is not possible, then what does that mean for our current work? Existing networks will not go away for a long time to come. We have to work with what we have. Especially with regards to PWE, I don't see how we can work on Performance Monitoring without taking existing protocols and techniques into account.



> > 
> > Peter
> > 
> > > -----Original Message-----
> > > From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> > > Sent: Monday, March 01, 2004 3:57 PM
> > 
> > > > > 2	There is no demarcation between the available state and 
> > > > > unavailable state for network trail entities.  This means 
> > > > > there is no temporal basis for the specification of an 
> > > > > availability SLA or a network performance SLA, noting that 
> > > > > the latter is only relevant to the available state.  These 
> > > > > impact network element specifications and thus have 
> > > > > consequential impact on NMS/OSS.  NE and NMS/OSS 
> > > > > considerations are important for an operator to see correctly 
> > > > > executed.  CF Y.1711 where the unavailable state is specified 
> > > > > (as a consequential persistence of defects).
> > > > > 
> > > > 
> > > > Adding a definition of availabillity would be pretty easy to 
> > > > specify and implement. I would like to understand better, 
> > > > though, how this would be used in practice. It seems to me 
> > > > that SLAs apply to the services carried over PWs, not to the 
> > > > PWs themselves.
> > > NH=> Several points here.
> > > 
> > > First, there is a difference between QoS and Network 
> > > Performance (NP) metrics/objectives.  The former are what a 
> > > specific application percieves, whereas the latter are 
> > > application invariant (ie for a given level of NP impairment 
> > > different applications can have quite a different perspective 
> > > on QoS).  NP metrics are really what the network elements 
> > > should capture and SLAs specify.
> > > 
> > > Second, the control of availability and NP are complementary 
> > > performance requirements.  If one does not have an agreed 
> > > datum at which NP metrics should no longer be counted then 
> > > one can easily distort the NP SLA.  There is also the 
> > > requirement to measure the same 'apples and apples' here in 
> > > different networks/equipment.....and this also applies 
> > > *across* nested layer networks (the commonly agreed 
> > > integration period for assessing availability is based on 10s 
> > > of outage). Further, a service which has a 99% unavailability 
> > > can still have perfect NP......this is why these metrics are 
> > > complimentary.  See section 7 of Y.1711 for more info.
> > > 
> > > Third, there is a key ordering behaviour here:
> > > => ensure the right net arch for mode considered 1st
> > > => this allows the relevant defects to be identified
> > > => this allows appropriate OAM to be specified (and from this 
> > > defect entry/exit criteria and consequent actions)
> > > => this allows unavalability entry/exit criteria to be 
> > > specified based on defect persistence
> > > => this allows the up-time to be specified over which NP 
> is relevent
> > > You can very easily make life more complex than it need be by 
> > > not following this ordering.  Further, and for complexity 
> > > reasons, I would also not advise using NP metrics within the 
> > > availability entry/exit criteria.....just use defect 
> > > persistency.  Much careful thought went into Y.1711 on these, 
> > > and several other, matters that may not be readily apparent 
> > > to someone on a cursory reading.
> > > > 
> > 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: RE: PW Availability
Date: Fri, 26 Mar 2004 10:28:02 +0000
Organization: Cisco Systems, Inc.
Lines: 200
Sender: pwe3-admin@ietf.org
References: <B99995113B318D44BBE87DC50092EDA90C0D595F@nj7460exch006u.ho.lucent.com>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>, pwe3@ietf.org
X-From: pwe3-admin@ietf.org Fri Mar 26 11:31:10 2004
Return-path: <pwe3-admin@ietf.org>
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: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>
In-Reply-To: <B99995113B318D44BBE87DC50092EDA90C0D595F@nj7460exch006u.ho.lucent.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I am surprised that such a relatively large fixed number is specified.

What is the rational for 10s?

- Stewart

Busschbach, Peter B (Peter) wrote:

> Neil,
> 
> I would be happy to add to draft-nadeau-pwe3-oam-msg-map-04.txt that a PW is declared unavailable if a defect persists for more than 10 seconds. However, at this point I am not sure what that means since I don't know how it affects anything that goes on in the network.
> 
> You have mentioned that it is important to recognize such a state, because it determines when Performance Monitoring should be started and stopped. However, from your response to my last email, it appears that a clear and realistic approach to Performance Monitoring does not exist yet. Therefore, I wonder what the point is of introducing concepts that may or may not be relevant in the future.
> 
> Therefore, I propose that we add the following statements to draft-nadeau-pwe3-oam-msg-map-04.txt:
> 
> a) in general (i.e. for other technologies), operators consider a connection unavailable of a defect persists for more than 10 seconds
> 
> b) the interaction between PW fault management and Performance Monitoring is for further study.
> 
> Further comments in-line.
> 
> Peter
> 
> 
>>-----Original Message-----
>>From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
>>Sent: Wednesday, March 24, 2004 5:53 PM
>>To: busschbach@lucent.com; pwe3@ietf.org
>>Subject: RE: PW Availability
>>
>>
>>Peter..
>>
>>>Neil,
>>>
>>>A while ago we exchanged emails on the availability of Pseudo 
>>>Wires. The relevant part is attached to this email.
>>>
>>>I agree with the observations you made, but my main question 
>>>was not answered: if you emulate a service over PWs,
>>
>>NH=> Can you define precisely what 'emulate' means here?
>>
> 
> 
> I meant "emulate" in the same way as it is used in all WG drafts and emails on this mailing list: the encapsulation of client traffic so as to transport it over a PSN.
> 
> 
>>>is it 
>>>really necessary to measure Network Performance (NP) of the 
>>>PW itself?
>>
>>NH=> Pass.  Depends on what the definition of 'emulation' 
>>really meens (and I have no idea) and what a PW actually 
>>is....to me its some form of adaptation.  XoverIP could have 
>>different perf to XoverMPLS....the defect behaviour is for 
>>sure very different.  I think folks really ought to 
>>differentiate these 2 cases as they are obviously not the same.
> 
> 
> I may be naive, but I would think that Network Performance to the extend that it relates to SLAs should be independent of the network layers over which the service is carried.
> 
> In fact, you assertion that defect behavior of IP and MPLS networks is so different that XoverIP and XoverMPLS should be considered as two totally different solutions suggests that NP measurements of X would yield completely different results in the two cases. I can't see why that would be desirable to Service Providers.
>  
> 
>>>If a Service Provider measures NP on end-to-end 
>>>ATM VCs, why is it necessary to obtain additional NP 
>>>measurements on one specific segment?
>>
>>NH=> To see where impairments are coming from say.  In a more 
>>general case if you have some global reference connection 
>>with metrics A, B, C that have objectives a, b, c (to be met 
>>over some period, eg month), you need some way to fairly 
>>apportion these to  partitions of the end-end path, eg to 
>>countries or operator domains.  So each partition need to 
>>check its bit is within its apportioned target.
>>
>>>Now, assuming that a Service Provider wants to measure NP of 
>>>PWs, how does that work?
>>
>>NH=> I have no idea....you are starting down the very 
>>slippery slope of making a PW a networked entity....and it is 
>>not (as yet anyway).
> 
> 
> I am  not sure who started down the slippery slope. I did not say there was a need for an availability state for PWs. You did. I am actually arguing for the position that it doesn't make sense to measure NP for Pseudo Wires.
> 
> 
> 
>>>I assume that it is based on 
>>>comparing packet counts both at ingress and egress. Following 
>>>the method proposed by Y.1711, performance measurements are 
>>>stopped upon detection of a defect and restarted a certain 
>>>period after the defects disappears and the connection is 
>>>stable again. However, in general a defect exists some time 
>>>before a connection end-point finds out. Therefore, a number 
>>>of packets will have been dropped already. Rather than trying 
>>>to minimize the effect of this time lag by specifying 
>>>available/unavailable state, as Y.1711 does, would it not 
>>>make more sense to sanitize the data in an off-line 
>>>performance monitoring tool that can exclude counts taken 
>>>just before the defect occurred?
>>
>>NH=> Y.1711 has not defined any NP collection yet.  Its more 
>>important to get the basic defects, short-breaks and 
>>unavailability bits done 1st.  NP stuff can be added later on 
>>this firm defect detection/handling basis.  I can think of 
>>some smart/simple ways of doing NP collection however.....the 
>>details are not given in Y.1711 right now. One also has to be 
>>aware of 'PDUs in flight'.  
>>
>>>In short: how exactly do Service Prodivers measure Network 
>>>Performance?
>>
>>NH=> Badly to date is my view.  Why?  Because the ordering I 
>>mentioned in the mail below has never properly been executed 
>>in the past.
> 
> 
> I am not sure what point you are trying to make. Service Providers (BT being one of them) have large networks in which they run ATM over SDH or SONET. I was not asking a rhetorical question. I am genuinely interested to learn more about operator experiences.
> 
> However, if you say that even ATM-over-SDH is such a mess that decent Performance Monitoring is not possible, then what does that mean for our current work? Existing networks will not go away for a long time to come. We have to work with what we have. Especially with regards to PWE, I don't see how we can work on Performance Monitoring without taking existing protocols and techniques into account.
> 
> 
> 
> 
>>>Peter
>>>
>>>
>>>>-----Original Message-----
>>>>From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
>>>>Sent: Monday, March 01, 2004 3:57 PM
>>>
>>>>>>2	There is no demarcation between the available state and 
>>>>>>unavailable state for network trail entities.  This means 
>>>>>>there is no temporal basis for the specification of an 
>>>>>>availability SLA or a network performance SLA, noting that 
>>>>>>the latter is only relevant to the available state.  These 
>>>>>>impact network element specifications and thus have 
>>>>>>consequential impact on NMS/OSS.  NE and NMS/OSS 
>>>>>>considerations are important for an operator to see correctly 
>>>>>>executed.  CF Y.1711 where the unavailable state is specified 
>>>>>>(as a consequential persistence of defects).
>>>>>>
>>>>>
>>>>>Adding a definition of availabillity would be pretty easy to 
>>>>>specify and implement. I would like to understand better, 
>>>>>though, how this would be used in practice. It seems to me 
>>>>>that SLAs apply to the services carried over PWs, not to the 
>>>>>PWs themselves.
>>>>
>>>>NH=> Several points here.
>>>>
>>>>First, there is a difference between QoS and Network 
>>>>Performance (NP) metrics/objectives.  The former are what a 
>>>>specific application percieves, whereas the latter are 
>>>>application invariant (ie for a given level of NP impairment 
>>>>different applications can have quite a different perspective 
>>>>on QoS).  NP metrics are really what the network elements 
>>>>should capture and SLAs specify.
>>>>
>>>>Second, the control of availability and NP are complementary 
>>>>performance requirements.  If one does not have an agreed 
>>>>datum at which NP metrics should no longer be counted then 
>>>>one can easily distort the NP SLA.  There is also the 
>>>>requirement to measure the same 'apples and apples' here in 
>>>>different networks/equipment.....and this also applies 
>>>>*across* nested layer networks (the commonly agreed 
>>>>integration period for assessing availability is based on 10s 
>>>>of outage). Further, a service which has a 99% unavailability 
>>>>can still have perfect NP......this is why these metrics are 
>>>>complimentary.  See section 7 of Y.1711 for more info.
>>>>
>>>>Third, there is a key ordering behaviour here:
>>>>=> ensure the right net arch for mode considered 1st
>>>>=> this allows the relevant defects to be identified
>>>>=> this allows appropriate OAM to be specified (and from this 
>>>>defect entry/exit criteria and consequent actions)
>>>>=> this allows unavalability entry/exit criteria to be 
>>>>specified based on defect persistence
>>>>=> this allows the up-time to be specified over which NP 
>>
>>is relevent
>>
>>>>You can very easily make life more complex than it need be by 
>>>>not following this ordering.  Further, and for complexity 
>>>>reasons, I would also not advise using NP metrics within the 
>>>>availability entry/exit criteria.....just use defect 
>>>>persistency.  Much careful thought went into Y.1711 on these, 
>>>>and several other, matters that may not be readily apparent 
>>>>to someone on a cursory reading.
>>>>
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: RE: PW Availability
Date: Fri, 26 Mar 2004 10:56:28 -0000
Lines: 47
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <busschbach@lucent.com>, <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Fri Mar 26 12:00:03 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] RE: PW Availability
Thread-Index: AcQTHQk6rwEcrC+4RnqgJz4rqa/GygAAJrIA
To: <stbryant@cisco.com>
X-OriginalArrivalTime: 26 Mar 2004 10:56:38.0564 (UTC) FILETIME=[036E8640:01C41321]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

<snipped>
>=20
> I am surprised that such a relatively large fixed number is specified.
>=20
> What is the rational for 10s?
>=20
> - Stewart

Hi Stewart,

This is what folks use to define availability in most telecoms networks =
and it is in common usage.  The value is historical (I can explain its =
roots if you are really intersted). You need some value specifying, and =
this is probably as good as any other for the purpose it serves......but =
it is not the full story of course. If you don't have an agreed =
definition of availability you cannot compare apples with apples. This =
affects at least 2 dimensions:
-	in a horizontally partitioned layer network, ie spanning several =
operators domains......this also leads into partitioned performance =
allocations within (longer) reference connections
-	in a vertically nested set of layer networks, ie one wants some form =
on uniformity of performance specification across each layer network

Further, there is an ordering here.  PM measurements need to know the =
state of the network.  PMs measurements are only associated with the =
available state for SLA purposes....so clearly we need a common basis =
for PM measureements, and this is dependent on a common basis for =
availabilty.  Unavailability is a function of defect persistence.  So =
one also needs a commonly agreed specification of defects (these are of =
course different for each mode).  And finally, though most importantly, =
to define the defects one needs to respect the func arch requirements of =
the mode considered......break that and you will have major problems =
doing the rest that is dependent on this anyway (as we know only too =
well).

Please have a read through Y.1711.....its all done in there (and =
more....check out the stuff on short-breaks for example).

Note - You could propose changing the definition of availability.....but =
we would still need some commonly agreed definition.   But I suspect you =
may get some kick-back from folks who want to retain the classical =
definition.  And to be honest I can't actually see changing it is really =
going to provide that much benefit....respecting the arch of the mode =
and having sound defect detection/handling is far more important IMO =
speaking as an operator.

regards, Neil


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Kenji Kumaki <ke-kumaki@kddi.com>
Subject: Re: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Tue, 02 Mar 2004 00:13:38 +0900
Lines: 30
Sender: pwe3-admin@ietf.org
References: <3C775706078CA347A8653E03E14691060318CFF0@xbe-ams-313.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 01 17:06:36 2004
Return-path: <pwe3-admin@ietf.org>
To: <pwe3@ietf.org>
In-Reply-To: <3C775706078CA347A8653E03E14691060318CFF0@xbe-ams-313.cisco.com>
X-Mailer: Becky! ver. 2.05.08
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi all,

This draft is useful OAM from the point of SP's view.
I would like to support this one as a WG doc.

Regards,
Kenji

On Mon, 1 Mar 2004 04:59:53 +0100
"Monique Morrow (mmorrow)" <mmorrow@cisco.com> wrote:

> Folks,
>  
> I presented OAM Msg Mapping status today in Seoul,
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
> with a proposal to progress the draft as a Working Group item  
>  
> Whilst we had no opposition the room, I would like to ensure that there
> is consensus on the list to progress the draft as a WG item.
>  
> Essentially, the draft has been revised to reflect like-to-like
> constructs as per the scope of PWE3 and, covers fault detection and
> alarm message mapping as two separate elements.
>  
> /Monique
>  
>  

-- 
Kenji Kumaki <ke-kumaki@kddi.com>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: RE: PW Availability
Date: Fri, 26 Mar 2004 14:34:46 -0000
Lines: 275
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <busschbach@lucent.com>, <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Fri Mar 26 15:38:10 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] RE: PW Availability
Thread-Index: AcQTHQk6rwEcrC+4RnqgJz4rqa/GygAAJrIAAAMd38A=
To: <stbryant@cisco.com>
X-OriginalArrivalTime: 26 Mar 2004 14:34:48.0864 (UTC) FILETIME=[7DDBCA00:01C4133F]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

As a postscript to this, I have had some private mail requests to give =
further insight on 2 things:
-	the origins of 10s availability value
-	the origins of 50ms prot-sw value

10s availability:

This goes way back to the days when the 64k N-ISDN was being specified =
(ie early/mid 80s), and folks were just starting to introduce digital Tx =
and Sw systems.  I was a new graduate then...so its a while ago ;-)

Folks knew that they had to define 2 types of performance =
specifications. One type would control how much downtime a network path =
could exhibit and the other type would control the transfer impairments =
when the path was 'up'.

The dominant application at the time was telephony.  So 10s came from a =
guess at an upper bound on how long it would be before folks would have =
cleared down the call.  IMO, I suspect few folks would clear a call =
until maybe 4+ seconds had passed....but 10s is a bit long.  There were =
also factors on how fast folks could effect restoration schemes then.  =
Whether this figure is right/wrong is of course debateable.....and it =
has indeed been discussed many times since with a view to change it, but =
it still remains.  If you reduce it you are making things more stringent =
for operators to meet.....many may not like this.  It also won't =
harmonise with existing networks/practices.  So, for the purpose it =
serves I think it is fine, and I see no compelling reason for wanting to =
change it now.

Now here's some stuff related to availability that you may not know =
about......those who are not interested in this should skip the text =
delimited by =3D=3D=3D=3D> and return (if they want) to where I discuss =
the 50ms issue.

=3D=3D=3D=3D=3D>

The error performance metrics for the up-state were defined in Rec G.821 =
(this also had the availability definition in too).  There were =
originally 3 parameters:
-	the ES (Errored Second), ie 1s period with >=3D1 bit errors
-	the SES (Severely Errored Second), ie 1s period with an error density =
>=3D 10^-3
-	the DM (Degraded Minute), ie 1min period with an error density =
>=3D10^-6 *after* removing SES

Folks thought these were sensible for the services envisaged at the =
time.  IMO only 1 of these parameters is truly valid....the ES (or more =
generally 'an errored interval')....and if you read on you will =
understand (some of the reasons) why.

The definition of entry to the unavailable state is 10 consecutive SES.  =
These ES/SES events are then *excluded* from the NP SLA. Similarly, the =
exit from the unavailable state required 10 consecutive seconds with no =
SES events.....they could have ES events however, and if there were any =
these would need including in the NP SLA.  Note also that any ES events =
may also give rise to DM events.  And also note that the DM might =
straddle a period of unavailable time.  All rather messy.

You may hear me say from time to time 'don't use NP metrics as part of =
the (un)availability entry/exit criteria'.....the above hints at why =
this is, but I need to explain more about the above metrics to make this =
point even clearer.

I spent a great deal of time in late 80s and early 90s trying to =
properly understand the behaviour of Tx networks.  We built some =
specialised kit to study error event distributions.  And we found some =
nice mathematical models of real error distributions.  Forget Poisson =
stuff.  Digital Tx systems are not dominated by thermal noise.  The =
models we found that accurately characterised Tx systems had =
self-similar characteristics (due to ESD, weather related, human =
activity, etc).  More specifically, this work was based on the work of a =
colleague and good friend of mine called Andy Reid (I have mentioned his =
name before, this is also the guy who did the early functional modelling =
stuff too) and a mathematician from our labs called David Bond......in =
fact the 'Bond Model' was a development of the stuff Mandelbrot did =
earlier on error event distributions whilst he was with IBM (I think).  =
However, all this work was somewhat dry/academic.....but a major =
immediate conclusion from it was 'do not try and time-scale error metric =
objectives to shorter periods', eg if you have some objective to meet =
over a 1 month period (which is what G.821 requires) then simple =
statistical methods of deriving the confidence bounds for what you could =
expect in a shorter period (eg 15min, hour, or day say) just did not =
hold.  This is important for folks attempting to set provsioning levels =
and mtce thresholds in NEs.

These studies however showed us some other very important practical =
things.  Most error events were a short intense burst.  These could be =
expanded (in a non-linear way) as the error event propagated up nested =
layer networks by affecting framing and justification bits for example.  =
I am not going to go into the detail of this as it would take me pages =
to explain.

Now the errors event we saw came in 2 main flavours:
(i) us/ms events of error density 0.5
(ii) >1s events of error density 0.5

Consider the type (i) events first. If these existed for >2ms they would =
create an ES/SES pair event (0.5 error density over 2ms =3D 10^-3 error =
density over 1s). If these existed for <2ms they would always create an =
ES event but they might also create an ES/DM pair (that is, an error =
event lasting between 0.12ms and 2ms with an error density of 0.5 would =
create an error density >=3D10^-6 over a 1 min period).  What a =
nonsense!  If not obvious, the metrics being used (both SES, and (much =
worse) DM) bore no relationship to the event they were recording.  So we =
were measuring all this stuff that made absolutely no sense.

I then spent several years trying to convince folks to scrap =
DMs.....which thankfully they eventually did.  I did not have the heart =
to ram home the point that the SES metric was equally flawed....esp as =
it was also the basis for the availability specification.

However, the *practically* key observation is that I never saw a real =
nice/stable 10^-3 error density event in all the years I looked for =
them.....such nice stable Poisson behaviour was the stuff of fiction in =
digital Tx systems (it only applied to the old analogue Tx systems). But =
folks loved talking about BERs....and they still do it today!

Real error events knocked systems over, eg caused re-frames or such.  So =
the important things to measure were the defects like LOS, LOF.  I never =
saw a SES that did not cause a defect event.  And this is one of the =
reasons why I urge folks not to use NP metrics in any definition of =
entry/exit of the available state.....you can make life unnecessarily =
complex for no real benefit. Now I know one can't directly translate =
these observations of co-cs Tx networks to co-ps/cl-ps pkt networks, but =
I do believe the same general principles should apply.....and you are =
for sure going to get the server layer co-cs networks delivering these =
type of error events into their client layers.

Now let me come back to the type (ii) events I noted above.  I expected =
type (i) events to massively dominate the population and type (ii) =
events to be relatively rare.  The big shock we found was that of all =
the SES events the split was roughly 50:50. Type (ii) events could last =
up to say 3-4s and then just disappear.....if they lasted more than 4s =
they lasted forever, unless one took action to repair/restore the failed =
path.  This was worrying but it also explained something we had been =
noticing from customer complaints......folks were seeing 'short-break' =
events.  Note that a type (ii) event is 3 orders of magnitude more =
damaging than a type (i) event.....so no wonder it was affecting =
applications.  What concerned me at the time was that we had no way of =
distinguishing/measuring these 2 types of SES event if we threw them =
both in the same SES bucket.

We had some massive witch-hunts to discover what was the cause of these =
events, and although loads of components got changed out no one ever got =
to the bottom of them (at least AFAIK before I left this area of work).  =
We asked other operators to look for these events and sure enough they =
found them.  And although I had moved on at that time I believe they did =
eventually get specified in Rec G.826 (next gen G.821 for primary rate =
and above Tx networks) and were called 'consecutive SES (CSES) =
events'.....where a CSES event was defined as 2-10 consecutive SES =
events.

Now for those of you who have read the stuff I wrote-up in Y.1711 you =
may start to notice how I have drawn on the above experiences of real =
networks to shape, and simplify, MPLS OAM.  The defects are all based on =
harmonised 3s entry/exit periods to align with the error events that may =
or may not self-heal.....but if they don't self heal they give us the =
basis to measure short-break events.  I also stop NP counters on defect =
entry....again to make life simpler.  Unavailability is now based on =
defects that persist for 10s.  If you enter the unavailable state the NP =
counters are only re-enabled on entry to the available state....so there =
is some hysteresis here to make sure the network is stable =
again.....again this is aimed at keeping stuff simple.

There is actually a whole load of other stuff about Y.1711 that might =
not be apparent to someone on a cursory read that aims to make its =
simple.

Anyway, that is the origins of the 10s availability definition and some =
of the deeper stuff I know about that relate to it.  Hope those who =
asked for this found it useful.

<=3D=3D=3D=3D=3D=3D

50ms prot Sw target in SDH:

This one is much easier to explain.  I know the folks in BT who were =
active in the stds when this was originally being defined.  There is =
nothing magical about 50ms.  This was the figure folks thought was =
reasonable to assume in the largest SDH rings at the time based on =
propagation delay and processing requirements.  I was for sure *not* =
driven by any application requirements.  It also assumes one has access =
to the 'bottom-of-layered-network-stack' signal....so one can get a =
handle on real loss of signal at origin and thus accurately measure the =
defects.

We developed a general rule about prot-sw way back that I think still =
holds true today....as fast as possible as close to the duct as =
possible, and as slow as possible when close to the application.  If you =
read my explanation of the 10s availability stuff above you may have =
noted the significance of the type (ii) SES events here.  That is, at =
the network layers above the Tx networks (and I would place MPLS here) =
one does not want to be invoking prot-sw too fast because you could be =
erroneously triggering on error events that may go away.

Now its a while since I studied real error events on Tx networks so if =
anyone reading this has any newer information on what they look like =
today it would be good to hear about this.  However, if what I saw still =
holds true then we should be careful not to prot-sw too hastily above =
the Tx layer networks, eg at least make this configurable.  Of course =
one also must detect the defect first, and that will generally be to a =
lower resolution above the Tx layer networks.

Final point - I don't know any applications that need a 50ms restoration =
value.  Voice for sure does not.  Some old PSTN signalling protocols =
were a bit flaky......but then one should not penalise the whole future =
network behaviour on a flaky protocol, you should fix that protocol.  So =
I regards the folk chasing really fast restoration times above the Tx =
layer networks as in some 'macho arms race'.....I for sure don't see any =
logic or application drivers for this.

regards, Neil

> -----Original Message-----
> From: Harrison,N,Neil,IKL2 R=20
> Sent: 26 March 2004 10:58
> To: 'stbryant@cisco.com'
> Cc: Busschbach, Peter B (Peter); pwe3@ietf.org
> Subject: RE: [PWE3] RE: PW Availability
>=20
>=20
> <snipped>
> >=20
> > I am surprised that such a relatively large fixed number is=20
> specified.
> >=20
> > What is the rational for 10s?
> >=20
> > - Stewart
>=20
> Hi Stewart,
>=20
> This is what folks use to define availability in most=20
> telecoms networks and it is in common usage.  The value is=20
> historical (I can explain its roots if you are really=20
> intersted). You need some value specifying, and this is=20
> probably as good as any other for the purpose it=20
> serves......but it is not the full story of course. If you=20
> don't have an agreed definition of availability you cannot=20
> compare apples with apples. This affects at least 2 dimensions:
> -	in a horizontally partitioned layer network, ie=20
> spanning several operators domains......this also leads into=20
> partitioned performance allocations within (longer) reference=20
> connections
> -	in a vertically nested set of layer networks, ie one=20
> wants some form on uniformity of performance specification=20
> across each layer network
>=20
> Further, there is an ordering here.  PM measurements need to=20
> know the state of the network.  PMs measurements are only=20
> associated with the available state for SLA purposes....so=20
> clearly we need a common basis for PM measureements, and this=20
> is dependent on a common basis for availabilty. =20
> Unavailability is a function of defect persistence.  So one=20
> also needs a commonly agreed specification of defects (these=20
> are of course different for each mode).  And finally, though=20
> most importantly, to define the defects one needs to respect=20
> the func arch requirements of the mode considered......break=20
> that and you will have major problems doing the rest that is=20
> dependent on this anyway (as we know only too well).
>=20
> Please have a read through Y.1711.....its all done in there=20
> (and more....check out the stuff on short-breaks for example).
>=20
> Note - You could propose changing the definition of=20
> availability.....but we would still need some commonly agreed=20
> definition.   But I suspect you may get some kick-back from=20
> folks who want to retain the classical definition.  And to be=20
> honest I can't actually see changing it is really going to=20
> provide that much benefit....respecting the arch of the mode=20
> and having sound defect detection/handling is far more=20
> important IMO speaking as an operator.
>=20
> regards, Neil
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: RE: PW Availability
Date: Fri, 26 Mar 2004 20:05:18 +0200
Lines: 257
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "'Busschbach, Peter B (Peter) '" <busschbach@lucent.com>,
        "'pwe3@ietf.org '" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Fri Mar 26 19:11:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Stewart Bryant '" <stbryant@cisco.com>,
        "''neil.2.harrison@bt.com' '"
	 <neil.2.harrison@bt.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart and all,
I assume that 10 seconds delay for declaring a PW unavailable
is compliant with G.826 where a circuit is declared unavailable after 10
consecutive severely errored seconds (these secondsa are then alos
re-classified as unavailable). And, if I remember correctly, a defect 
renders a second when it was observed severely errored.

This explains (hopefully) the background for the definition you 
have questioned. Whetherthis definition is or is not suitable for PWs
is another question.

Regards,
                    Sasha

-----Original Message-----
From: Stewart Bryant
To: 'neil.2.harrison@bt.com'
Cc: Busschbach, Peter B (Peter); pwe3@ietf.org
Sent: 26/03/2004 12:28
Subject: Re: [PWE3] RE: PW Availability

I am surprised that such a relatively large fixed number is specified.

What is the rational for 10s?

- Stewart

Busschbach, Peter B (Peter) wrote:

> Neil,
> 
> I would be happy to add to draft-nadeau-pwe3-oam-msg-map-04.txt that a
PW is declared unavailable if a defect persists for more than 10
seconds. However, at this point I am not sure what that means since I
don't know how it affects anything that goes on in the network.
> 
> You have mentioned that it is important to recognize such a state,
because it determines when Performance Monitoring should be started and
stopped. However, from your response to my last email, it appears that a
clear and realistic approach to Performance Monitoring does not exist
yet. Therefore, I wonder what the point is of introducing concepts that
may or may not be relevant in the future.
> 
> Therefore, I propose that we add the following statements to
draft-nadeau-pwe3-oam-msg-map-04.txt:
> 
> a) in general (i.e. for other technologies), operators consider a
connection unavailable of a defect persists for more than 10 seconds
> 
> b) the interaction between PW fault management and Performance
Monitoring is for further study.
> 
> Further comments in-line.
> 
> Peter
> 
> 
>>-----Original Message-----
>>From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
>>Sent: Wednesday, March 24, 2004 5:53 PM
>>To: busschbach@lucent.com; pwe3@ietf.org
>>Subject: RE: PW Availability
>>
>>
>>Peter..
>>
>>>Neil,
>>>
>>>A while ago we exchanged emails on the availability of Pseudo 
>>>Wires. The relevant part is attached to this email.
>>>
>>>I agree with the observations you made, but my main question 
>>>was not answered: if you emulate a service over PWs,
>>
>>NH=> Can you define precisely what 'emulate' means here?
>>
> 
> 
> I meant "emulate" in the same way as it is used in all WG drafts and
emails on this mailing list: the encapsulation of client traffic so as
to transport it over a PSN.
> 
> 
>>>is it 
>>>really necessary to measure Network Performance (NP) of the 
>>>PW itself?
>>
>>NH=> Pass.  Depends on what the definition of 'emulation' 
>>really meens (and I have no idea) and what a PW actually 
>>is....to me its some form of adaptation.  XoverIP could have 
>>different perf to XoverMPLS....the defect behaviour is for 
>>sure very different.  I think folks really ought to 
>>differentiate these 2 cases as they are obviously not the same.
> 
> 
> I may be naive, but I would think that Network Performance to the
extend that it relates to SLAs should be independent of the network
layers over which the service is carried.
> 
> In fact, you assertion that defect behavior of IP and MPLS networks is
so different that XoverIP and XoverMPLS should be considered as two
totally different solutions suggests that NP measurements of X would
yield completely different results in the two cases. I can't see why
that would be desirable to Service Providers.
>  
> 
>>>If a Service Provider measures NP on end-to-end 
>>>ATM VCs, why is it necessary to obtain additional NP 
>>>measurements on one specific segment?
>>
>>NH=> To see where impairments are coming from say.  In a more 
>>general case if you have some global reference connection 
>>with metrics A, B, C that have objectives a, b, c (to be met 
>>over some period, eg month), you need some way to fairly 
>>apportion these to  partitions of the end-end path, eg to 
>>countries or operator domains.  So each partition need to 
>>check its bit is within its apportioned target.
>>
>>>Now, assuming that a Service Provider wants to measure NP of 
>>>PWs, how does that work?
>>
>>NH=> I have no idea....you are starting down the very 
>>slippery slope of making a PW a networked entity....and it is 
>>not (as yet anyway).
> 
> 
> I am  not sure who started down the slippery slope. I did not say
there was a need for an availability state for PWs. You did. I am
actually arguing for the position that it doesn't make sense to measure
NP for Pseudo Wires.
> 
> 
> 
>>>I assume that it is based on 
>>>comparing packet counts both at ingress and egress. Following 
>>>the method proposed by Y.1711, performance measurements are 
>>>stopped upon detection of a defect and restarted a certain 
>>>period after the defects disappears and the connection is 
>>>stable again. However, in general a defect exists some time 
>>>before a connection end-point finds out. Therefore, a number 
>>>of packets will have been dropped already. Rather than trying 
>>>to minimize the effect of this time lag by specifying 
>>>available/unavailable state, as Y.1711 does, would it not 
>>>make more sense to sanitize the data in an off-line 
>>>performance monitoring tool that can exclude counts taken 
>>>just before the defect occurred?
>>
>>NH=> Y.1711 has not defined any NP collection yet.  Its more 
>>important to get the basic defects, short-breaks and 
>>unavailability bits done 1st.  NP stuff can be added later on 
>>this firm defect detection/handling basis.  I can think of 
>>some smart/simple ways of doing NP collection however.....the 
>>details are not given in Y.1711 right now. One also has to be 
>>aware of 'PDUs in flight'.  
>>
>>>In short: how exactly do Service Prodivers measure Network 
>>>Performance?
>>
>>NH=> Badly to date is my view.  Why?  Because the ordering I 
>>mentioned in the mail below has never properly been executed 
>>in the past.
> 
> 
> I am not sure what point you are trying to make. Service Providers (BT
being one of them) have large networks in which they run ATM over SDH or
SONET. I was not asking a rhetorical question. I am genuinely interested
to learn more about operator experiences.
> 
> However, if you say that even ATM-over-SDH is such a mess that decent
Performance Monitoring is not possible, then what does that mean for our
current work? Existing networks will not go away for a long time to
come. We have to work with what we have. Especially with regards to PWE,
I don't see how we can work on Performance Monitoring without taking
existing protocols and techniques into account.
> 
> 
> 
> 
>>>Peter
>>>
>>>
>>>>-----Original Message-----
>>>>From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
>>>>Sent: Monday, March 01, 2004 3:57 PM
>>>
>>>>>>2	There is no demarcation between the available state and 
>>>>>>unavailable state for network trail entities.  This means 
>>>>>>there is no temporal basis for the specification of an 
>>>>>>availability SLA or a network performance SLA, noting that 
>>>>>>the latter is only relevant to the available state.  These 
>>>>>>impact network element specifications and thus have 
>>>>>>consequential impact on NMS/OSS.  NE and NMS/OSS 
>>>>>>considerations are important for an operator to see correctly 
>>>>>>executed.  CF Y.1711 where the unavailable state is specified 
>>>>>>(as a consequential persistence of defects).
>>>>>>
>>>>>
>>>>>Adding a definition of availabillity would be pretty easy to 
>>>>>specify and implement. I would like to understand better, 
>>>>>though, how this would be used in practice. It seems to me 
>>>>>that SLAs apply to the services carried over PWs, not to the 
>>>>>PWs themselves.
>>>>
>>>>NH=> Several points here.
>>>>
>>>>First, there is a difference between QoS and Network 
>>>>Performance (NP) metrics/objectives.  The former are what a 
>>>>specific application percieves, whereas the latter are 
>>>>application invariant (ie for a given level of NP impairment 
>>>>different applications can have quite a different perspective 
>>>>on QoS).  NP metrics are really what the network elements 
>>>>should capture and SLAs specify.
>>>>
>>>>Second, the control of availability and NP are complementary 
>>>>performance requirements.  If one does not have an agreed 
>>>>datum at which NP metrics should no longer be counted then 
>>>>one can easily distort the NP SLA.  There is also the 
>>>>requirement to measure the same 'apples and apples' here in 
>>>>different networks/equipment.....and this also applies 
>>>>*across* nested layer networks (the commonly agreed 
>>>>integration period for assessing availability is based on 10s 
>>>>of outage). Further, a service which has a 99% unavailability 
>>>>can still have perfect NP......this is why these metrics are 
>>>>complimentary.  See section 7 of Y.1711 for more info.
>>>>
>>>>Third, there is a key ordering behaviour here:
>>>>=> ensure the right net arch for mode considered 1st
>>>>=> this allows the relevant defects to be identified
>>>>=> this allows appropriate OAM to be specified (and from this 
>>>>defect entry/exit criteria and consequent actions)
>>>>=> this allows unavalability entry/exit criteria to be 
>>>>specified based on defect persistence
>>>>=> this allows the up-time to be specified over which NP 
>>
>>is relevent
>>
>>>>You can very easily make life more complex than it need be by 
>>>>not following this ordering.  Further, and for complexity 
>>>>reasons, I would also not advise using NP metrics within the 
>>>>availability entry/exit criteria.....just use defect 
>>>>persistency.  Much careful thought went into Y.1711 on these, 
>>>>and several other, matters that may not be readily apparent 
>>>>to someone on a cursory reading.
>>>>
> 
> _______________________________________________
> 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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pwe3-hdlc-ppp-encap-mpls-02.txt
Date: Fri, 26 Mar 2004 15:57:40 -0500
Lines: 82
Sender: pwe3-admin@ietf.org
Reply-To: Internet-Drafts@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Fri Mar 26 21:58:15 2004
Return-path: <pwe3-admin@ietf.org>
To: IETF-Announce: ;
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--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		: Encapsulation Methods for Transport of PPP/HDLC Over IP and MPLS Networks
	Author(s)	: L. Martini, T. Smith
	Filename	: draft-ietf-pwe3-hdlc-ppp-encap-mpls-02.txt
	Pages		: 10
	Date		: 2004-3-26
	
A Pseudowire (PW) can be used to carry PPP, or HDLC Protocol Data
Units over an IP or MPLS network without terminating the PPP/HDLC
protocol. This enables service providers to offer 'emulated' HDLC, or
PPP link services over existing IP or MPLS networks. This document
specifies the encapsulation of PPP/HDLC PDUs within a pseudowire.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-hdlc-ppp-encap-mpls-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-hdlc-ppp-encap-mpls-02.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-hdlc-ppp-encap-mpls-02.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"

Content-Type: text/plain
Content-ID:	<2004-3-26161431.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-hdlc-ppp-encap-mpls-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pwe3-hdlc-ppp-encap-mpls-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-26161431.I-D@ietf.org>

--OtherAccess--

--NextPart--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Sun, 28 Mar 2004 11:46:28 +0200
Lines: 19
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Cc: "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Sun Mar 28 11:52:07 2004
Return-path: <pwe3-admin@ietf.org>
To: "Luca Martini (E-mail)" <lmartini@cisco.com>,
        "Mark Townsley (E-mail)"
	 <townsley@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Luca and Mark,
I have just read the newly posted draft-ietf-pwe3-iana-allocation-03.
Unfortunately, some issues raised at the Seoul meeting and later on 
this list wrt the TDM PWs have not been addressed:

1. Renaming the CEP Payload Bytes interface parameter to CEP/TDM Payload
Bytes
2. Allocation of a new interface parameter ID for TDM options (could be
0x0b)
3. Allocation of a new LDP status code - TDM mis-configuration (could be
0x00000029).

Hopefully these issues can be easily addressed before the WG Last Call.
With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: =?iso-8859-1?Q?Bj=F6rn_Bergl=F6f?= <Bjorn.Berglof@xelerated.com>
Subject: RE: 16 bit interpretation of sequence checking?
Date: Mon, 29 Mar 2004 10:24:59 +0200
Lines: 463
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Mon Mar 29 10:28:15 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Thread-Topic: [PWE3] 16 bit interpretation of sequence checking?
Thread-Index: AcQBFA8kEjiwrm9ETLecIQN4cUdj3AAEDGSQBRBQroA=
To: <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


For completeness, I want to share that the algorithm in=20
"draft-ietf-pwe3-atm-encap-04.txt" CAN be simplified=20
using pure 16 bit arithmetic in stead of assuming 32 bit=20
logic and having to use cumbersome range checking.

    diff <- SeqNo - ExpNo;
    if ((SeqNo=3D0) or (diff[15]=3D0) then OK<-True;
    else OK<-False;
    end if;
    if (OK=3DTrue) then NewExpNo <- (SeqNo=3DFFFFh) ? 1 : SeqNo+1;
    end if;

Regards,
    / Bj=F6rn

-------------------------------------------------
OK, in that case I think it is all right.=20

Of course, if SeqNo=3D0 then there is no need to compute
diff or to check its sign, but that might not matter in your case.

Y(J)S

> -----Original Message-----
> From: Bjorn.Berglof@xelerated.com=20
> [mailto:Bjorn.Berglof@xelerated.com]=20
> Sent: Tuesday, March 09, 2004 15:18
> To: Yaakov Stein
> Cc: Bj?rn Bergl?f
> Subject: Again: Still do not get the difference; 16 bit=20
> interpretation of sequence checking?
>=20
>=20
> Thanks Yaakov,
> I think we are closer to understand each other...
> First to answer your questions/comments:
>=20
>  - I see your point about using side-effects. They are=20
>    however inpractical in hardware modelling languages,
>    while multi-output functions is sort of 'normal'.
>=20
>  - I also see that our different understandings of the code comes=20
>    from this difference in sequential/parallel views of the world.=20
>    As you may note the 'SeqNo' never changes value during the=20
>    evaluation of the function. Rather the NewExpNo is 'saved'
>    and used next time the function is called.
>=20
>  - Yes I assume bit 15 is MSB.
>    But my code uses unsigned logic which means that the=20
>    number should be interpreded as 0->65536. (However signed=20
>    (2-complement) or unsigned does not matter in my code since
>    I look at subtraction bits directly, not using outcome
>    of status bits.)
>=20
>  - You probably noticed that I avoid the '-2^15' stuff in your
>    code since it will only invert the bit 15.=20
>=20
>  - I actually meant =3D> to mean "leads to" or "results in".
>    Rather sloppy writing actually.
>=20
> > First, you are missing the following in each update of the expected=20
> > number
> >   NewExpNo <- SeqNo+1
> >   (NewExpNo =3D 0) =3D> NewExpNo <- 1
>=20
>  - No, I do not believe I missed that. In my original psueudo-code
>    I use a ? : operator whenever I set the new sequence value which
>    takes care of the 'skip-the-zero-in-a-sequence', only I check
>    for the FFFFh value in stead of doing 'inc' and then check for=20
>    zero (again because it is more effective H/W-wise). Same, yes ?=20
>=20
>  - Regarding late packets, I do not reorder any packets. The aim
>    is mainly to simplify the sequence check operation, when the=20
>    rate is very high and the number of sequency counters are high.
>    The H/W function will only return the OK/Not-OK back to the=20
>    processor.=20
>=20
>  - Rewriting my psueudo-code in line with your terminology:
>=20
>    diff <- SeqNo - ExpNo;
>    if ((SeqNo=3D0) or (diff[15]=3D0) then OK<-True;
>    else OK<-False;
>    end if;
>    if (OK=3DTrue) then NewExpNo <- (SeqNo=3DFFFFh) ? 1 : SeqNo+1;
>    end if;
>=20
> Given the claerifications above, have I still missed something?
> Best regards,
>     / Bj?rn
>=20
>=20
>=20
> > -----Original Message-----
> > From: Yaakov Stein [mailto:yaakov_s@rad.com]
> > Sent: Sunday, March 07, 2004 07:49
> > To: Bj?rn Bergl?f
> > Subject: RE: Still do not get the difference; 16 bit=20
> interpretation of=20
> > sequence checking?
> >=20
> >=20
> > Bjorn,
> > =20
> >=20
> > > Hi,
> > > thanks for your reply. I've still a bit confused; hope it's OK to=20
> > > send a follow-up question 'off-line'.
> >=20
> > Of course !
> >=20
> >=20
> > > First a question:
> > >  Do you not mean (received-expected) in stead of
> > >  (expected-received) in your psueudo-code ?
> >=20
> > ooops!  yes, that is right.
> >=20
> > >  That would fit better withe the paper and my thinking.
> > >  Anyway, I asume that in the following...
> > >=20
> > > I'm a bit confused of your uses of 'IMMEDIATELY' and 'AFTER'.
> > > The way I see it is that sequence checking is a function with two=20
> > > input data and two output data:
> > >   =20
> > >    SeqNo     : The packet seq number. (16b)
> > >    ExpNo     : The saved value between packet processings. (16b)
> > >    OK        : Pass/Packet is in order. Controls what to do with=20
> > >                the packet. (1b)
> > >    NewExpNo  : Updated value to be saved. (16b)
> >=20
> > OK, although I would think of it as a function returning an=20
> OK value,=20
> > and updating the ExpNo, i.e.
> >      function IsCorrectSN( in RecSeqNo, inout ExpNo) : boolean
> >=20
> > >=20
> > > Given this, I can not see any difference between mine=20
> psueudo-code=20
> > > and yours :
> > >=20
> > > ---------------------------- Equality case. Same, yes ?
> > > Mine:
> > >    (SeqNo=3DExpNo) =3D> Diff=3D0 =3D> Diff bit 15=3D0 =3D>=20
> > >    OK=3D1, NewExpNo=3DSeqNo+1.
> > > Yours:
> > >    if received =3D expected then=20
> > >         treat packet as in-order=20
> > >         set expected =3D (received + 1) mod 2^16
> >=20
> > To ensure that this is the same I have to understand your=20
> erminology.=20
> > I assume that bit 15 is the MSB of a 16 bit register  (i.e.=20
> the LSB is=20
> > numbered 0) and that you are using 2s complement=20
> arithmetic, and that=20
> > 1 is considered "true".
> > Furthermore, I assume that =3D> means if .. then and =3D means =
equality=20
> > check (not asignment).
> > Then there shouldn't be so many =3D> (causes) but rather separate=20
> > assignment statements (I use <- to mean assignment).
> >=20
> >   Diff <- (SeqNo-ExpNo)
> >   Diff =3D 0 =3D> OK <- 1; NewExpNo <- SeqNo+1
> >=20
> > > ----------------------------- In-order case. Same, yes ?
> > > Mine:
> > >    (SeqNo-ExpNo) =3D> Diff is positive =3D> Diff bit 15=3D0 =3D>
> > >    OK=3D1, NewExpNo=3DSeqNo+1.
> > >=20
> > > Yours:
> > >     calculate D =3D ((received-expected) mod 2^16 )) - 2^15=20
> > >     if D > 0 then
> > >         packets expected, expected+1, ... received-1 have not been
> > received
> > >         set expected =3D (received + 1) mod 2^16
> >=20
> > Do you mean the following?
> >=20
> >   Diff <- (SeqNo-ExpNo)
> >   Diff bit 15 =3D 0 =3D> OK <- 1; NewExpNo <- SeqNo+1
> > =20
> > > ----------------------------- Out-of-order case. Same, yes ?
> > > Mine:
> > >     (SeqNo-ExpNo) =3D> Diff is negative =3D> Diff bit 15=3D1
> > >     OK=3D0;
> > >=20
> > > Yuors
> > >     calculate D =3D ((received-expected) mod 2^16 ) - 2^15
> > >     if D > 0 then  ...
> > >     else =20
> > >             late packet arrived
> > >             do NOT update expected
> >=20
> >   Diff bit 15 =3D 1  =3D> OK=3D0;
> > =20
> > > ------------------------------------------------------------------
> > >=20
> > > Please help me see in which aspect the codes differ. Since we are=20
> > > looking at implementing this in hardware (to support 100M=20
> checks/s=20
> > > or so) it is important that no mistakes slips through.
> >=20
> > First, you are missing the following in each update of the expected=20
> > number
> >   NewExpNo <- SeqNo+1
> >   (NewExpNo =3D 0) =3D> NewExpNo <- 1
> >=20
> > Second, this handles the sequence numbers, but what do you do about=20
> > late packets?
> > Do you allow them (and re-order) if they are still "in time" ?
> >=20
> >=20
> > >=20
> > > Best regards,
> > >      / Bj?rn
> > >=20
> > >      =20
> > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >     / Bj?rn 'Mr Bear' Bergl?f
> > >    /  Xelerated:   08  - 506 257 94 =20
> > > mailto:bjorn.berglof@xelerated.com
> > >   /   Mobile:      0733- 277 808     http://www.mrbear.se
> > >  /    Home office: 08  - 532 532 69  mailto:bjorn@mrbear.se
> > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > =20
> > >=20
> > >=20
> > >=20
> > >=20
> > >=20
> > >=20
> > >=20
> > >=20
> > >=20
> > > > -----Original Message-----
> > > > From: Yaakov Stein [mailto:yaakov_s@rad.com]
> > > > Sent: Wednesday, March 03, 2004 14:46
> > > > To: Bj?rn Bergl?f; pwe3@ietf.org
> > > > Subject: RE: [PWE3] 16 bit interpretation of sequence checking?
> > > >=20
> > > >=20
> > > > > QUESTION 1:
> > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > > Is "the packet passes the sequence number check" the
> > same as "the
> > > > > packet is in order" ? I.e, Should the
> > expected_sequence_number be
> > > > > updated if the sequence number i 0 ?
> > > >=20
> > > > Passes the sequence number check =3D=3D is in order =3D=3D has
> > not arrived
> > > > later than a packet sent earlier (although packets may be
> > missing).
> > > >=20
> > > > If the sequence number is zero, it is IMMEDIATELY
> > > incremented before
> > > > the test. After the test passes the expected sequence number is=20
> > > > incremented. If the test fails (i.e. the packet=20
> received was sent=20
> > > > earlier than a packet previously received) then the epected
> > > number is
> > > > not incremented.
> > > > =20
> > > > > QUESTION 2:
> > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > > I enterpret this rather complex description above as a
> > > way to map 16
> > > > > bit behaviour into a 32 bit environment. As a hardware
> > designer I
> > > > > have a hard time convincing myself (and others) that
> > the above is
> > > > > equivalent to the following psueudo-code:
> > > > >=20
> > > > >       diff =3D SeqNo - ExpNo;
> > > > >       if ((SeqNo=3D0) or (diff[15]=3D0) then OK;
> > > > >       else NOT_OK;
> > > > >       end if;
> > > > >       if OK then NewExpNo =3D (SeqNo=3DFFFF) ? 1 : SeqNo+1;
> > > > >       end if;
> > > > >=20
> > > > > where all variables are 16 bit and count operations allow
> > > > wrap-around.
> > > >=20
> > > > You are have a hard time because it isn't the same.
> > > > You are checking for equality with the next packet number,
> > > while the
> > > > test in the draft is for equal OR AFTER the expected
> > > sequence number.
> > > >=20
> > > > Try thinking about it in the following way:
> > > >=20
> > > >    if received =3D expected then
> > > >        treat packet as in-order=20
> > > >        set expected =3D (received + 1) mod 2^16
> > > >    else
> > > >        calculate D =3D ( (expected-received) mod 2^16 ) - 2^15
> > > >        if D > 0 then
> > > >            packets expected, expected+1, ... received-1
> > > have not been
> > > > received
> > > >            set expected =3D (received + 1) mod 2^16
> > > >        else =20
> > > >            late packet arrived
> > > >            do NOT update expected
> > > >=20
> > > > Y(J)S
> > > >=20
> > > >=20
> > >=20
> > >=20
> >=20
>=20
>=20









> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
> Sent: Wednesday, March 03, 2004 14:46
> To: Bj=F6rn Bergl=F6f; pwe3@ietf.org
> Subject: RE: [PWE3] 16 bit interpretation of sequence checking?
>=20
>=20
> > QUESTION 1:
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Is "the packet passes the sequence number check" the same as=20
> > "the packet is in order" ? I.e, Should the=20
> > expected_sequence_number be updated if the sequence number i 0 ?
>=20
> Passes the sequence number check =3D=3D is in order =3D=3D has not =
arrived
> later than a packet sent earlier (although packets may be missing).
>=20
> If the sequence number is zero, it is IMMEDIATELY incremented
> before the test. After the test passes the expected sequence number
> is incremented. If the test fails (i.e. the packet received was sent
> earlier
> than a packet previously received) then the epected number is not
> incremented.
> =20
> > QUESTION 2:
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > I enterpret this rather complex description above as a way to=20
> > map 16 bit behaviour into a 32 bit environment. As a hardware=20
> > designer I have a hard time convincing myself (and others)=20
> > that the above is equivalent to the following psueudo-code:
> >=20
> >       diff =3D SeqNo - ExpNo;
> >       if ((SeqNo=3D0) or (diff[15]=3D0) then OK;
> >       else NOT_OK;
> >       end if;
> >       if OK then NewExpNo =3D (SeqNo=3DFFFF) ? 1 : SeqNo+1;
> >       end if;
> >=20
> > where all variables are 16 bit and count operations allow=20
> wrap-around.
>=20
> You are have a hard time because it isn't the same.
> You are checking for equality with the next packet number,
> while the test in the draft is for equal OR AFTER the expected
> sequence number.
>=20
> Try thinking about it in the following way:
>=20
>    if received =3D expected then
>        treat packet as in-order=20
>        set expected =3D (received + 1) mod 2^16
>    else
>        calculate D =3D ( (expected-received) mod 2^16 ) - 2^15
>        if D > 0 then
>            packets expected, expected+1, ... received-1 have not been
> received=20
>            set expected =3D (received + 1) mod 2^16
>        else =20
>            late packet arrived
>            do NOT update expected
>=20
> Y(J)S
>=20

BACKGROUND:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
In "draft-ietf-pwe3-atm-encap-04.txt" section 4.3.4 describes
the sequence number processing as:
     =
----------------------------------------------------------------------
     - if the sequence number on the packet is 0, then the packet passes
       the sequence number check.

     - otherwise if the packet sequence number >=3D the expected =
sequence
       number and the packet sequence number - the expected sequence
       number < 32768, then the packet is in order.

     - otherwise if the packet sequence number < the expected sequence
       number and the expected sequence number - the packet sequence
       number >=3D 32768, then the packet is in order.

     - otherwise the packet is out of order.

   If a packet is in order then, it can be delivered immediately. If the
   packet is in order, then the expected sequence number MUST be set
   using the algorithm:

   expected_sequence_number :=3D packet_sequence_number + 1 mod 2**16
   if (expected_sequence_number =3D 0) then expected_sequence_number:=3D =
1;
     =
----------------------------------------------------------------------

QUESTION 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Is "the packet passes the sequence number check" the same as=20
"the packet is in order" ? I.e, Should the expected_sequence_number
be updated if the sequence number i 0 ?

QUESTION 2:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I enterpret this rather complex description above as a way to map 16 bit =

behaviour into a 32 bit environment. As a hardware designer I have=20
a hard time convincing myself (and others) that the above is equivalent=20
to the following psueudo-code:

      diff =3D SeqNo - ExpNo;
      if ((SeqNo=3D0) or (diff[15]=3D0) then OK;
      else NOT_OK;
      end if;
      if OK then NewExpNo =3D (SeqNo=3DFFFF) ? 1 : SeqNo+1;
      end if;

where all variables are 16 bit and count operations allow wrap-around.
All comments are appreciated.
      / Bj=F6rn


     =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    / Bj=F6rn 'Mr Bear' Bergl=F6f
   /  Xelerated:   08  - 506 257 94  mailto:bjorn.berglof@xelerated.com
  /   Mobile:      0733- 277 808     http://www.mrbear.se
 /    Home office: 08  - 532 532 69  mailto:bjorn@mrbear.se
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Ashok Singh <singh_ashok_k@yahoo.com>
Subject: VC TYPE 5 Support
Date: Mon, 29 Mar 2004 00:34:53 -0800 (PST)
Lines: 43
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1071957751-1080549293=:97504"
X-From: pwe3-admin@ietf.org Mon Mar 29 10:37:03 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--0-1071957751-1080549293=:97504
Content-Type: text/plain; charset=us-ascii

Hello All,
 
I want to know if there are products in market that support VC TYPE 5 as mentioned in the pwe3 drafts. 
My initial understanding seems to indicate that: 
 
CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM documents)
 
Riverstone also does not support VC TYPE 5 but achieves this (Port based L2 FEC support)  by using VC TYPE 4 (Ethernet VLAN) only, requiring hybrid port/trunk port/access port vlan configuration.
 
Only Juniper seems to have support for VC TYPE 5, as mentioned in the requirements (configuring Ethernet ccc) in its configuration documents.
 
Any comments from the group? Does it imply that purpose of VC TYPE 5 can even be achieved with VC TYPE 4 as done by some vendors? Please correct me if I am going wrong anywhere.
 
Regards,



---------------------------------
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
--0-1071957751-1080549293=:97504
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>Hello All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I want to know if there are products in market that support VC TYPE&nbsp;5 as mentioned in the pwe3 drafts. </DIV>
<DIV>My initial understanding seems to indicate that: </DIV>
<DIV>&nbsp;</DIV>
<DIV>CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM documents)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Riverstone also does not support VC TYPE&nbsp;5 but achieves this (Port based L2 FEC support)&nbsp; by using VC TYPE&nbsp;4 (Ethernet VLAN) only, requiring hybrid port/trunk port/access port&nbsp;vlan configuration.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Only Juniper seems to have&nbsp;support for VC TYPE 5, as mentioned in the requirements (configuring Ethernet ccc) in its configuration documents.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Any comments from the group? Does it imply that purpose of&nbsp;VC TYPE 5 can even be&nbsp;achieved with VC TYPE 4 as done by some vendors? Please correct me if I am going wrong anywhere.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards,</DIV></DIV><p><hr size=1><font face=arial size=-1>Do you Yahoo!?<br>
<a href="http://taxes.yahoo.com/filing.html"><b>Yahoo! Finance Tax Center</a></b> - File online. File on time.
--0-1071957751-1080549293=:97504--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Orly Nicklass" <orly_n@rad.com>
Subject: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 11:51:25 +0100
Lines: 55
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 29 12:54:06 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-topic: [PWE3] Comments to draft-ietf-pwe3-iana-allocation-03
Thread-index: AcQUqm/y/8T5JAeDQLKkY1ZvD3RucwAz+Ywg
To: "Sasha Vainshtein" <Sasha@AXERRA.com>,
        "Luca Martini \(E-mail\)" <lmartini@cisco.com>,
        "Mark Townsley \(E-mail\)" <townsley@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

It seems like there is also miscounting or typo err in the newly added
PW types.
First there are two "0x0011", then assuming we want those two, the text
in section 2 should relate to dec values and not to hex values. (18 and
19 in the text should be changed) See below.


"....PW Type values 1 through 18
   are defined in this document. PW Type values 19 through 63 are to be
   assigned by IANA using the "IETF Consensus" policy defined in
   RFC2434.
...
      0x0010   SONET/SDH Circuit Emulation over Packet (CEP)
      0x0011   Structure-Agnostic TDM over Packet (SAToP)
      0x0011   Structure-agnostic E1 over Packet (SAToP)
      0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP)
      0x0013   Structure-agnostic E3 over Packet (SAToP)
      0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP)
      0x0015   CESoPSN basic mode
      0x0016   TDMoIP basic mode
      0x0017   CESoPSN TDM with CAS
      0x0018   TDMoIP TDM with CAS "

-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
Sasha Vainshtein
Sent: Sunday, March 28, 2004 12:46
To: Luca Martini (E-mail); Mark Townsley (E-mail)
Cc: PWE3 WG (E-mail)
Subject: [PWE3] Comments to draft-ietf-pwe3-iana-allocation-03

Luca and Mark,
I have just read the newly posted draft-ietf-pwe3-iana-allocation-03.
Unfortunately, some issues raised at the Seoul meeting and later on this
list wrt the TDM PWs have not been addressed:

1. Renaming the CEP Payload Bytes interface parameter to CEP/TDM Payload
Bytes 2. Allocation of a new interface parameter ID for TDM options
(could be
0x0b)
3. Allocation of a new LDP status code - TDM mis-configuration (could be
0x00000029).

Hopefully these issues can be easily addressed before the WG Last Call.
With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: claude.kawa@sympatico.ca
Subject: FR/MPLS
Date: Mon, 29 Mar 2004 8:05:16 -0500
Lines: 3
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 29 15:08:05 2004
Return-path: <pwe3-admin@ietf.org>
X-Mailer: Openwave WebEngine, version 2.8.6.6 (webedge20-101-174-112-20020617)"
To: <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is just to let you know that ITU-T SG 17 approved Recommendation X.84 (Frame relay over MPLS) at its last meeting. A number of issues raised after the last call were resolved. X.84 is technically the same as PWE3 draft on frame relay over pseudo-wires.  

claude kawa


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 10:27:08 -0700
Organization: Cisco Systems
Lines: 50
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1106@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 29 19:30:12 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031020
X-Accept-Language: en-us, en
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1106@TLV1>
X-PMX-Version: 4.1.1.86173
X-from-outside-Cisco-experimental-header: [10.32.224.186]
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Sasha Vainshtein wrote:

>Luca and Mark,
>I have just read the newly posted draft-ietf-pwe3-iana-allocation-03.
>Unfortunately, some issues raised at the Seoul meeting and later on 
>this list wrt the TDM PWs have not been addressed:
>
>1. Renaming the CEP Payload Bytes interface parameter to CEP/TDM Payload
>Bytes
>  
>
ok this will need to be updated in the draft-ietf-pwe3-sonet-03.txt as well.

>2. Allocation of a new interface parameter ID for TDM options (could be
>0x0b)
>  
>
ok, but we need to find a location for the text in 
draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt

I suggest that this text be included in it's  respective document.
In te future when we might add new technologies we do not want to go 
edit the original control protocol RFC every time.

>3. Allocation of a new LDP status code - TDM mis-configuration (could be
>0x00000029).
>
>  
>
We only need one ? not the 6 that are defined in 
draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt ?

( I added only this one. )

Luca
( I 'll send the update after I get your response. )

>Hopefully these issues can be easily addressed before the WG Last Call.
>With best regards,
>                                   Sasha Vainshtein
>email:     sasha@axerra.com
>tel:       +972-3-7659993 (office)
>           +972-8-9254948 (res.)
>           +972-58-674833 (cell.)
>
>
>  
>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Dmitry Bokotey" <dbokotey@cisco.com>
Subject: RE: VC TYPE 5 Support
Date: Mon, 29 Mar 2004 11:29:04 -0800
Organization: Cisco Systems, Inc
Lines: 338
Sender: pwe3-admin@ietf.org
References: <20040329083453.97869.qmail@web80803.mail.yahoo.com>
Reply-To: <dbokotey@cisco.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_010E_01C41581.0B3D2EA0"
X-From: pwe3-admin@ietf.org Mon Mar 29 19:32:04 2004
Return-path: <pwe3-admin@ietf.org>
X-BrightmailFiltered: true
To: "'Ashok Singh'" <singh_ashok_k@yahoo.com>, <pwe3@ietf.org>
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <20040329083453.97869.qmail@web80803.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcQVaSbNWnp+GHhSSWyr/yiHPjjugwAWrdCQ
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_010E_01C41581.0B3D2EA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Where did you get this information only Juniper supports VC TYPE 5

Cisco does support vc-type 5 port transparency.

 

 

  _____  

From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of Ashok
Singh
Sent: Monday, March 29, 2004 12:35 AM
To: pwe3@ietf.org
Subject: [PWE3] VC TYPE 5 Support

 

Hello All,

 

I want to know if there are products in market that support VC TYPE 5 as
mentioned in the pwe3 drafts. 

My initial understanding seems to indicate that: 

 

CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM
documents)

 

Riverstone also does not support VC TYPE 5 but achieves this (Port based L2
FEC support)  by using VC TYPE 4 (Ethernet VLAN) only, requiring hybrid
port/trunk port/access port vlan configuration.

 

Only Juniper seems to have support for VC TYPE 5, as mentioned in the
requirements (configuring Ethernet ccc) in its configuration documents.

 

Any comments from the group? Does it imply that purpose of VC TYPE 5 can
even be achieved with VC TYPE 4 as done by some vendors? Please correct me
if I am going wrong anywhere.

 

Regards,

  _____  

Do you Yahoo!?
 <http://taxes.yahoo.com/filing.html> Yahoo! Finance Tax Center - File
online. File on time.


------=_NextPart_000_010E_01C41581.0B3D2EA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Where did you get this information =
only
Juniper supports </span></font>VC TYPE 5<o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Cisco does support vc-type 5 port =
transparency.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Ashok Singh<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, =
2004 12:35
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pwe3@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [PWE3] VC TYPE 5 =
Support</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hello All,<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I want to know if there are products in market that support VC
TYPE&nbsp;5 as mentioned in the pwe3 drafts. =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>My initial understanding seems to indicate that: =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>CISCO's AToM does not support VC TYPE 5 (apparent from the =
recent AToM
documents)<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Riverstone also does not support VC TYPE&nbsp;5 but achieves =
this (Port
based L2 FEC support)&nbsp; by using VC TYPE&nbsp;4 (Ethernet VLAN) =
only,
requiring hybrid port/trunk port/access port&nbsp;vlan =
configuration.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Only Juniper seems to have&nbsp;support for VC TYPE 5, as =
mentioned in
the requirements (configuring Ethernet ccc) in its configuration =
documents.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Any comments from the group? Does it imply that purpose =
of&nbsp;VC TYPE
5 can even be&nbsp;achieved with VC TYPE 4 as done by some vendors? =
Please
correct me if I am going wrong anywhere.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Regards,<o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do you Yahoo!?<br>
<a href=3D"http://taxes.yahoo.com/filing.html"><b><span =
style=3D'font-weight:bold'>Yahoo!
Finance Tax Center</span></b></a> - File online. File on =
time.</span></font><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_010E_01C41581.0B3D2EA0--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.
	txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 11:18:28 -0500
Lines: 269
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: andy.bd.reid@bt.com, alan.mcguire@bt.com, peter.j.willis@bt.com,
        richard.spencer@bt.com, benjamin.niven-jenkins@bt.com,
        dave.milham@bt.com
X-From: pwe3-admin@ietf.org Mon Mar 01 17:25:16 2004
Return-path: <pwe3-admin@ietf.org>
To: "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>, mmorrow@cisco.com,
        pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> Sent: Monday, March 01, 2004 7:55 AM
> To: mmorrow@cisco.com; pwe3@ietf.org
> Cc: andy.bd.reid@bt.com; alan.mcguire@bt.com; peter.j.willis@bt.com;
> richard.spencer@bt.com; benjamin.niven-jenkins@bt.com;
> dave.milham@bt.com
> Subject: RE: [PWE3] Proposal to Progress
> draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
> 
> 
> <converted to plain text from original HTML format>
> 
> Monique Morrow wrote 01 March 2004 04:00
> I presented OAM Msg Mapping status today in Seoul, 
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-
> map-04.txt with a proposal to progress the draft as a Working 
> Group item  
>  
> Whilst we had no opposition the room, I would like to ensure 
> that there is consensus on the list to progress the draft as 
> a WG item.
>  
> Essentially, the draft has been revised to reflect 
> like-to-like constructs as per the scope of PWE3 and, covers 
> fault detection and alarm message mapping as two separate elements.
> ====
> 
> We (ie BT) cannot support this document as it stands for 
> several reasons....for example:
> 
> 1	No defects are defined anywhere (not just in here but 
> in any other IETF draft/rfc) in terms of clear entry/exit 
> criteria and consequent actions.  Note that the defects in 
> MPLS are different to the defects in IP.....which should not 
> be surprising as their modes are different, and even this 
> draft recognises that fact (also see 4).  CF Y.1711 where 
> these are specified.
> 

The draft identifies several tools for fault detection. IMO, the documents that describe these tools should define entry and exit criteria. The BFD draft already does that. To the extent that the OAM Message Mapping draft should add clarity on entry and exit criteria, we could add that to subsequent drafts.

> 
> 2	There is no demarcation between the available state and 
> unavailable state for network trail entities.  This means 
> there is no temporal basis for the specification of an 
> availability SLA or a network performance SLA, noting that 
> the latter is only relevant to the available state.  These 
> impact network element specifications and thus have 
> consequential impact on NMS/OSS.  NE and NMS/OSS 
> considerations are important for an operator to see correctly 
> executed.  CF Y.1711 where the unavailable state is specified 
> (as a consequential persistence of defects).
> 

Adding a definition of availabillity would be pretty easy to specify and implement. I would like to understand better, though, how this would be used in practice. It seems to me that SLAs apply to the services carried over PWs, not to the PWs themselves. 

> 
> 3	Seq Nos cannot be left 'open-ended' wrt aberration 
> handling.  At some degree of persistent corruption a defect 
> state must be declared.  This therefore requires entry/exit 
> criteria and consequent actions specifying.  We note this is 
> at least recognised as an open issue in section 4.1.1.
> 

agreed

> 
> 4	A PW is *not* a networked entity....it is just an 
> adaptation function (now whether it is a good adaptation 
> function for the server layer considered is a different 
> consideration).  An LSP however is a networked path entity in 
> the case of using MPLS (co-ps mode).  Similarly, an IP pkt is 
> also a networked entity (in the case of an IP cl-ps mode 
> server layer).  XoverMPLS is therefore not the same as 
> XoverIP....I am perplexed as to why this fact so hard for 
> some folks to grok/accept.  Is it to make the work palatable 
> to IETF folks?  But who is kidding who here?  Whilst this 
> stance might be necessary to 'sell' this stuff in IETF, 
> speaking as an operator we can't afford to base future 
> network investments on such misplaced ideologies....we need 
> this stuff properly architecting else it will impact our 
> costs (both capex and opex) and the efficacy of the services 
> we can offer.  
> 
> This distinction between MPLS and IP is even recognised in 
> the draft.....for example, in section 4.1 it says:
> 
> "In case of MPLS there are additional failures (see also [ITU-T 
>    Y.1710]). E.g. 
>     
>    . PW mislabeling, which could be due to a failure on the 
> ingress PE 
>      or due to an over-writing of the PW label value somewhere along 
>      the way 
>     
>    . Label swapping or LSP mismerge in the PSN network, which could 
>      result in the termination of a PW at the wrong egress PE. 
> 
>    . Unintended self-replication (e.g. due to loops or denial-of-
>      Service attacks) "
> 
> This is of course correct. Note that these defects *cannot* 
> occur in a cl-ps server layer like IP, which is precisely 
> what the above text implies, because a cl-ps server layer 
> must always have a network significant DA/SA pair in each 
> packet.  However, when using a co-ps forwarding mode like 
> MPLS this is not the case.  Here we have a trail entity (ie 
> an LSP) that is constructed between addressable (ie network 
> significant) access points by the concatenation of a sequence 
> of single link-connection (downstream only) significant identifiers.
> 
> So given this is even recognised in the draft now (and as one 
> reads through the draft it becomes increasingly clear that 
> the MPLS server layer case is being treated quite differently 
> to the IP server layer case), then why not go the extra step 
> and come clean by accepting that we don't have to force 
> XoverMPLS to be the same as XoverIP?  We could have a 
> nice/simple adaptation for carrying clients over arch 
> compliant MPLS now and really start to leverage the latent 
> potential of MPLS.
> 
> Can someone please explain to us why this can't this be done 
> (and please don't use mp2p and PHP as excuses....we know 
> these are broken arch flavours of MPLS, we just have to live 
> with these and move on....we should not keep making further 
> mistakes on the back of past mistakes)?
> 

Many of the procedures described in the document apply to both X-over-MPLS and X-over-IP. Some procedures depend on the specific type of PSN and are identified as such. 

I don't understand why it is so hard to grok that there is an advantage in trying to achieve as much commonality as possible between both modes, given that many network elements support both MPLS and IP.


> 
> 5	Can someone please explain to us why Y.1710 (which is 
> largely about principles/requirements) is at long last 
> recognised in this draft but Y.1711 is not recognised as a 
> valid OAM solution for MPLS?  This is especially puzzling for 
> us as Y.1711 is simple and complete (wrt defect and 
> availability specifications) and was written by an 
> operator.....so one might get the hint here that it was 
> something that we 'required' ;-)  It seems quite bizarre that 
> this is not included (even for completeness of reference), 
> especially noting this remark at the end of section 4.2.2:
> 
> "Based on these observations, it is clear that a Service 
> Provider has the disposal of a variety of tools. There are 
> many factors that influence which combination of tools best 
> meets its needs." 
> 
> Is there some specific technical (or other) reason why Y.1711 
> cannot be referenced?
> 

No technical reason. Since Y.1711 is controversial within the IETF, it was decided to leave it out of the current draft and ask  the mailing list for their opinion about the inclusion of Y.1711. That request went out a while ago and several people responded. I assume it is up to the WG Chairs to make the final decision.

> 
> 6	In section 4.4 it says:
> 
> "Besides reporting PW failures, PW status is used to 
> propagate AC failures. When and how to use those messages is 
> dependent on the emulated protocol and will be explained in 
> the subsequent paragraphs 5.3 and 6.3)."
> 
> This is generally incorrect.  If one respects the 
> client/server architectural requirements (in particular 
> client and server layer independence, and client layer 
> transparency) then a failure of a client layer network should 
> have no consequential impact on any server layer.  The above 
> statement is violating layer independence and it is therefore 
> not a good idea.  It's the same as asking a SDH network to 
> carry an ATM client (or any other client) layer's failure indications.
> 
> And what happens if the client and server layers are own by 
> different operating parties?  This is obviously a wrong 
> behaviour here.
> 
> Each layer network must be self-contained and in a 
> client/server relationship they must be independent.
> 

I agree. As you can verify, the behavior specified for PWE of ATM, SONET (CES)and TDM (SATOP) meets your requirements. However, what to do in case of Frame Relay? Frame Relay doesn't have a standard in-band way of conveying state information  from one NNI to another. In case a PW is used to connect two FR NNIs, it was decided to use the PW Status message to carry AC state information.

What do you propose? Should we eradicate Frame Relay from this world because it doesn't meet your client/server principles? :-)


>  
> 7	In section 4.7 it says:
> 
> "PWs can fail in a single direction or in both directions. 
> PEs SHOULD keep track of the status of each individual 
> direction. In other words, a PE SHOULD be able to distinguish 
> between the following states: "PW UP", "PW Transmit Direction 
> Down", "PW Receive Direction Down", "PW Receive and Transmit Down". 
>    
> The next two sections discuss under which conditions a PE 
> enters and exits these states. To avoid an unnecessarily 
> complicated description, only the states "PW UP" and "PW 
> DOWN" are discussed without further analysis whether it 
> applies to one or two directions of the PW."
> 
> Be careful here.  Performance metrics apply unidirectionally 
> and only to the available state.  However, for many 
> applications the failure of one direction effectively means 
> *both* directions must be considered as failed.  Thus even if 
> only a single direction fails (though to be accurate, this 
> actually means if one direction enters the unavailable state) 
> then the collection of performance metrics of *both* 
> directions should be suspended....at least wrt to their 
> meaning against any performance SLAs that are being measured. 
>  Have a read of Y.1711, as this explains what is required here.
> 
> 

Good point. The PW Status error codes distinguish between the PW being down in one direction and it being down in both directions. Therefore, the PEs need to maintain the states identified in the document. However, as far as availability  from an operator perspective is concerned, the PW should be considered down even if only one direciton is down. We can clarify that in the next draft.


> 8	In section 4.7.1 it says:
> 
> "Note that if the control session between the PEs fails, the 
> PW is torn down and needs to be re-established. As a 
> consequence, control session failure leads to disappearance 
> of the PW, not to a PW Down state." 
> 
> This should not be taken as a general requirement.  Failures 
> of control-plane components should not necessarily remove 
> data-plane trails that have been set-up.  This is 
> particularly true in the case of S-PVC-like constructs.
> 

I agree, but IMO this should be resolved in the Control Draft. The current version of the control draft refers to  RFC 3036 for the use of LDP to set up PWs. In my interpretation that means that a PW must be torn down if the LDP session fails. Graceful Restart for PWs could be added but would require specific text to that effect. Once it is in the Control Draft, we could update the OAM Message Mapping draft accordingly.


> 
> 9	Towards the end of section 5.2 FR 'port-mode' is 
> mentioned.  Similarly in section 6.2 wrt ATM 'transparent 
> mapping' it says:
> 
> "In case of transparent mapping, where the PE does not keep 
> track of the status of individual ATM VPCs or VCCs, it is 
> possible that a PE does not know which VPCs and/or VCCs are 
> active. In such a case there is a need for another fault 
> indication mechanism on the AC. This is beyond the scope of 
> this document."
> 
> 'Port-mode' has no meaning in functional architecture 
> terms.....and for a good reason as the extract above 
> demonstrates....and really ought not to be used for any client case.

I think there are situations in which the port mode makes sense and where proper behavior can be specified. It is, however, our of scope and I don't think we should use bandwidth on the mailing list to discuss that.


> 
> 
> .....so far.....regards, Neil
> 
> 
> 
>  
>  
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 19:34:51 +0200
Lines: 83
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Cc: "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)"
	 <pwe3@ietf.org>,
        "Orly Niklass (E-mail)" <orly_n@rad.com>,
        "Ron Cohen (E-mail)" <ronc@lyciumnetworks.com>
X-From: pwe3-admin@ietf.org Mon Mar 29 19:40:02 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Luca,
Please see some answers inline.
With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Monday, March 29, 2004 7:27 PM
> To: Sasha Vainshtein
> Cc: Mark Townsley (E-mail); PWE3 WG (E-mail)
> Subject: Re: Comments to draft-ietf-pwe3-iana-allocation-03
> 
> 
> 
> 
> Sasha Vainshtein wrote:
> 
> >Luca and Mark,
> >I have just read the newly posted draft-ietf-pwe3-iana-allocation-03.
> >Unfortunately, some issues raised at the Seoul meeting and later on 
> >this list wrt the TDM PWs have not been addressed:
> >
> >1. Renaming the CEP Payload Bytes interface parameter to 
> CEP/TDM Payload
> >Bytes
> >  
> >
> ok this will need to be updated in the 
> draft-ietf-pwe3-sonet-03.txt as well.
>
[Sasha] Ron, I hope this is OK with you.
> 
> >2. Allocation of a new interface parameter ID for TDM 
> options (could be
> >0x0b)
> >  
> >
> ok, but we need to find a location for the text in 
> draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt
>
> 
> I suggest that this text be included in it's  respective document.
> In te future when we might add new technologies we do not want to go 
> edit the original control protocol RFC every time.
>
[Sasha] OK with me. I'll resubmit the draft with all the necessary changes.
> 
> >3. Allocation of a new LDP status code - TDM 
> mis-configuration (could be
> >0x00000029).
> >
> >  
> >
> We only need one ? not the 6 that are defined in 
> draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt ?
>
[Sasha] I think that "just one" will be enough - just as it is enough for
SONET/SDH.
> 
> ( I added only this one. )
> 
> Luca
> ( I 'll send the update after I get your response. )
> 
> >Hopefully these issues can be easily addressed before the WG 
> Last Call.
> >With best regards,
> >                                   Sasha Vainshtein
> >email:     sasha@axerra.com
> >tel:       +972-3-7659993 (office)
> >           +972-8-9254948 (res.)
> >           +972-58-674833 (cell.)
> >
> >
> >  
> >
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 10:47:00 -0700
Organization: Cisco Systems
Lines: 68
Sender: pwe3-admin@ietf.org
References: <27A0F290348F8E45AEF79889DDE65A52024EA413@exrad2.ad.rad.co.il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Sasha Vainshtein <Sasha@AXERRA.com>,
        "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 29 19:50:04 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031020
X-Accept-Language: en-us, en
To: Orly Nicklass <orly_n@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52024EA413@exrad2.ad.rad.co.il>
X-PMX-Version: 4.1.1.86173
X-from-outside-Cisco-experimental-header: [10.32.224.186]
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Orly,

Thanks, I had already noticed.
Luca


Orly Nicklass wrote:

>It seems like there is also miscounting or typo err in the newly added
>PW types.
>First there are two "0x0011", then assuming we want those two, the text
>in section 2 should relate to dec values and not to hex values. (18 and
>19 in the text should be changed) See below.
>
>
>"....PW Type values 1 through 18
>   are defined in this document. PW Type values 19 through 63 are to be
>   assigned by IANA using the "IETF Consensus" policy defined in
>   RFC2434.
>...
>      0x0010   SONET/SDH Circuit Emulation over Packet (CEP)
>      0x0011   Structure-Agnostic TDM over Packet (SAToP)
>      0x0011   Structure-agnostic E1 over Packet (SAToP)
>      0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP)
>      0x0013   Structure-agnostic E3 over Packet (SAToP)
>      0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP)
>      0x0015   CESoPSN basic mode
>      0x0016   TDMoIP basic mode
>      0x0017   CESoPSN TDM with CAS
>      0x0018   TDMoIP TDM with CAS "
>
>-----Original Message-----
>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
>Sasha Vainshtein
>Sent: Sunday, March 28, 2004 12:46
>To: Luca Martini (E-mail); Mark Townsley (E-mail)
>Cc: PWE3 WG (E-mail)
>Subject: [PWE3] Comments to draft-ietf-pwe3-iana-allocation-03
>
>Luca and Mark,
>I have just read the newly posted draft-ietf-pwe3-iana-allocation-03.
>Unfortunately, some issues raised at the Seoul meeting and later on this
>list wrt the TDM PWs have not been addressed:
>
>1. Renaming the CEP Payload Bytes interface parameter to CEP/TDM Payload
>Bytes 2. Allocation of a new interface parameter ID for TDM options
>(could be
>0x0b)
>3. Allocation of a new LDP status code - TDM mis-configuration (could be
>0x00000029).
>
>Hopefully these issues can be easily addressed before the WG Last Call.
>With best regards,
>                                   Sasha Vainshtein
>email:     sasha@axerra.com
>tel:       +972-3-7659993 (office)
>           +972-8-9254948 (res.)
>           +972-58-674833 (cell.)
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>
>
>  
>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 15:49:49 -0700
Organization: Cisco Systems
Lines: 19
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1112@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>,
        "Orly Niklass (E-mail)" <orly_n@rad.com>,
        "Ron Cohen (E-mail)" <ronc@lyciumnetworks.com>
X-From: pwe3-admin@ietf.org Tue Mar 30 00:54:02 2004
Return-path: <pwe3-admin@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031020
X-Accept-Language: en-us, en
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1112@TLV1>
X-PMX-Version: 4.1.1.86173
X-from-outside-Cisco-experimental-header: [10.32.224.186]
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



>>>3. Allocation of a new LDP status code - TDM 
>>>      
>>>
>>mis-configuration (could be
>>    
>>
>>>0x00000029).
>>>
>>>      
>>>
>[Sasha] I think that "just one" will be enough - just as it is enough for
>SONET/SDH.
>
In this case can we use the existing code for CEP ?


Luca


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Mon, 29 Mar 2004 15:52:31 -0800
Lines: 15
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1112@TLV1>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: "'Mark Townsley \(E-mail\)'" <townsley@cisco.com>,
        "'PWE3 WG \(E-mail\)'" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 30 01:55:05 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>,
        "'Luca Martini'" <lmartini@cisco.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1112@TLV1>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi,

> > >1. Renaming the CEP Payload Bytes interface parameter to 
> > CEP/TDM Payload
> > >Bytes
> > >  
> > >
> > ok this will need to be updated in the 
> > draft-ietf-pwe3-sonet-03.txt as well.
> >
> [Sasha] Ron, I hope this is OK with you.

No problem. I will update the name in the coming CEP draft.

Ron


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Ashok Singh <singh_ashok_k@yahoo.com>
Subject: RE: VC TYPE 5 Support
Date: Mon, 29 Mar 2004 23:16:50 -0800 (PST)
Lines: 195
Sender: pwe3-admin@ietf.org
References: <200403291729.JAA14699@fargo.cisco.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1184839350-1080631010=:64647"
X-From: pwe3-admin@ietf.org Tue Mar 30 09:19:10 2004
Return-path: <pwe3-admin@ietf.org>
To: dbokotey@cisco.com, pwe3@ietf.org
In-Reply-To: <200403291729.JAA14699@fargo.cisco.com>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--0-1184839350-1080631010=:64647
Content-Type: text/plain; charset=us-ascii

Thank you for your response! It was my inference based on my initial understanding of the configuration and technical documentation on Ethernet over MPLS by CISCO (AToM),Juniper (Junos 6.0) and Riverstone, which as I now understand, was wrong.
 
Could you give me some pointers in the CISCO AToM (or any other) documents which discuss/mention Raw mode support? I got this idea of CISCO not supporting Raw mode because in all the AToM documents, while discussing Ethernet over MPLS, configuring VLAN using "encapsulation vlan dot1q xxx" has been mentioned as a necessary step. This, in my understanding, indicates that the received L2 packet processing at the PE will be based on the (Service Delimitting) VLAN Tag (or in other words, only VC TYPE: Ethernet VLAN support). I could not find documents talking about the VC TYPE 4 support or port based L2 FEC support for that matter, in CISCO AToM documents.
 
About Juniper (Junos 6.0),  the case that I was talking about is that apart from "encapsulation vlan-ccc" for configuring a PE interface, it also has "encapsulation ethernet-ccc" option where it must be using Raw mode and supporting port based L2 FEC (the interface has not been configured as a VLAN interface). Reference for this is 
http://www.juniper.net/techpubs/software/junos/junos60/feature-guide-60/download/fg-l2circuit.pdf, (page 6)
 
Do help me in case I am lacking in my understanding of the concepts or am wrong anywhere. 
 
Regards,


Dmitry Bokotey <dbokotey@cisco.com> wrote:v\:* {behavior:url(#default#VML);}o\:* {behavior:url(#default#VML);}w\:* {behavior:url(#default#VML);}.shape {behavior:url(#default#VML);}
Where did you get this information only Juniper supports VC TYPE 5

Cisco does support vc-type 5 port transparency.

 

 

---------------------------------


From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of Ashok Singh
Sent: Monday, March 29, 2004 12:35 AM
To: pwe3@ietf.org
Subject: [PWE3] VC TYPE 5 Support


 

Hello All,


 


I want to know if there are products in market that support VC TYPE 5 as mentioned in the pwe3 drafts. 


My initial understanding seems to indicate that: 


 


CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM documents)


 


Riverstone also does not support VC TYPE 5 but achieves this (Port based L2 FEC support)  by using VC TYPE 4 (Ethernet VLAN) only, requiring hybrid port/trunk port/access port vlan configuration.


 


Only Juniper seems to have support for VC TYPE 5, as mentioned in the requirements (configuring Ethernet ccc) in its configuration documents.


 


Any comments from the group? Does it imply that purpose of VC TYPE 5 can even be achieved with VC TYPE 4 as done by some vendors? Please correct me if I am going wrong anywhere.


 


Regards,



---------------------------------


Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.




---------------------------------
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
--0-1184839350-1080631010=:64647
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>Thank you for your response! It was my inference based on my initial understanding of the configuration and technical documentation on Ethernet over MPLS&nbsp;by CISCO (AToM),Juniper (Junos 6.0)&nbsp;and Riverstone, which as I now understand, was wrong.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Could you give me some pointers in the CISCO AToM (or any other) documents which discuss/mention Raw mode support? I got this idea of CISCO not supporting Raw mode&nbsp;because in all the AToM documents, while discussing Ethernet over MPLS, configuring VLAN using "encapsulation vlan dot1q xxx" has been mentioned as a necessary step. This, in my understanding, indicates that the received L2 packet processing at the PE will be based on the (Service Delimitting) VLAN Tag (or in other words, only VC TYPE: Ethernet VLAN support). I could not find documents talking about the VC TYPE 4 support or port based L2 FEC support for that matter, in CISCO AToM documents.</DIV>
<DIV>&nbsp;</DIV>
<DIV>About Juniper (Junos 6.0),&nbsp;&nbsp;the case that I was talking about is that&nbsp;apart from "encapsulation vlan-ccc" for configuring a PE&nbsp;interface, it&nbsp;also has "encapsulation ethernet-ccc" option where it&nbsp;must be&nbsp;using Raw mode and supporting port based L2 FEC (the interface has not been configured as a VLAN interface). Reference for this is <BR><A href="http://www.juniper.net/techpubs/software/junos/junos60/feature-guide-60/download/fg-l2circuit.pdf"><FONT color=#800080>http://www.juniper.net/techpubs/software/junos/junos60/feature-guide-60/download/fg-l2circuit.pdf</FONT></A>, (page 6)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Do help me in case I am lacking in my understanding of the concepts or am wrong anywhere. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Regards,</DIV><BR><BR><B><I>Dmitry Bokotey &lt;dbokotey@cisco.com&gt;</I></B> wrote:
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<META content="Microsoft Word 11 (filtered medium)" name=Generator>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>

<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>

<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Where did you get this information only Juniper supports </SPAN></FONT>VC TYPE 5<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Cisco does support vc-type 5 port transparency.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] <B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Ashok Singh<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, March 29, 2004 12:35 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> pwe3@ietf.org<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> [PWE3] VC TYPE 5 Support</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Hello All,<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">I want to know if there are products in market that support VC TYPE&nbsp;5 as mentioned in the pwe3 drafts. <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">My initial understanding seems to indicate that: <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM documents)<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Riverstone also does not support VC TYPE&nbsp;5 but achieves this (Port based L2 FEC support)&nbsp; by using VC TYPE&nbsp;4 (Ethernet VLAN) only, requiring hybrid port/trunk port/access port&nbsp;vlan configuration.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Only Juniper seems to have&nbsp;support for VC TYPE 5, as mentioned in the requirements (configuring Ethernet ccc) in its configuration documents.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Any comments from the group? Does it imply that purpose of&nbsp;VC TYPE 5 can even be&nbsp;achieved with VC TYPE 4 as done by some vendors? Please correct me if I am going wrong anywhere.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">Regards,<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR align=center width="100%" SIZE=1>
</SPAN></FONT></DIV>
<P class=MsoNormal><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Do you Yahoo!?<BR><A href="http://taxes.yahoo.com/filing.html"><B><SPAN style="FONT-WEIGHT: bold">Yahoo! Finance Tax Center</SPAN></B></A> - File online. File on time.</SPAN></FONT><o:p></o:p></P></DIV></BLOCKQUOTE></DIV><p><hr size=1><font face=arial size=-1>Do you Yahoo!?<br>
<a href="http://taxes.yahoo.com/filing.html"><b>Yahoo! Finance Tax Center</a></b> - File online. File on time.
--0-1184839350-1080631010=:64647--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Dmitry Bokotey" <dbokotey@cisco.com>
Subject: RE: VC TYPE 5 Support
Date: Tue, 30 Mar 2004 01:40:36 -0800
Organization: Cisco Systems, Inc
Lines: 644
Sender: pwe3-admin@ietf.org
References: <20040330071650.64726.qmail@web80808.mail.yahoo.com>
Reply-To: <dbokotey@cisco.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0009_01C415F8.008F23B0"
X-From: pwe3-admin@ietf.org Tue Mar 30 09:44:07 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Ashok Singh'" <singh_ashok_k@yahoo.com>, <pwe3@ietf.org>
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <20040330071650.64726.qmail@web80808.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcQWJv1zhgiAdVZFSTmxaYzj1zlexQAE6+lQ
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multi-part message in MIME format.

------=_NextPart_000_0009_01C415F8.008F23B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Ashok check this links out, hope this will make more sense to you.

http://www.cisco.com/en/US/products/hw/optical/ps2006/products_module_config
uration_guide_chapter09186a00801ea619.html

http://www.cisco.com/univercd/cc/td/doc/product/ong/15400/r46docs/r46mlios/e
ompls.htm#18213

http://www.cisco.com/global/CN/learning/training/citgq3/pdf/5-atom.pdf

 

 

Dmitry Bokotey

 

  _____  

From: Ashok Singh [mailto:singh_ashok_k@yahoo.com] 
Sent: Monday, March 29, 2004 11:17 PM
To: dbokotey@cisco.com; pwe3@ietf.org
Subject: RE: [PWE3] VC TYPE 5 Support

 

Thank you for your response! It was my inference based on my initial
understanding of the configuration and technical documentation on Ethernet
over MPLS by CISCO (AToM),Juniper (Junos 6.0) and Riverstone, which as I now
understand, was wrong.

 

Could you give me some pointers in the CISCO AToM (or any other) documents
which discuss/mention Raw mode support? I got this idea of CISCO not
supporting Raw mode because in all the AToM documents, while discussing
Ethernet over MPLS, configuring VLAN using "encapsulation vlan dot1q xxx"
has been mentioned as a necessary step. This, in my understanding, indicates
that the received L2 packet processing at the PE will be based on the
(Service Delimitting) VLAN Tag (or in other words, only VC TYPE: Ethernet
VLAN support). I could not find documents talking about the VC TYPE 4
support or port based L2 FEC support for that matter, in CISCO AToM
documents.

 

About Juniper (Junos 6.0),  the case that I was talking about is that apart
from "encapsulation vlan-ccc" for configuring a PE interface, it also has
"encapsulation ethernet-ccc" option where it must be using Raw mode and
supporting port based L2 FEC (the interface has not been configured as a
VLAN interface). Reference for this is 
 
<http://www.juniper.net/techpubs/software/junos/junos60/feature-guide-60/dow
nload/fg-l2circuit.pdf>
http://www.juniper.net/techpubs/software/junos/junos60/feature-guide-60/down
load/fg-l2circuit.pdf, (page 6)

 

Do help me in case I am lacking in my understanding of the concepts or am
wrong anywhere. 

 

Regards,



Dmitry Bokotey <dbokotey@cisco.com> wrote: 

Where did you get this information only Juniper supports VC TYPE 5

Cisco does support vc-type 5 port transparency.

 

 

  _____  

From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of Ashok
Singh
Sent: Monday, March 29, 2004 12:35 AM
To: pwe3@ietf.org
Subject: [PWE3] VC TYPE 5 Support

 

Hello All,

 

I want to know if there are products in market that support VC TYPE 5 as
mentioned in the pwe3 drafts. 

My initial understanding seems to indicate that: 

 

CISCO's AToM does not support VC TYPE 5 (apparent from the recent AToM
documents)

 

Riverstone also does not support VC TYPE 5 but achieves this (Port based L2
FEC support)  by using VC TYPE 4 (Ethernet VLAN) only, requiring hybrid
port/trunk port/access port vlan configuration.

 

Only Juniper seems to have support for VC TYPE 5, as mentioned in the
requirements (configuring Ethernet ccc) in its configuration documents.

 

Any comments from the group? Does it imply that purpose of VC TYPE 5 can
even be achieved with VC TYPE 4 as done by some vendors? Please correct me
if I am going wrong anywhere.

 

Regards,

  _____  

Do you Yahoo!?
 <http://taxes.yahoo.com/filing.html> Yahoo! Finance Tax Center - File
online. File on time.

  _____  

Do you Yahoo!?
 <http://taxes.yahoo.com/filing.html> Yahoo! Finance Tax Center - File
online. File on time.


------=_NextPart_000_0009_01C415F8.008F23B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.SHAPE
	{behavior:url(#default#VML);}

 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Ashok check this links out, hope =
this will
make more sense to you.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><a
href=3D"http://www.cisco.com/en/US/products/hw/optical/ps2006/products_mo=
dule_configuration_guide_chapter09186a00801ea619.html">http://www.cisco.c=
om/en/US/products/hw/optical/ps2006/products_module_configuration_guide_c=
hapter09186a00801ea619.html</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><a
href=3D"http://www.cisco.com/univercd/cc/td/doc/product/ong/15400/r46docs=
/r46mlios/eompls.htm#18213">http://www.cisco.com/univercd/cc/td/doc/produ=
ct/ong/15400/r46docs/r46mlios/eompls.htm#18213</a><o:p></o:p></span></fon=
t></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><a
href=3D"http://www.cisco.com/global/CN/learning/training/citgq3/pdf/5-ato=
m.pdf">http://www.cisco.com/global/CN/learning/training/citgq3/pdf/5-atom=
.pdf</a><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Dmitry =
Bokotey<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ashok =
Singh
[mailto:singh_ashok_k@yahoo.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, =
2004 11:17
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> dbokotey@cisco.com;
pwe3@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [PWE3] VC =
TYPE 5
Support</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thank you for your response! It was my inference based on my =
initial
understanding of the configuration and technical documentation on =
Ethernet over
MPLS&nbsp;by CISCO (AToM),Juniper (Junos 6.0)&nbsp;and Riverstone, which =
as I
now understand, was wrong.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Could you give me some pointers in the CISCO AToM (or any other)
documents which discuss/mention Raw mode support? I got this idea of =
CISCO not
supporting Raw mode&nbsp;because in all the AToM documents, while =
discussing
Ethernet over MPLS, configuring VLAN using &quot;encapsulation vlan =
dot1q
xxx&quot; has been mentioned as a necessary step. This, in my =
understanding,
indicates that the received L2 packet processing at the PE will be based =
on the
(Service Delimitting) VLAN Tag (or in other words, only VC TYPE: =
Ethernet VLAN
support). I could not find documents talking about the VC TYPE 4 support =
or
port based L2 FEC support for that matter, in CISCO AToM =
documents.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>About Juniper (Junos 6.0),&nbsp;&nbsp;the case that I was =
talking about
is that&nbsp;apart from &quot;encapsulation vlan-ccc&quot; for =
configuring a
PE&nbsp;interface, it&nbsp;also has &quot;encapsulation =
ethernet-ccc&quot;
option where it&nbsp;must be&nbsp;using Raw mode and supporting port =
based L2
FEC (the interface has not been configured as a VLAN interface). =
Reference for
this is <br>
<a
href=3D"http://www.juniper.net/techpubs/software/junos/junos60/feature-gu=
ide-60/download/fg-l2circuit.pdf"><font
color=3Dpurple><span =
style=3D'color:purple'>http://www.juniper.net/techpubs/software/junos/jun=
os60/feature-guide-60/download/fg-l2circuit.pdf</span></font></a>,
(page 6)<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Do help me in case I am lacking in my understanding of the =
concepts or
am wrong anywhere. <o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Regards,<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br>
<b><i><span style=3D'font-weight:bold;font-style:italic'>Dmitry Bokotey
&lt;dbokotey@cisco.com&gt;</span></i></b> wrote: =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Where did you get this information =
only
Juniper supports </span></font>VC TYPE 5<o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Cisco does support vc-type 5 port =
transparency.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Ashok Singh<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Monday, March 29, =
2004 12:35
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pwe3@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [PWE3] VC TYPE 5 =
Support</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hello All,<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I want to know if there are products in market that support VC
TYPE&nbsp;5 as mentioned in the pwe3 drafts. =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>My initial understanding seems to indicate that: =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>CISCO's AToM does not support VC TYPE 5 (apparent from the =
recent AToM
documents)<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Riverstone also does not support VC TYPE&nbsp;5 but achieves =
this (Port
based L2 FEC support)&nbsp; by using VC TYPE&nbsp;4 (Ethernet VLAN) =
only,
requiring hybrid port/trunk port/access port&nbsp;vlan =
configuration.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Only Juniper seems to have&nbsp;support for VC TYPE 5, as =
mentioned in
the requirements (configuring Ethernet ccc) in its configuration =
documents.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Any comments from the group? Does it imply that purpose =
of&nbsp;VC TYPE
5 can even be&nbsp;achieved with VC TYPE 4 as done by some vendors? =
Please
correct me if I am going wrong anywhere.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Regards,<o:p></o:p></span></font></p>

</div>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do you Yahoo!?<br>
<a href=3D"http://taxes.yahoo.com/filing.html"><b><span =
style=3D'font-weight:bold'>Yahoo!
Finance Tax Center</span></b></a> - File online. File on =
time.</span></font><o:p></o:p></p>

</div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D1 width=3D"100%" align=3Dcenter>

</span></font></div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Do you Yahoo!?<br>
<a href=3D"http://taxes.yahoo.com/filing.html"><b><span =
style=3D'font-weight:bold'>Yahoo!
Finance Tax Center</span></b></a> - File online. File on =
time.</span></font><o:p></o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0009_01C415F8.008F23B0--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: PW Availability
Date: Tue, 30 Mar 2004 11:45:49 +0100
Lines: 340
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Tue Mar 30 12:52:14 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: PW Availability
Thread-Index: AcQSqrcYCLK6fZE/RnqXqZyH28RuzwAX3gmA
To: <busschbach@lucent.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 30 Mar 2004 10:45:50.0176 (UTC) FILETIME=[2A9D5E00:01C41644]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Thanks Peter.....I have some responses for you in-line....sorry for the =
delay.  regards, Neil

> -----Original Message-----
> From: Busschbach, Peter B (Peter) [mailto:busschbach@lucent.com]
> Sent: 25 March 2004 20:49
> To: Harrison,N,Neil,IKR2 R; pwe3@ietf.org
> Subject: RE: PW Availability
>=20
>=20
> Neil,
>=20
> I would be happy to add to=20
> draft-nadeau-pwe3-oam-msg-map-04.txt that a PW is declared=20
> unavailable if a defect persists for more than 10 seconds.=20
> However, at this point I am not sure what that means since I=20
> don't know how it affects anything that goes on in the network.
NH=3D> OK.  But please note: =20
-	you will have seen my explanation of the origins of the definition of =
availability and how I think it should be simplified, re how Y.1711 has =
addressed this.
-	there is need to aim for harmonisation of NP/availability metrics and =
objectives across all layer networks.......this becomes even more =
obvious as a requirement if there is no control over client/server layer =
relationships (though as I have noted before some C/S relationships =
between the 3 modes make far more sense than others)
-	both availability and NP aspects can be sensibly associated with =
trails.  Only co-cs and co-ps modes have trails.  So for MPLS these =
metrics need to be associated with an LSP.  Sure you can try and =
associate them with a PW but we don't network PWs, ie we do not switch, =
nest as client/server, etc PWs since they are an adaptation function.  I =
know most folks seem to struggle to grasp this but it is/will be a real =
limiting problem for MPLS....that is, a PW lives in no-mans land between =
a given client (eg FR, ATM etc) and either a cl-ps IP server layer or a =
co-ps MPLS server layer.  I am really puzzled however why folks find =
this hard to understand technically?
>=20
> You have mentioned that it is important to recognize such a=20
> state, because it determines when Performance Monitoring=20
> should be started and stopped. However, from your response to=20
> my last email, it appears that a clear and realistic approach=20
> to Performance Monitoring does not exist yet. Therefore, I=20
> wonder what the point is of introducing concepts that may or=20
> may not be relevant in the future.
NH=3D> This is not a logical argument.  If you don't get the ordering =
right then yes for sure you have a self-fulfilling prophecy that that =
there is no chance to get the NP aspects sorted.  However, if you do get =
the ordering right then when you are ready to measure NP you have the =
right basis.  NP is 2nd order in importance to defect =
detection/handling.  We have not discussed NP issues yet. You can also =
easily end up specifying way too many complex/unnecessary NP stuff that, =
in terms of its real benefit in a network, is an illusion of efficiency. =
 The 'QoS challenges' are not about having loads of classes in 1 mode, =
but they are all about how to deliver a suite of public/private services =
that are consistently meaningful across a large range of network load =
points, and thus allow SPs the ability to charge a fair price for doing =
so.  Real networks run lightly loaded for most of their working life =
(for lots of reasons).  Having lots of QoS classes won't help you with =
this goal if:
-	you can't differentiate 'urgency' and 'importance'......and this is =
one reason why there is a big difference between having the co-ps mode =
trail (eg LSP) or only the cl-ps mode pkt (eg IP) as the networked =
entity;
-	resource sharing is allowed between traffic classes....since this =
kills any sensible notion of 'QoS differentiation' dead.
>=20
> Therefore, I propose that we add the following statements to=20
> draft-nadeau-pwe3-oam-msg-map-04.txt:
>=20
> a) in general (i.e. for other technologies), operators=20
> consider a connection unavailable of a defect persists for=20
> more than 10 seconds
>=20
> b) the interaction between PW fault management and=20
> Performance Monitoring is for further study.
NH=3D> OK, seems this group is hell-bent of defining all the networking =
stuff round PWs rather than the LSP and pkt networked entities of the =
co-ps and cl-ps modes respectively.  Its wrong of course, but I alone =
can't stop you.  Some further remarks below. =20
>=20
> Further comments in-line.
>=20
> Peter
>=20
> > -----Original Message-----
> > From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]
> > Sent: Wednesday, March 24, 2004 5:53 PM
> > To: busschbach@lucent.com; pwe3@ietf.org
> > Subject: RE: PW Availability
> >=20
> >=20
> > Peter..
> > >=20
> > > Neil,
> > >=20
> > > A while ago we exchanged emails on the availability of Pseudo=20
> > > Wires. The relevant part is attached to this email.
> > >=20
> > > I agree with the observations you made, but my main question=20
> > > was not answered: if you emulate a service over PWs,
> > NH=3D> Can you define precisely what 'emulate' means here?
> >=20
>=20
> I meant "emulate" in the same way as it is used in all WG=20
> drafts and emails on this mailing list: the encapsulation of=20
> client traffic so as to transport it over a PSN.
NH=3D> Oh yes I know, that is why I asked you to flush this point out.  =
Its imprecise, and is thus a meaningless statement.  This is not a good =
starting point for operators who regard MPLS as a key core target =
technology.  I think its high time folks stopped pretending MPLS is the =
same as IP....its wrecking the potential of MPLS IMO.  XoverMPLS is not =
the same thing as XoverIP.  We can manage trails in a co-ps mode like =
MPLS, we cannot do that in a cl-ps mode like IP.  That is simply a fact =
which, for whatever reason, some folks here seem unable (or more likely =
'unwilling') to comprehend/accept.  Speaking as an engineer who has been =
brought-up to believe in honesty and accuracy, I find this 'sticking =
one's head in the sand' behaviour of ignoring the truth rather =
disturbing. {Note - this is not the same as saying I won't accept =
compromises....I have no problem with that *providing* they are =
recognised as such (eg arch violations) and we understand the =
implications of them.  I only have problems when folks tell me they are =
'right' and won't even recognise identified problems.} =20
>=20
> > > is it=20
> > > really necessary to measure Network Performance (NP) of the=20
> > > PW itself?
> > NH=3D> Pass.  Depends on what the definition of 'emulation'=20
> > really meens (and I have no idea) and what a PW actually=20
> > is....to me its some form of adaptation.  XoverIP could have=20
> > different perf to XoverMPLS....the defect behaviour is for=20
> > sure very different.  I think folks really ought to=20
> > differentiate these 2 cases as they are obviously not the same.
>=20
> I may be naive, but I would think that Network Performance to=20
> the extend that it relates to SLAs should be independent of=20
> the network layers over which the service is carried.
NH=3D> The whole point of my repeated observations about the 3 =
networking modes and client/server inheritance is to show this is not =
true.  The behaviour of a cl-ps mode network is different to a that of a =
co-ps mode network is different to that of a co-cs mode network.  One =
introduces constraints to the basic 'broadcast at source, filter at =
sink' mode (that ethernet uses) to get these 3 wide-area modes.....and =
one does this because they bring benefits in =
scaling/design/operation/NP/mtce/etc....in other words the network =
becomes simpler as we move towards the co-cs mode.  If not obvious, =
consider the fact that the co-cs mode has *no* traffic/QoS classes at =
all.....and just think how much simpler =
routing/signalling/resource-accounting/fault-management/etc is =
therefore.  So if a co-cs mode is the server layer then the client layer =
cannot get any better *inherited* NP than this.....remember, each layer =
network will inherit the NP of its server layer and this is recursive to =
the duct.  There are 9 combinations of client/server relationships =
between the 3 modes.....some make more sense than others.  We cannot be =
prescriptive about this (and currently there are no stds that describe =
this or control how many times one is allowed to go up/down a network =
stack of different modes)....however we can use common sense ;-)
>=20
> In fact, you assertion that defect behavior of IP and MPLS=20
> networks is so different that XoverIP and XoverMPLS should be=20
> considered as two totally different solutions suggests that=20
> NP measurements of X would yield completely different results=20
> in the two cases. I can't see why that would be desirable to=20
> Service Providers.
NH=3D> Can't you?  Blimey that is of concern then.  As a hint go check =
real core network utilisations, esp when one has uncertainty of =
behaviour under failure.  But let me try and help further:  In a cl-ps =
network you only have one traffic entity.....the pkt.  In a co-ps =
network you have 2 traffic entities.....the parent trail and the child =
pkt.  The trail is the dominant entity here.  One can therefore provide =
additional constraints to the co-ps mode that don't exist in the cl-ps =
mode, eg you can explicitly control the directivity by signalling, and =
the survivability of the parent trail entity can be completely decoupled =
from the (child pkt) traffic it carries.....a rather important feature =
IMO, esp for VPNs (noting that this can be generalised to include all =
client/server cases since these are, if you think about it, a form of =
'VPN').  Now if you really wanted to see the power the co-ps mode can =
unlock for you I would need to get into a discussion of what QoS/NP =
really means....but that is another long story however.

But hang on a minute......this should all be obvious to network =
engineers.  This is starting to feel like I am giving some lecture on =
networking basics.
> =20
> >=20
> > > If a Service Provider measures NP on end-to-end=20
> > > ATM VCs, why is it necessary to obtain additional NP=20
> > > measurements on one specific segment?
> > NH=3D> To see where impairments are coming from say.  In a more=20
> > general case if you have some global reference connection=20
> > with metrics A, B, C that have objectives a, b, c (to be met=20
> > over some period, eg month), you need some way to fairly=20
> > apportion these to  partitions of the end-end path, eg to=20
> > countries or operator domains.  So each partition need to=20
> > check its bit is within its apportioned target.
> > >=20
> > > Now, assuming that a Service Provider wants to measure NP of=20
> > > PWs, how does that work?
> > NH=3D> I have no idea....you are starting down the very=20
> > slippery slope of making a PW a networked entity....and it is=20
> > not (as yet anyway).
>=20
> I am  not sure who started down the slippery slope.
NH=3D> I'll tell you then.  It was those folks who wanted to 'do' stuff =
like FR and ATM without deploying native technologies.  Quite =
understandable.  However, its one thing doing a cheap/cheerful expedient =
technology emulation (over either IP or MPLS), but its quite another =
thing to then say PWs are the basis of next gen networks for everybody.  =
AFAI can tell, the direction here is network convergence on =
PWs.......but I think most operators want a convergence on MPLS.  But =
PWs are not even a layer network, and the real layer networks of IP and =
MPLS are not the same.....if there were the same then why did MPLS come =
into being in the first place?  Every time I make this observation folks =
ignore it....I assume because its something some would rather was not =
recognised (though these same folks don't seem to have a problem =
recognising that SDH and OTNs are co-cs mode networks when talking about =
GMPLS....there are some very strange double-stds being applied here =
IMO).  This attitude is not healthy IMO.  Its not allowing the full =
potential of MPLS to be seen/developed, and IMO its also an attempt to =
hide (or maybe justify) some arch violations of MPLS IMO.  Now I know =
there are religious/commercial factors at play here, but I am trying to =
be brutally honest about 'networking truths'.....I used to think that =
'technical honesty/accuracy' was something that was held in high esteem =
in IETF, but I have had to change my views on that.


> I did not=20
> say there was a need for an availability state for PWs. You=20
> did.
NH=3D> Yes, but it is now a logical conclusion of what has been done =
here.  A PW is now a unifying adaptation function above either an IP =
server layer network or an MPLS server layer network.....but it does not =
exist in its own right as a layer network interface.....you still have =
FR, ATM, or whatever above this.  We do not (as yet anyway) 'network' =
PWs but we do network IP pkts and MPLS trails.....and pkts and trails =
are quite different network entities.  However, given the status of this =
discussion I fear you either honestly don't get this (which I find hard =
to believe in your case) or you are unwilling to recognise it for some =
other reason.

>I am actually arguing for the position that it doesn't=20
> make sense to measure NP for Pseudo Wires.
NH=3D> Good, that is something we agree on then.  I am actually arguing =
for an acceptance by the community that there are 3 networks modes.  SDH =
and OTNs belong to the co-cs mode.  IP and ethernet belongs to the cl-ps =
mode (though only IP has proper addressing/routing).  MPLS, ATM and FR =
belong to the co-ps mode.  These modes have fundamentally different =
behaviours....that is why they were created in the first place for =
goodness sake.  These are simply facts....pretending they are not true =
is not helping anyone in the long-term.  Now given your statement above, =
I therefore have to assume that you also agree that the NP needs to be =
associated with the real network then....so that is either IP or MPLS.  =
I want to associate *all* the networked attributes (ie defects, =
availability, NP) with the LSP in MPLS as its this that is the networked =
entity.  One manages trails in a co-ps mode network quite differently to =
how one manages pkts in a cl-ps mode network.  =20
>=20
> >=20
> > > I assume that it is based on=20
> > > comparing packet counts both at ingress and egress. Following=20
> > > the method proposed by Y.1711, performance measurements are=20
> > > stopped upon detection of a defect and restarted a certain=20
> > > period after the defects disappears and the connection is=20
> > > stable again. However, in general a defect exists some time=20
> > > before a connection end-point finds out. Therefore, a number=20
> > > of packets will have been dropped already. Rather than trying=20
> > > to minimize the effect of this time lag by specifying=20
> > > available/unavailable state, as Y.1711 does, would it not=20
> > > make more sense to sanitize the data in an off-line=20
> > > performance monitoring tool that can exclude counts taken=20
> > > just before the defect occurred?
> > NH=3D> Y.1711 has not defined any NP collection yet.  Its more=20
> > important to get the basic defects, short-breaks and=20
> > unavailability bits done 1st.  NP stuff can be added later on=20
> > this firm defect detection/handling basis.  I can think of=20
> > some smart/simple ways of doing NP collection however.....the=20
> > details are not given in Y.1711 right now. One also has to be=20
> > aware of 'PDUs in flight'. =20
> > >=20
> > > In short: how exactly do Service Prodivers measure Network=20
> > > Performance?
> > NH=3D> Badly to date is my view.  Why?  Because the ordering I=20
> > mentioned in the mail below has never properly been executed=20
> > in the past.
>=20
> I am not sure what point you are trying to make. Service=20
> Providers (BT being one of them) have large networks in which=20
> they run ATM over SDH or SONET. I was not asking a rhetorical=20
> question. I am genuinely interested to learn more about=20
> operator experiences.
NH=3D> And the answer I gave is correct.  We really do not do a good =
job, because whilst I.610 may look superficially OK, there are several =
problems with it....and they started because folks initially focussed on =
NP/QoS and forgot about the more basic defect detection/handling first.  =
I can explain but its yet another long story.
>=20
> However, if you say that even ATM-over-SDH
> is such a mess=20
NH=3D> No, SDH is fine.  Its ATM's OAM that is not good in some =
respects.  The problem with ATM was that folks got far too interested =
with NP metrics and defining lots of traffic classes (we had 5 AALs at =
one stage).....a complexity that we can now see was largely =
unnecessary....and they forgot about attending to the less sexy basic =
stuff, like defining defects and their detection/handling.  So ATM's OAM =
is far from ideal.  I can explain why if you are really interested.

> that decent Performance Monitoring is not possible, then what=20
> does that mean for our current work?
NH=3D> Which current work?  Y.1711 is fine.  It corrects the problems in =
I.610.

> Existing networks will=20
> not go away for a long time to come.
NH=3D> Agreed.  That is why if we continue to screw things up by not =
facing up to network arch truths early its us operators who will be left =
paying for it for many years hence.  This is why I will not let folks =
off the hook who continue to violate func arch rules just because it =
might suit them right now in selling boxes.

> We have to work with=20
> what we have. Especially with regards to PWE, I don't see how=20
> we can work on Performance Monitoring without taking existing=20
> protocols and techniques into account.
NH=3D> I would understand if you you were talking about going back and =
trying to redo FR and ATM say. But one should not be specifying stuff in =
stds that are still draft and known to be flawed.  We and other =
operators have not yet built our next generation networks, ie a =
converged core on MPLS.  PWs are not a common deployed legacy =
technology.  MPLS is only used today in niche applications.  We are very =
concerned about the arch flaws in some types of MPLS and its missing =
functional components.  Similarly, we are also concerned about PWs that =
are then based on these.  We therefore do not regard these technologies =
as legacy in the same way as FR or ATM.  MPLS is currently not fit for =
purpose as a future key convergence technology.  You appear to be =
insisting here that because someone has made some errors in the past =
with some types of MPLS that these must be visited on all future work =
and imposed on all operators....why?  We have the chance to correct =
these.  Why is it not possible to get the stds right now based on =
respecting the func arch requirements?

regards Neil=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: CAITR <info@caitr.org>
Subject: Internetworking 2004: May 13-14, 2004, Las Vegas
Date: Tue, 30 Mar 2004 08:28:45 -0800 (PST)
Lines: 97
Sender: pwe3-admin@ietf.org
Reply-To: info@caitr.org
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1837819455-1080664125=:20662"
X-From: pwe3-admin@ietf.org Tue Mar 30 18:31:13 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

--0-1837819455-1080664125=:20662
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA27287

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Internetworking 2004=20
May 13-14, 2004
Las Vegas Convention Center, Las Vegas, Nevada
http://www.caitr.org/internetworking04/index.htm
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
Internetworking 2004, for the first time collocated with NetWorld+Interop=
, aims to address some of the main issues of concern within IP networking=
 and the Internet. This exclusive leading-edge technology program covers =
innovative solutions for Enterprises, Service Providers, networking equip=
ment manufacturers, government and others.=20
=20
The Internetworking 2004 conference, comprised of comprehensive technical=
 sessions, panels, and case studies for real operational networks, is int=
ended as a forum for technical discussions on topics including:=20
=20
=95 Voice over IP (VoIP) and Convergence
=95 Multiservice Network Design and Planning
=95 Virtual Private Networks (VPNs)
=95 Routing: Unicast & Multicast=20
=95 Wireless Internet=20
=95 Next Generation Mobile Networks=20
=95 Quality of Service (QoS)
=95 Network Security=20
=95 Network Processors=20
=95 Service Integration=20
=95 Operational Support Systems=20
=95 Network Survivability and Fault Management=20
=95 Internetworking IP and Optical Networks=20

***EXCLUSIVE ALUMNI DISCOUNT***
We are pleased to extend a special alumni discount for the 2-day Internet=
working 2004 Pass. Purchase the pass for $595.00, a $500.00 savings off t=
he regular price. Visit <http://www.caitr.org/internetworking04/registrat=
ion.htm> for Priority Code and registration details.=20

We look forward to seeing you at the only end-to-end networking and commu=
nications event.
=20
Sincerely,
The NetWorld+Interop Team
http://www.interop.com/


--0-1837819455-1080664125=:20662
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA27287

<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
/DIV>
<DIV>Internetworking 2004 <BR>May 13-14, 2004<BR>Las Vegas Convention Cen=
ter, Las Vegas, Nevada<BR><A href=3D"http://www.caitr.org/internetworking=
04/index.htm">http://www.caitr.org/internetworking04/index.htm</A></DIV>
<DIV>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>Internetworking 2004, for the first time collocated with NetWorld+In=
terop, aims to address some of the main issues of concern within IP netwo=
rking and the Internet. This exclusive leading-edge technology program co=
vers innovative solutions for Enterprises, Service Providers, networking =
equipment manufacturers, government and others. </DIV>
<DIV>&nbsp;</DIV>
<DIV>The Internetworking 2004 conference, comprised of comprehensive tech=
nical sessions, panels, and case studies for real operational networks, i=
s intended as a forum for technical discussions on topics including: </DI=
V>
<DIV>&nbsp;</DIV>
<DIV>=95 Voice over IP (VoIP) and Convergence<BR>=95 Multiservice Network=
 Design and Planning<BR>=95 Virtual Private Networks (VPNs)<BR>=95 Routin=
g: Unicast &amp; Multicast <BR>=95 Wireless Internet <BR>=95 Next Generat=
ion Mobile Networks <BR>=95 Quality of Service (QoS)<BR>=95 Network Secur=
ity <BR>=95 Network Processors <BR>=95 Service Integration <BR>=95 Operat=
ional Support Systems <BR>=95 Network Survivability and Fault Management =
<BR>=95 Internetworking IP and Optical Networks <BR></DIV>
<DIV>***EXCLUSIVE ALUMNI DISCOUNT***<BR>We are&nbsp;pleased to extend a s=
pecial alumni discount for the 2-day Internetworking 2004 Pass. Purchase =
the pass for $595.00,&nbsp;a $500.00 savings off the regular price. Visit=
 &lt;<A href=3D"http://www.caitr.org/internetworking04/registration.htm">=
http://www.caitr.org/internetworking04/registration.htm</A>&gt; for Prior=
ity Code and registration details. </DIV>
<DIV><BR>We look forward to seeing you at the only end-to-end networking =
and communications event.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Sincerely,<BR>The NetWorld+Interop Team<BR><A href=3D"http://www.int=
erop.com/">http://www.interop.com/</A><BR></DIV>
--0-1837819455-1080664125=:20662--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Ramalingam, Swaminathan (Swaminathan)" <swamir@lucent.com>
Subject: Ethernet Encapsulation
Date: Wed, 31 Mar 2004 11:12:40 +0530
Lines: 22
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 31 07:46:06 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I have a query on the section 3.1.2 of
draft-ietf-pwe3-ethernet-encap-05.txt, it reads,

"In both modes, non-service-delimiting tags are passed transparently across
the PW as part of the payload"

Is this mean, PW is signalled for that VLAN but VLAN tag is not removed from
the frame, which is going to be MPLS data. I am here talking about
non-service-delimiting tag alone. so the frame should look like this


  SP-DA - SP-SA - Type/Length - MPLS label1- MPLS label2 - DA - SA -
*802.1Q* tag - type/length .....

If the PW is singalled especially for an VLAN, why should we carry 802.1 Q
in the MPLS data?. This looks like an overhead of 4 bytes for each frame. Is
my understanding correct?.



Thanks,
wami


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Wed, 31 Mar 2004 13:44:11 +0200
Lines: 48
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)"
	 <pwe3@ietf.org>,
        "Orly Niklass (E-mail)" <orly_n@rad.com>
X-From: pwe3-admin@ietf.org Wed Mar 31 13:50:12 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Luca Martini'" <lmartini@cisco.com>,
        "Ron Cohen (E-mail)"
	 <ronc@lyciumnetworks.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Luca and Ron,
I've re-read the relevant section of the SONET draft
and I think that the same status code can be safely
re-used for both. It should be renamed to 
"CEP/TDM mis-configuration" but, hopefully, this will not
be a problem also.


With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Luca Martini [mailto:lmartini@cisco.com]
> Sent: Tuesday, March 30, 2004 12:50 AM
> To: Sasha Vainshtein
> Cc: Mark Townsley (E-mail); PWE3 WG (E-mail); Orly Niklass 
> (E-mail); Ron Cohen (E-mail)
> Subject: Re: [PWE3] RE: Comments to draft-ietf-pwe3-iana-allocation-03
> 
> 
> 
> 
> >>>3. Allocation of a new LDP status code - TDM 
> >>>      
> >>>
> >>mis-configuration (could be
> >>    
> >>
> >>>0x00000029).
> >>>
> >>>      
> >>>
> >[Sasha] I think that "just one" will be enough - just as it 
> is enough for
> >SONET/SDH.
> >
> In this case can we use the existing code for CEP ?
> 
> 
> Luca
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 1 Mar 2004 08:00:29 -0800
Lines: 57
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain
X-From: pwe3-admin@ietf.org Mon Mar 01 17:26:20 2004
Return-path: <pwe3-admin@ietf.org>
To: "'tnadeau@cisco.com'" <tnadeau@cisco.com>, stbryant@cisco.com,
        pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2656.59)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi Tom,

Yes, I agree with you. 

-Shahram

-----Original Message-----
From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
Sent: Monday, March 01, 2004 10:57 AM
To: Shahram Davari; stbryant@cisco.com; pwe3@ietf.org
Subject: RE: [PWE3] Pseudo Wire (PW) OAM Message Mapping



> Hi,
> 
> It looks like a good initial document. However, May I suggest changing
> its name to " PW OAM interworking".

	This sounds reasonable to me as long as we put a
statement that this is not service interworking.
Don't want the document to catch fire, you know. *)

	--Tom


 
> Cheers,
> -Shahram
> 
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Sunday, February 29, 2004 11:15 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping
> 
> 
> Is there WG consensus for
> 
> Pseudo Wire (PW) OAM Message Mapping
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-
map-04.txt

to be accepted as a WG draft?

- Stewart


_______________________________________________
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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Ramalingam, Swaminathan (Swaminathan)" <swamir@lucent.com>
Subject: Ethernet Raw mode encapsulation
Date: Wed, 31 Mar 2004 17:38:14 +0530
Lines: 18
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
X-From: pwe3-admin@ietf.org Wed Mar 31 14:14:04 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

All-

As per section 4.4 Ethernet of PWE3-CTRL, Ethernet frame (untagged) should
be encapsulated with "ethernet raw mode". But in section 3.1.2 "Raw mode Vs
Tagged mode", 

"In both modes, non-service-delimiting tags are passed transparently across
the PW, as part of the payload"...

I assume non-service-delimiting is a customer VLAN tag. If it is, how does
Ethernet raw mode PW can have non-service-delimiting tag, as this mode is
only for Ethernet frame not the frame with VLAN tags

Pl. clarify


Thanks,
Swami


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: RE: Comments to draft-ietf-pwe3-iana-allocation-03
Date: Wed, 31 Mar 2004 08:30:54 -0700
Organization: Cisco Systems
Lines: 82
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E111F@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Ron Cohen (E-mail)" <ronc@lyciumnetworks.com>,
        "Mark Townsley (E-mail)" <townsley@cisco.com>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>,
        "Orly Niklass (E-mail)" <orly_n@rad.com>
X-From: pwe3-admin@ietf.org Wed Mar 31 17:33:08 2004
Return-path: <pwe3-admin@ietf.org>
X-BrightmailFiltered: true
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.5) Gecko/20031020
X-Accept-Language: en-us, en
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E111F@TLV1>
X-PMX-Version: 4.1.1.86173
X-from-outside-Cisco-experimental-header: [10.32.224.186]
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Excellent,
I will make the change.
Luca


Sasha Vainshtein wrote:

>Luca and Ron,
>I've re-read the relevant section of the SONET draft
>and I think that the same status code can be safely
>re-used for both. It should be renamed to 
>"CEP/TDM mis-configuration" but, hopefully, this will not
>be a problem also.
>
>
>With best regards,
>                                   Sasha Vainshtein
>email:     sasha@axerra.com <mailto:sasha@axerra.com> 
>tel:       +972-3-7659993 (office)
>           +972-8-9254948 (res.)
>           +972-58-674833 (cell.)
> 
>
>
>  
>
>>-----Original Message-----
>>From: Luca Martini [mailto:lmartini@cisco.com]
>>Sent: Tuesday, March 30, 2004 12:50 AM
>>To: Sasha Vainshtein
>>Cc: Mark Townsley (E-mail); PWE3 WG (E-mail); Orly Niklass 
>>(E-mail); Ron Cohen (E-mail)
>>Subject: Re: [PWE3] RE: Comments to draft-ietf-pwe3-iana-allocation-03
>>
>>
>>
>>
>>    
>>
>>>>>3. Allocation of a new LDP status code - TDM 
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>mis-configuration (could be
>>>>   
>>>>
>>>>        
>>>>
>>>>>0x00000029).
>>>>>
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>[Sasha] I think that "just one" will be enough - just as it 
>>>      
>>>
>>is enough for
>>    
>>
>>>SONET/SDH.
>>>
>>>      
>>>
>>In this case can we use the existing code for CEP ?
>>
>>
>>Luca
>>
>>
>>    
>>
>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
>
>
>  
>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 1 Mar 2004 16:59:06 +0100
Lines: 46
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Mon Mar 01 17:26:23 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: [PWE3] Pseudo Wire (PW) OAM Message Mapping
Thread-Index: AcP/pQJY9niE81PFQR+xZYmRGzq0CAAARDyw
To: "Shahram Davari" <Shahram_Davari@pmc-sierra.com>,
        "Stewart Bryant (stbryant)" <stbryant@cisco.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 15:59:07.0269 (UTC) FILETIME=[20936350:01C3FFA6]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Sounds reasonable --

Merci - m

-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
Shahram Davari
Sent: 01 March 2004 15:39
To: Stewart Bryant (stbryant); pwe3@ietf.org
Subject: RE: [PWE3] Pseudo Wire (PW) OAM Message Mapping


Hi,

It looks like a good initial document. However, May I suggest changing
its name to " PW OAM interworking".

Cheers,
-Shahram

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]
Sent: Sunday, February 29, 2004 11:15 PM
To: pwe3@ietf.org
Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping


Is there WG consensus for

Pseudo Wire (PW) OAM Message Mapping
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


_______________________________________________
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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 1 Mar 2004 10:57:04 -0500
Organization: Cisco Systems, inc.
Lines: 44
Sender: pwe3-admin@ietf.org
References: <4B6D09F3B826D411A67300D0B706EFDE0115CE29@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Reply-To: <tnadeau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 01 17:27:02 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Shahram Davari'" <Shahram_Davari@pmc-sierra.com>, <stbryant@cisco.com>,
        <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <4B6D09F3B826D411A67300D0B706EFDE0115CE29@nt-exch-yow.pmc_nt.nt.pmc-sierra.bc.ca>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


> Hi,
> 
> It looks like a good initial document. However, May I suggest changing
> its name to " PW OAM interworking".

	This sounds reasonable to me as long as we put a
statement that this is not service interworking.
Don't want the document to catch fire, you know. *)

	--Tom


 
> Cheers,
> -Shahram
> 
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Sunday, February 29, 2004 11:15 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping
> 
> 
> Is there WG consensus for
> 
> Pseudo Wire (PW) OAM Message Mapping
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-
map-04.txt

to be accepted as a WG draft?

- Stewart


_______________________________________________
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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 20:56:34 -0000
Lines: 333
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 21:59:11 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/qOnIyvR+Wg5jRtGnbMYycCldcAAHsSvg
To: <busschbach@lucent.com>, <mmorrow@cisco.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 20:56:34.0935 (UTC) FILETIME=[AE9D1870:01C3FFCF]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Many thanks Peter for providing a useful and reasoned response =
here......please see below.  regards, Neil

Busschbach, Peter B (Peter) wrote 01 March 2004 16:18:

> > 1	No defects are defined anywhere (not just in here but=20
> > in any other IETF draft/rfc) in terms of clear entry/exit=20
> > criteria and consequent actions.  Note that the defects in=20
> > MPLS are different to the defects in IP.....which should not=20
> > be surprising as their modes are different, and even this=20
> > draft recognises that fact (also see 4).  CF Y.1711 where=20
> > these are specified.
> >=20
>=20
> The draft identifies several tools for fault detection. IMO,=20
> the documents that describe these tools should define entry=20
> and exit criteria. The BFD draft already does that. To the=20
> extent that the OAM Message Mapping draft should add clarity=20
> on entry and exit criteria, we could add that to subsequent drafts.
NH=3D> Thanks.  But please remember that the defects that are relevant =
to a co-ps mode are different to those in a cl-ps mode (and both are =
different to a co-cs mode).  And a co-ps mode which does things like =
mp2p, PHP and ECMP if different yet again (here I would advise just =
using ad hoc diagnostics and running automatic defect detection/handling =
on the higher p2p LSPs where one can).  Y.1711 gives the sort of =
specification we would be expecting to see.
>=20
> >=20
> > 2	There is no demarcation between the available state and=20
> > unavailable state for network trail entities.  This means=20
> > there is no temporal basis for the specification of an=20
> > availability SLA or a network performance SLA, noting that=20
> > the latter is only relevant to the available state.  These=20
> > impact network element specifications and thus have=20
> > consequential impact on NMS/OSS.  NE and NMS/OSS=20
> > considerations are important for an operator to see correctly=20
> > executed.  CF Y.1711 where the unavailable state is specified=20
> > (as a consequential persistence of defects).
> >=20
>=20
> Adding a definition of availabillity would be pretty easy to=20
> specify and implement. I would like to understand better,=20
> though, how this would be used in practice. It seems to me=20
> that SLAs apply to the services carried over PWs, not to the=20
> PWs themselves.
NH=3D> Several points here.

First, there is a difference between QoS and Network Performance (NP) =
metrics/objectives.  The former are what a specific application =
percieves, whereas the latter are application invariant (ie for a given =
level of NP impairment different applications can have quite a different =
perspective on QoS).  NP metrics are really what the network elements =
should capture and SLAs specify.

Second, the control of availability and NP are complementary performance =
requirements.  If one does not have an agreed datum at which NP metrics =
should no longer be counted then one can easily distort the NP SLA.  =
There is also the requirement to measure the same 'apples and apples' =
here in different networks/equipment.....and this also applies *across* =
nested layer networks (the commonly agreed integration period for =
assessing availability is based on 10s of outage). Further, a service =
which has a 99% unavailability can still have perfect NP......this is =
why these metrics are complimentary.  See section 7 of Y.1711 for more =
info.

Third, there is a key ordering behaviour here:
=3D> ensure the right net arch for mode considered 1st
=3D> this allows the relevant defects to be identified
=3D> this allows appropriate OAM to be specified (and from this defect =
entry/exit criteria and consequent actions)
=3D> this allows unavalability entry/exit criteria to be specified based =
on defect persistence
=3D> this allows the up-time to be specified over which NP is relevent
You can very easily make life more complex than it need be by not =
following this ordering.  Further, and for complexity reasons, I would =
also not advise using NP metrics within the availability entry/exit =
criteria.....just use defect persistency.  Much careful thought went =
into Y.1711 on these, and several other, matters that may not be readily =
apparent to someone on a cursory reading.
>=20
> >=20
> > 3	Seq Nos cannot be left 'open-ended' wrt aberration=20
> > handling.  At some degree of persistent corruption a defect=20
> > state must be declared.  This therefore requires entry/exit=20
> > criteria and consequent actions specifying.  We note this is=20
> > at least recognised as an open issue in section 4.1.1.
> >=20
>=20
> agreed
NH=3D> Thanks Peter, I do know that you also recognise this point.
>=20
> >=20
> > 4	A PW is *not* a networked entity....it is just an=20
> > adaptation function (now whether it is a good adaptation=20
> > function for the server layer considered is a different=20
> > consideration).  An LSP however is a networked path entity in=20
> > the case of using MPLS (co-ps mode).  Similarly, an IP pkt is=20
> > also a networked entity (in the case of an IP cl-ps mode=20
> > server layer).  XoverMPLS is therefore not the same as=20
> > XoverIP....I am perplexed as to why this fact so hard for=20
> > some folks to grok/accept.  Is it to make the work palatable=20
> > to IETF folks?  But who is kidding who here?  Whilst this=20
> > stance might be necessary to 'sell' this stuff in IETF,=20
> > speaking as an operator we can't afford to base future=20
> > network investments on such misplaced ideologies....we need=20
> > this stuff properly architecting else it will impact our=20
> > costs (both capex and opex) and the efficacy of the services=20
> > we can offer. =20
> >=20
> > This distinction between MPLS and IP is even recognised in=20
> > the draft.....for example, in section 4.1 it says:
> >=20
> > "In case of MPLS there are additional failures (see also [ITU-T=20
> >    Y.1710]). E.g.=20
> >    =20
> >    . PW mislabeling, which could be due to a failure on the=20
> > ingress PE=20
> >      or due to an over-writing of the PW label value=20
> somewhere along=20
> >      the way=20
> >    =20
> >    . Label swapping or LSP mismerge in the PSN network, which could=20
> >      result in the termination of a PW at the wrong egress PE.=20
> >=20
> >    . Unintended self-replication (e.g. due to loops or denial-of-
> >      Service attacks) "
> >=20
> > This is of course correct. Note that these defects *cannot*=20
> > occur in a cl-ps server layer like IP, which is precisely=20
> > what the above text implies, because a cl-ps server layer=20
> > must always have a network significant DA/SA pair in each=20
> > packet.  However, when using a co-ps forwarding mode like=20
> > MPLS this is not the case.  Here we have a trail entity (ie=20
> > an LSP) that is constructed between addressable (ie network=20
> > significant) access points by the concatenation of a sequence=20
> > of single link-connection (downstream only) significant identifiers.
> >=20
> > So given this is even recognised in the draft now (and as one=20
> > reads through the draft it becomes increasingly clear that=20
> > the MPLS server layer case is being treated quite differently=20
> > to the IP server layer case), then why not go the extra step=20
> > and come clean by accepting that we don't have to force=20
> > XoverMPLS to be the same as XoverIP?  We could have a=20
> > nice/simple adaptation for carrying clients over arch=20
> > compliant MPLS now and really start to leverage the latent=20
> > potential of MPLS.
> >=20
> > Can someone please explain to us why this can't this be done=20
> > (and please don't use mp2p and PHP as excuses....we know=20
> > these are broken arch flavours of MPLS, we just have to live=20
> > with these and move on....we should not keep making further=20
> > mistakes on the back of past mistakes)?
> >=20
>=20
> Many of the procedures described in the document apply to=20
> both X-over-MPLS and X-over-IP. Some procedures depend on the=20
> specific type of PSN and are identified as such.=20
>=20
> I don't understand why it is so hard to grok that there is an=20
> advantage in trying to achieve as much commonality as=20
> possible between both modes, given that many network elements=20
> support both MPLS and IP.
NH=3D> Oh I do understand why some might hold this view.  However, it is =
a fact that a co-cs mode is different to a co-ps mode is different to a =
cl-ps mode.  One can get far more benefits IMO by using these =
differences wisely rather than not.  We have further stuff we are =
pursuing where using the modes in a complimentary manner can lead in our =
view to a better alternate network services vision.....however, this is =
outside the scope of this thread.
>=20
>=20
> >=20
> > 5	Can someone please explain to us why Y.1710 (which is=20
> > largely about principles/requirements) is at long last=20
> > recognised in this draft but Y.1711 is not recognised as a=20
> > valid OAM solution for MPLS?  This is especially puzzling for=20
> > us as Y.1711 is simple and complete (wrt defect and=20
> > availability specifications) and was written by an=20
> > operator.....so one might get the hint here that it was=20
> > something that we 'required' ;-)  It seems quite bizarre that=20
> > this is not included (even for completeness of reference),=20
> > especially noting this remark at the end of section 4.2.2:
> >=20
> > "Based on these observations, it is clear that a Service=20
> > Provider has the disposal of a variety of tools. There are=20
> > many factors that influence which combination of tools best=20
> > meets its needs."=20
> >=20
> > Is there some specific technical (or other) reason why Y.1711=20
> > cannot be referenced?
> >=20
>=20
> No technical reason. Since Y.1711 is controversial within the=20
> IETF, it was decided to leave it out of the current draft and=20
> ask  the mailing list for their opinion about the inclusion=20
> of Y.1711. That request went out a while ago and several=20
> people responded. I assume it is up to the WG Chairs to make=20
> the final decision.
NH=3D> What am I supposed to say to this?  Seems a very strange =
situation where some folks can work on a control-plane for SDH and yet =
ignore a simple/complete MPLS OAM solution like Y.1711.  It should at =
least be referenced even if folks then choose to ignore it for their own =
reasons.
>=20
> >=20
> > 6	In section 4.4 it says:
> >=20
> > "Besides reporting PW failures, PW status is used to=20
> > propagate AC failures. When and how to use those messages is=20
> > dependent on the emulated protocol and will be explained in=20
> > the subsequent paragraphs 5.3 and 6.3)."
> >=20
> > This is generally incorrect.  If one respects the=20
> > client/server architectural requirements (in particular=20
> > client and server layer independence, and client layer=20
> > transparency) then a failure of a client layer network should=20
> > have no consequential impact on any server layer.  The above=20
> > statement is violating layer independence and it is therefore=20
> > not a good idea.  It's the same as asking a SDH network to=20
> > carry an ATM client (or any other client) layer's failure=20
> indications.
> >=20
> > And what happens if the client and server layers are own by=20
> > different operating parties?  This is obviously a wrong=20
> > behaviour here.
> >=20
> > Each layer network must be self-contained and in a=20
> > client/server relationship they must be independent.
> >=20
>=20
> I agree. As you can verify, the behavior specified for PWE of=20
> ATM, SONET (CES)and TDM (SATOP) meets your requirements.=20
> However, what to do in case of Frame Relay? Frame Relay=20
> doesn't have a standard in-band way of conveying state=20
> information  from one NNI to another. In case a PW is used to=20
> connect two FR NNIs, it was decided to use the PW Status=20
> message to carry AC state information.
>=20
> What do you propose? Should we eradicate Frame Relay from=20
> this world because it doesn't meet your client/server principles? :-)
NH=3D> No of course not....but vendors specified FR not operators.  =
There is a lesson there ;-)
>=20
>=20
> > =20
> > 7	In section 4.7 it says:
> >=20
> > "PWs can fail in a single direction or in both directions.=20
> > PEs SHOULD keep track of the status of each individual=20
> > direction. In other words, a PE SHOULD be able to distinguish=20
> > between the following states: "PW UP", "PW Transmit Direction=20
> > Down", "PW Receive Direction Down", "PW Receive and Transmit Down".=20
> >   =20
> > The next two sections discuss under which conditions a PE=20
> > enters and exits these states. To avoid an unnecessarily=20
> > complicated description, only the states "PW UP" and "PW=20
> > DOWN" are discussed without further analysis whether it=20
> > applies to one or two directions of the PW."
> >=20
> > Be careful here.  Performance metrics apply unidirectionally=20
> > and only to the available state.  However, for many=20
> > applications the failure of one direction effectively means=20
> > *both* directions must be considered as failed.  Thus even if=20
> > only a single direction fails (though to be accurate, this=20
> > actually means if one direction enters the unavailable state)=20
> > then the collection of performance metrics of *both*=20
> > directions should be suspended....at least wrt to their=20
> > meaning against any performance SLAs that are being measured.=20
> >  Have a read of Y.1711, as this explains what is required here.
> >=20
> >=20
>=20
> Good point. The PW Status error codes distinguish between the=20
> PW being down in one direction and it being down in both=20
> directions. Therefore, the PEs need to maintain the states=20
> identified in the document. However, as far as availability =20
> from an operator perspective is concerned, the PW should be=20
> considered down even if only one direciton is down. We can=20
> clarify that in the next draft.
NH=3D> Thanks....but note my earlier comments on availability vs NP =
objectives.  Its so easy to make life very hard for yourself.  These =
aspectes were considered in Y.1711 in an attempt to make this stuff =
simple.
>=20
>=20
> > 8	In section 4.7.1 it says:
> >=20
> > "Note that if the control session between the PEs fails, the=20
> > PW is torn down and needs to be re-established. As a=20
> > consequence, control session failure leads to disappearance=20
> > of the PW, not to a PW Down state."=20
> >=20
> > This should not be taken as a general requirement.  Failures=20
> > of control-plane components should not necessarily remove=20
> > data-plane trails that have been set-up.  This is=20
> > particularly true in the case of S-PVC-like constructs.
> >=20
>=20
> I agree, but IMO this should be resolved in the Control=20
> Draft.
NH=3D> I agree.  But maybe the requirement should at least be noted.

> The current version of the control draft refers to =20
> RFC 3036 for the use of LDP to set up PWs. In my=20
> interpretation that means that a PW must be torn down if the=20
> LDP session fails. Graceful Restart for PWs could be added=20
> but would require specific text to that effect. Once it is in=20
> the Control Draft, we could update the OAM Message Mapping=20
> draft accordingly.
>=20
>=20
> >=20
> > 9	Towards the end of section 5.2 FR 'port-mode' is=20
> > mentioned.  Similarly in section 6.2 wrt ATM 'transparent=20
> > mapping' it says:
> >=20
> > "In case of transparent mapping, where the PE does not keep=20
> > track of the status of individual ATM VPCs or VCCs, it is=20
> > possible that a PE does not know which VPCs and/or VCCs are=20
> > active. In such a case there is a need for another fault=20
> > indication mechanism on the AC. This is beyond the scope of=20
> > this document."
> >=20
> > 'Port-mode' has no meaning in functional architecture=20
> > terms.....and for a good reason as the extract above=20
> > demonstrates....and really ought not to be used for any client case.
>=20
> I think there are situations in which the port mode makes=20
> sense and where proper behavior can be specified. It is,=20
> however, our of scope and I don't think we should use=20
> bandwidth on the mailing list to discuss that.
NH=3D> OK, but the cases where this can be resolved are not clear to me =
however.


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Toby Smith <tob@laurelnetworks.com>
Subject: Glitches in draft-ietf-pwe3-iana-allocation-02.txt
Date: Mon, 1 Mar 2004 16:31:07 -0500
Lines: 49
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0 (Apple Message framework v552)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Mon Mar 01 22:32:08 2004
Return-path: <pwe3-admin@ietf.org>
To: lmartini@cisco.com, mark@townsley.net
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi,

There seem to be some discrepancies in this document compared to what's 
stated in its companion, draft-ietf-pwe3-control-protocol-05.txt.

In section 5.4, pwe3-control states:

"The Length field is defined as the length of the interface parameter 
including the parameter id and length field itself."

The first few interface parameters defined in pwe3-iana-allocation seem 
to obey this, but then go off the rails at some point.  Its current 
contents:

    The interface parameter ID is assigned as follows:
    Parameter   ID Length    Description

        0x01         4       Interface MTU in octets.
        0x02         4       Maximum Number of concatenated ATM cells.
        0x03   up to 82      Optional Interface Description string.
        0x04         4       CEP [8] Payload Bytes.
        0x05         2       CEP options.
        0x06         2       Requested VLAN ID
        0x07         4       CEP/TDM bit-rate
        0x08         2       Frame-Relay DLCI Length
        0x09         2       Fragmentation indicator

Looks like beginning at CEP options (0x05), all length values are 2 
bytes too short.  The correct table should be:

    The interface parameter ID is assigned as follows:
    Parameter   ID Length    Description

        0x01          4      Interface MTU in octets.
        0x02          4      Maximum Number of concatenated ATM cells.
        0x03   up to 82      Optional Interface Description string.
        0x04          4      CEP [8] Payload Bytes.
        0x05          4      CEP options.
        0x06          4      Requested VLAN ID
        0x07          6      CEP/TDM bit-rate
        0x08          4      Frame-Relay DLCI Length
        0x09          4      Fragmentation indicator

Although this all raises the question of why the IANA document need 
discuss the length of these parameters at all, when they're adequately 
described in pwe3-control already.

Regards,
Tob


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: Proposal to Progress
  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 01 Mar 2004 17:31:04 -0500
Lines: 15
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF3321@i2km07-ukbr.domain1.systemhost.net> <0536FC9B908BEC4597EE721BE6A3538904EF3321@i2km07-ukbr.domai
 n1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: <busschbach@lucent.com>, <mmorrow@cisco.com>, <pwe3@ietf.org>,
        <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 23:36:05 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: andymalis@comcast.net@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: neil.2.harrison@bt.com
In-Reply-To: <0536FC9B908BEC4597EE721BE6A3538904EF3321@i2km07-ukbr.domai
 n1.systemhost.net>
References: <0536FC9B908BEC4597EE721BE6A3538904EF3321@i2km07-ukbr.domain1.systemhost.net>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Neil,

Without re-quoting the email exchange (to save us all some BW and disk 
space), it's clear that you have some technical problems with this draft. 
:-)  However, are you opposed to this becoming a working group draft solely 
on the technical grounds, or because you also feel that it's not a valid WG 
work item because it doesn't fit within the charter and/or because you feel 
that it's not a useful work item?  If your objection is solely technical, 
then it can still become a WG draft, and we can all work towards correcting 
the details.  Personally, I think this fits within the WG charter 
(especially now since the interworking aspects have been removed) and 
provides not just useful, but required, functionality.

Cheers,
Andy


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: How to proceed with the PWE3 TDM Control Protocol Extensions draf
 t
Date: Mon, 1 Mar 2004 05:17:28 +0200
Lines: 37
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain
Cc: "'pwe3@ietf.org '" <pwe3@ietf.org>, Alik Shimelmits <alik@AXERRA.com>,
        Sharon Galtzur <sharon@AXERRA.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 04:23:04 2004
Return-path: <pwe3-admin@ietf.org>
To: "'lmartini@cisco.com '" <lmartini@cisco.com>,
        "'danny@tcb.com '"
	 <danny@tcb.com>,
        "'stbryant@cisco.com '" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi all,
Following my presentation at the Seoul PWE3 session today and
a side discussion with Luca, I'd like to present the following
questions for the WG feedback:

Q1. Should the PWE3 TDM Control Prorocol Extensions draft
    (draft-vainshtein-pwe3-tdm-control-protocol-extensi-00.txt)
    be progressed separately or should it be merged with the 
    PWE3 IANA allocation and Control Protocol drafts?
    I would like to clarify that setup of TDM PWs does not 
    assume any changes in the existing Control Protocol, just
    allocation of new code points for the TDM-related service 
    types one new interface parameter (TDM Options) and 
    some new LDP status codes. It also requires some explanation
    on how these parameters are used for setup of TDM PWs.
    I'd also like to clarify that no new status TLV has been defined
    or used.
    Hence if the "merged" option is preferable, most work would be done
    done in the IANA allocation draft, but it would be also nice to
    add some reference to this work in the Control Protocol document.   

Q2. Should setup of structure-agnostic and structure-aware TDM
    PWs be treated in the same way or should it be split
    along the "Standards Track TDM PWs" vs. the "Informational
    TDM PWs" demarcation line? 
    The 1st option would mean that the current PWE3 TDM control
    protocol draft would be merged with the IANA allocation draft
    in its entirety, while the 2nd option would mean that only 
    SAToP-related components would be merged, while setup of CESoPSN and
    TDMoIP PWs would be treated in a separate draft (presumably also
    Informational). The decision would mainly affect allocation of 
    the service type code points.

Your timely feedback would be highly appreciated.

Regards,
                           Sasha


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "S.Matsushima" <satoru@ft.solteria.net>
Subject: RE:Pseudo Wire (PW) OAM Message Mapping
Date: Tue, 02 Mar 2004 13:13:09 +0900
Lines: 15
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: satoru@ft.solteria.net
X-From: pwe3-admin@ietf.org Tue Mar 02 05:16:08 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: satoru@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4
To: pwe3@ietf.org
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

It looks a good document to have oam mapping, I will support it.


--
Satoru Matsushima


>Is there WG consensus for
>
>Pseudo Wire (PW) OAM Message Mapping
>http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>
>to be accepted as a WG draft?
>
>- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Orly Nicklass" <orly_n@rad.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Date: Tue, 2 Mar 2004 07:10:49 +0200
Lines: 162
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Tue Mar 02 06:14:09 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Thread-Index: AcP/kZc+/3P7wi3sTSag1kxQRWDdawAfcfYg
To: <tnadeau@cisco.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
I agree, the two issues are important and indeed the first one is
implemented as described, the second need modification in the TC
document. I addressed both below.


-----Original Message-----
From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]=20
Sent: Monday, March 01, 2004 15:32
To: Orly Nicklass; pwe3@ietf.org
Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and
draft-orly-pwe3-tdm-mib


	A few comments. First, they are both short and sweet, which
I like. 8)   Second, Although both MIB modules state that they
fit into the existing MIB framework, and have figures that show that
they do, it is unclear to me as to how they do. For exaple, they both
seem to define their own indexing, and do not describe how this
interacts with the PW-MIB as well as the native TDM (DSx) MIBs. For
example, the way all of the existing service "glue" MIBs work is to use
the PwIndex as common index:

  pwVcEnetEntry  OBJECT-TYPE=20
      SYNTAX     PwVcEnetEntry=20
      MAX-ACCESS  not-accessible=20
      STATUS     current=20
      DESCRIPTION =20
          "This table is indexed by the same index that was created =20
          for the associated entry in the PW Table in the PW MIB.=20
          The PwVcIndex and the pwVcEnetPwVlan are used as indexes =20
          to allow multiple VLANs to exist on the same PW.=20
                          =20
          An entry is created in this table by the agent for every =20
          entry in the pwVcTable with a pwVcType of 'ethernetTagged'=20
          or 'ethernet'. Additional rows may be created by the =20
          operator or the agent if multiple entries are required for=20
          the same PW.=20
       =20
          This table provides Ethernet port mapping and VLAN =20
          configuration for each Ethernet PW."=20
  =20
      INDEX { pwVcIndex, pwVcEnetPwVlan }=20
      ::=3D { pwVcEnetTable 1 }=20

	This allows one to look at the PW in the PW-MIB based on the
PwIndex and then look at the pwVcType associated with that entry and
quickly know how to find either the PSN or service "glue" MIB entry
because it uses that same entry. Please make sure you use this.

	Please make sure these MIBs are aligned for configuration with
the existing MIBs.

ON_____________________________________________________

An entry in the TDM table is created in the exact same way as done in
the example provided above, however for value 'tdm'. Section 7 in the
TDM draft describes the sequence of actions, items 5 and 6 relate to the
linking of the new entry to the source entry in the PW-std MIB using the
same index pwVcIndex .

 pwVcTDMEntry OBJECT-TYPE
     SYNTAX        PwVcTDMEntry
     MAX-ACCESS    not-accessible
     STATUS        current
     DESCRIPTION
         "This table is indexed by the same index that was
          created for the associated entry in the PW Table
          (in the PW-STD-MIB).

            - The PwVcIndex.

          An entry is created in this table by the agent for every
          entry in the pwVcTable with a pwVcType of 'TDM'."

     INDEX  { pwVcIndex }

        ::=3D { pwVcTDMTable 1 }

 The additional indexing type objects, I referred to, are 2 pointers to
entries in other tables holding additional parameters and 1  index
linking to the native service layer. I used pointers to allow for
multiple usage of the same PW configuration parameter set. It saves time
and it complies with similar methods done in ATM and FR native service
MIBs.
____________________________________________________________

	Finally, please check the PwVcType TC in
draft-ietf-pwe3-pw-tc-mib-04.txt to make sure that the appopriate Vc
Types are defined there to support your new modules as described above.

ON_______________________________________________

In January I addressed this issue to David Z. asking  the addition of
TDM value to the PwVcType.
I checked the latest draft 04, and as I mentioned in the meeting, we do
need to add this value in in order to get the system to work properly..
The latest PwVcType reads:

PwVcType ::=3D TEXTUAL-CONVENTION=20
     STATUS      current=20
     DESCRIPTION=20
        "Indicate the PW type (i.e. the carried service).=20
        "=20
   SYNTAX   INTEGER {=20
      other(0),=20
      frameRelayDlci(1),=20
      atmAal5SduVcc(2),=20
      atmTransparent(3),=20
      ethernetTagged(4),=20
      ethernet(5),=20
      hdlc(6),=20
      ppp(7),=20
      cem(8),  -- old format=20
      atmCellNto1Vcc(9),=20
      atmCellNto1Vpc(10),=20
      ipLayer2Transport(11),=20
      atmCell1to1Vcc(12),=20
      atmCell1to1Vpc(13),=20
      atmAal5PduVcc(14),=20
      frameRelayPortMode(15),=20
      cep(16)=20
       }       =20
 We need value tdm(17) to be added.

__________________________________________
	So as long a the above are completed, I see no reason why these
both shouldn't be made WG drafts.

	--Tom



> Hi All,
>=20
> Following my presentation today in Seoul,=20
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-satop-mib-00.txt
>=20
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-TDM-mib-00.txt

I would like to proceed with a proposal to progress the drafts as
Working Group items.=20
Please comment.=20
=20

Orly Nicklass, PhD
Associate VP R&D,
RAD Data Communications Ltd,
24 Raoul Wallenberg St.
Tel Aviv, 69719, Israel
Tel : +972 3 765 9969; Fax : +972 3 644 0930
email: orly_n@rad.com
RAD's web site : www.rad.com



=20

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Rahul Aggarwal <rahul@juniper.net>
Subject: Re: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 1 Mar 2004 21:14:44 -0800 (PST)
Lines: 26
Sender: pwe3-admin@ietf.org
References: <4042B8AF.5060204@cisco.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 02 06:18:02 2004
Return-path: <pwe3-admin@ietf.org>
X-Authentication-Warning: sapphire.juniper.net: rahul owned process doing -bs
To: Stewart Bryant <stbryant@cisco.com>
In-Reply-To: <4042B8AF.5060204@cisco.com>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Hi Stewart,

On Mon, 1 Mar 2004, Stewart Bryant wrote:

> Is there WG consensus for
>
> Pseudo Wire (PW) OAM Message Mapping
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>
> to be accepted as a WG draft?
>

This draft provides a reasonable starting point for bringing this work in
the WG. Hence yes.

rahul

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Andrew G. Malis" <andy.malis@tellabs.com>
Subject: RE:Pseudo Wire (PW) OAM Message Mapping
Date: Tue, 02 Mar 2004 00:33:46 -0500
Lines: 22
Sender: pwe3-admin@ietf.org
References: <5.1.1.9.2.20040302113354.06038ec8@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-From: pwe3-admin@ietf.org Tue Mar 02 06:37:03 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: pwe3@ietf.org
In-Reply-To: <5.1.1.9.2.20040302113354.06038ec8@localhost>
References: <5.1.1.9.2.20040302113354.06038ec8@localhost>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I've already said it elsewhere, but ditto.

Andy

---------

At 3/2/2004 01:13 PM +0900, S.Matsushima wrote:
>It looks a good document to have oam mapping, I will support it.
>
>
>--
>Satoru Matsushima
>
>
>>Is there WG consensus for
>>
>>Pseudo Wire (PW) OAM Message Mapping
>>http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>>
>>to be accepted as a WG draft?
>>
>>- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: PWE3 new WG items? PW QoS
Date: Mon, 01 Mar 2004 23:12:12 -0700
Lines: 116
Sender: pwe3-admin@ietf.org
References: <8162DD929D7AD24CAD3FC5317CE41FB06D46F3@w2kmaexg02.wavesmithnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>,
        "'Proch, Daniel'" <Daniel.Proch@marconi.com>,
        "'Rahul Aggarwal'" <rahul@juniper.net>, benjamin.niven-jenkins@bt.com,
        pwe3@ietf.org
X-From: pwe3-admin@ietf.org Tue Mar 02 07:13:03 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029
X-Accept-Language: Italian [it],French/Canada [fr-CA],French/France [fr-FR],English/United States [en-US]
To: "Shah, Himanshu" <hshah@ciena.com>
In-Reply-To: <8162DD929D7AD24CAD3FC5317CE41FB06D46F3@w2kmaexg02.wavesmithnet.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Shah, Himanshu wrote:

>If one was to map one PW per transport LSP,
>one does not need RSVP signaling for PW QOS....:-)
>
>I remember a debate at IETF where a group of people 
>were concerned about scaling of RSVP's use 
>for LSP signaling. Well, PWs are multi magnitude
>higher order than transport LSPs.
>
>  
>
I did not say it would scale well ....
ATM stile CAC for each PW has been proved not to scale.
But this is useful as an exception tool in some cases.

>Also, isn't direction an issue?
>  
>
no. 2 LSPs need to be setup.

>Target PE (tail end) tells the source PE (head end)
>about his local AC's QOS requirements. Source PE (head-end)
>then selects an appropriate transport tunnel to target PE (tail-end).
>  
>
Luca

>If I remember correctly, in RSVP-TE the head-end specifies
>the QOS requirement (which tail-end can adjust in RESV).
>
>/himanshu
>
>
>  
>
>>-----Original Message-----
>>From: Luca Martini [mailto:lmartini@cisco.com]
>>Sent: Thursday, February 19, 2004 10:51 AM
>>To: Busschbach, Peter B (Peter)
>>Cc: 'Proch, Daniel'; 'Rahul Aggarwal'; benjamin.niven-jenkins@bt.com;
>>Shah, Himanshu; pwe3@ietf.org
>>Subject: Re: [PWE3] PWE3 new WG items? PW QoS
>>
>>
>>Busschbach, Peter B (Peter) wrote:
>>
>>[snip]
>>
>>    
>>
>>>I would agree that if QoS were the only problem that needs 
>>>      
>>>
>>to be solved it could be acceptable to carry QoS information 
>>in the LDP messages that are used for PW setup (albeit that 
>>it is somewhat ugly since it makes LDP look like CR-LDP which 
>>has been depreciated).
>>    
>>
>>>However, there are other issues that need to be solved. 
>>>      
>>>
>>Several people on this mailing list suggested that we need to 
>>address PW stitching. It seems to me that stitching of PWs 
>>requires a signaling protocol that establishes a multi-hop PW 
>>through switches that switch based on the PW label. RSVP is 
>>in my view the only reasonable solution.
>>    
>>
>>>Hence, if we don't look at one problem at a time, but at the 
>>>      
>>>
>>entire problem space, I think we need to adopt RSVP as a way 
>>to establish PWs. It would solve the problems of both QoS and 
>>stitching.
>>    
>>
>>>Peter
>>>
>>> 
>>>
>>>      
>>>
>>Peter,
>>It is possible ( I already know of one implementation ) to select an 
>>RSVP LSP to transport a single PW.
>>That does not change the protocol , and does carry QoS information 
>>needed by the PSN. It also achieves another property that as it turns 
>>out is quite useful in practice: explicit routing of the PW 
>>across the 
>>PSN. ( this is for TE , but also other reasons like avoiding 
>>shared PSN 
>>failure modes )
>>
>>Luca
>>
>>    
>>
>>>_______________________________________________
>>>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-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: David Zelig <Davidz@corrigent.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and dra
	ft-orly-pwe3-tdm-mib
Date: Tue, 2 Mar 2004 09:22:00 +0200
Lines: 26
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Cc: tnadeau@cisco.com, pwe3@ietf.org
X-From: pwe3-admin@ietf.org Tue Mar 02 08:23:06 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Orly Nicklass'" <orly_n@rad.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Orly,
There is an inconsistency between the MIB suggested and Sasha's draft
draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt - in the MIB
module you ask for a single PW type and the later draft suggests a PW type
per TDM mode. Since PwVcType should be one to one the PW type carried in the
signaling message, one of the two methods should be first selected.

In addition - I need a specific number allocated to whatever method  - so
when a decision will be made where the signaling extension for TDM will be
defined  - it should include suggested numbers and then I will update the tc
draft.
 
Thanks
David


> -----Original Message-----
> From: Orly Nicklass [mailto:orly_n@rad.com]
> Sent: Tuesday, March 02, 2004 7:11 AM
> To: tnadeau@cisco.com; pwe3@ietf.org
> Subject: RE: [PWE3] Proposal to Progress 
> draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
> 
> 
>  
Snipped...


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and dra
	 ft-orly-pwe3-tdm-mib
Date: Tue, 2 Mar 2004 09:52:14 +0200
Lines: 62
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Cc: "'tnadeau@cisco.com '" <tnadeau@cisco.com>,
        "'pwe3@ietf.org '"
	 <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 02 08:57:20 2004
Return-path: <pwe3-admin@ietf.org>
To: "'David Zelig '" <Davidz@corrigent.com>,
        "''Orly Nicklass' '"
	 <orly_n@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

David,
I was not aware of the need of one-to-one mapping between the PW
service types used in the Martini FEC and pwVcType values in the MIB.
You seem tospecify it as a mandatory requirement in your email.

Accommodating this requirement would, IMO, result in invalidating the
"generic" TDM MIB and distributing its contents among many specific
MIB modules. 

Using just a single "TDM PW Service type" is probably possible, but would
complicate the setup draft. Clearly some form of compromise should be found.

Maybe we (you, Orly, Yaakov and myself) should meet and discuss the
possibilities once we are back from Seoul.

Regards,
                 Sasha

-----Original Message-----
From: David Zelig
To: 'Orly Nicklass'
Cc: tnadeau@cisco.com; pwe3@ietf.org
Sent: 3/2/2004 9:22 AM
Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and dra
ft-orly-pwe3-tdm-mib

Orly,
There is an inconsistency between the MIB suggested and Sasha's draft
draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt - in the MIB
module you ask for a single PW type and the later draft suggests a PW
type
per TDM mode. Since PwVcType should be one to one the PW type carried in
the
signaling message, one of the two methods should be first selected.

In addition - I need a specific number allocated to whatever method  -
so
when a decision will be made where the signaling extension for TDM will
be
defined  - it should include suggested numbers and then I will update
the tc
draft.
 
Thanks
David


> -----Original Message-----
> From: Orly Nicklass [mailto:orly_n@rad.com]
> Sent: Tuesday, March 02, 2004 7:11 AM
> To: tnadeau@cisco.com; pwe3@ietf.org
> Subject: RE: [PWE3] Proposal to Progress 
> draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
> 
> 
>  
Snipped...

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Orly Nicklass" <orly_n@rad.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and dra ft-orly-pwe3-tdm-mib
Date: Tue, 2 Mar 2004 10:22:03 +0200
Lines: 81
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <tnadeau@cisco.com>, <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 02 09:25:13 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and dra ft-orly-pwe3-tdm-mib
Thread-Index: AcQAK5HnNWH3Q974QEmYhEE0WKBjWwAAs4rQ
To: "Alexander Vainshtein" <sasha@axerra.com>,
        "David Zelig " <Davidz@corrigent.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Since the TDM draft indicates creating an entry in the TDM generic table
upon the value of 'TDM', if the 4 values suggested by Sasha will become
the solution, we can extend the generic entry to be created based on one
of the 4 values rather then based on a single value.   Obviously the
process description will have to be modified in the draft, but it will
not break the concept.

In any case the TDM generic entry was assumed to support all types under
single name so nothing is violated by providing more than a single name.

The additional pointers in that table are also consistent with such
solution.

-----Original Message-----
From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]=20
Sent: Tuesday, March 02, 2004 09:52
To: 'David Zelig '; Orly Nicklass
Cc: 'tnadeau@cisco.com '; 'pwe3@ietf.org '
Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and
dra ft-orly-pwe3-tdm-mib

David,
I was not aware of the need of one-to-one mapping between the PW service
types used in the Martini FEC and pwVcType values in the MIB.
You seem tospecify it as a mandatory requirement in your email.

Accommodating this requirement would, IMO, result in invalidating the
"generic" TDM MIB and distributing its contents among many specific MIB
modules.=20

Using just a single "TDM PW Service type" is probably possible, but
would complicate the setup draft. Clearly some form of compromise should
be found.

Maybe we (you, Orly, Yaakov and myself) should meet and discuss the
possibilities once we are back from Seoul.

Regards,
                 Sasha

-----Original Message-----
From: David Zelig
To: 'Orly Nicklass'
Cc: tnadeau@cisco.com; pwe3@ietf.org
Sent: 3/2/2004 9:22 AM
Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and
dra ft-orly-pwe3-tdm-mib

Orly,
There is an inconsistency between the MIB suggested and Sasha's draft
draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt - in the MIB
module you ask for a single PW type and the later draft suggests a PW
type per TDM mode. Since PwVcType should be one to one the PW type
carried in the signaling message, one of the two methods should be first
selected.

In addition - I need a specific number allocated to whatever method  -
so when a decision will be made where the signaling extension for TDM
will be defined  - it should include suggested numbers and then I will
update the tc draft.
=20
Thanks
David


> -----Original Message-----
> From: Orly Nicklass [mailto:orly_n@rad.com]
> Sent: Tuesday, March 02, 2004 7:11 AM
> To: tnadeau@cisco.com; pwe3@ietf.org
> Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and

> draft-orly-pwe3-tdm-mib
>=20
>=20
> =20
Snipped...

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "David Allan" <dallan@nortelnetworks.com>
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.
	 txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 03:42:27 -0500
Lines: 12
Sender: pwe3-admin@ietf.org
Cc: Shahram Davari <Shahram_Davari@pmc-sierra.com>
X-From: pwe3-admin@ietf.org Tue Mar 02 09:45:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Busschbach, Peter B (Peter)'" <busschbach@lucent.com>,
        "'neil.2.harrison@bt.com'" <neil.2.harrison@bt.com>, mmorrow@cisco.com,
        pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I'd like to suggest a more specific title,

"Interworking of fault notifications for PWs", OAM is a BIG subject....

Neil does provide an important list of items to be addressed. I'd
specifically amplify that directional of notifications (AIS vs RDI) needs to
be preserved, a simple down indication is the degenerate case.

I've also suggested that Y.1712 should be in the document....

cheers
Dave


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 09:09:32 -0000
Lines: 98
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <busschbach@lucent.com>, <mmorrow@cisco.com>, <pwe3@ietf.org>,
        <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Tue Mar 02 10:12:16 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/3SH3RlZ++x+PSmWPHFNsXWg5GAAATyqQ
To: <andymalis@comcast.net>
X-OriginalArrivalTime: 02 Mar 2004 09:09:33.0347 (UTC) FILETIME=[13CA3730:01C40036]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

> Neil,
>=20
> Without re-quoting the email exchange (to save us all some BW=20
> and disk=20
> space), it's clear that you have some technical problems with=20
> this draft.=20
> :-)  However, are you opposed to this becoming a working=20
> group draft solely=20
> on the technical grounds, or because you also feel that it's=20
> not a valid WG=20
> work item because it doesn't fit within the charter and/or=20
> because you feel=20
> that it's not a useful work item?  If your objection is=20
> solely technical,=20
> then it can still become a WG draft, and we can all work=20
> towards correcting=20
> the details.  Personally, I think this fits within the WG charter=20
> (especially now since the interworking aspects have been removed) and=20
> provides not just useful, but required, functionality.
>=20
> Cheers,
> Andy

Hi Andy,

Our concerns are not whether: (i) this work in/out charter?, and/or (ii) =
this draft is technically correct?, and/or(iii) this is useful work =
anyway?  We have a more fundamental issue regarding the efficacy of the =
architecture and the functional components of the underpinning =
technologies concerned.

Let me try and explain this.  I work closely with some of the guys who =
did a lot of the G.805/809 functional architecture stuff.  We have a =
deep passion about getting the net arch right. Why?  Well, bitter =
experience has taught us that bad net arch will hurt downstream in many =
ways.....esp when its consequences play right through to NMS/OSS.  We =
have been here far too many times in the past.  So any technology that =
(i) breaks the arch rules of the network mode considered and/or (ii) has =
significant functional deficiences is going to start ringing alarms =
bells for us.

Now folks here would not get too upset if this stuff stayed niche, but =
when things like MPLS start to get discussed as a key core convergence =
technology then we are going to take a far stronger interest in it.

(To save your hard disc) I won't repeat the arguments about what is =
wrong with MPLS as-is, PWs not being a proper layer network, etc.  We =
are sure of our ground here, but we also know there is no point arguing =
with folks you don't understand the func arch language (or perhaps have =
other reasons for not wanting to accept our arguments).=20

Currently we regard MPLS as not fit-for-purpose as a key convergence =
technology.....and from discusssions we have had with engineers in =
several other operators it seems we are not alone in this view (though =
very few operators are active in standards these days, and even fewer =
are prepared to say anything in public for various reasons).

You have heard me say in the past that we need all 3 networking modes, =
and that the key challenge we have is working out how to make them work =
together most optimally to deliver a full range of network services that =
are fairly-priced, meaningful and secure in a future-proofed =
architecture at min capex/opex.....and we have some ideas on how to do =
this.  To us this starts with a good appreciation and respect of =
G.805/809 principles (though its more than that).  We need some =
technology to assume the co-ps role in this architecture, and in fact =
this does not have to be MPLS.  But if MPLS can assume this role then =
great.  But to do so the broken stuff needs to be deprecated over the =
long-term and the missing stuff added (eg the need an OOB =
control/management-plane that you/I briefly discussed a while ago when =
you came to see us).  We would also like to see a simpler adaptation for =
carrying clients over LSPs.  Put simply, we'd like to be able to do far =
more with MPLS and *not* PWs.

Now let's get back to this draft.  Its not that long ago we tried to get =
folks in IETF interested in adding an OAM functional component to MPLS.  =
Initially this idea was ridiculed......'go buy from a decent vendor and =
don't fix bugs with more SW' was the gist of the initial rebuff. We then =
tried running a BOF...little joy even then.  However, when deployed =
stuff started breaking then suddenly MPLS OAM is back on the agenda.  =
And not only that, I am seeing stuff that looks like my own words being =
played back now, eg don't use the control-plane to proxy for missing =
data-plane OAM, mis-branch/merge defects need factoring-in (because its =
a co-ps mode), etc.  Even Y.1710 requirements/principles is now getting =
quoted.

So, in summary:
-	whether this draft is in/out of charter is irrelevant in our view
-	the only thing that matters to us is whether MPLS is architecturally =
fit-for-purpose or not as a key core convergence technology, and this =
cannot be solved by any amount of tinkering with this draft
-	I do have some technical concerns with the draft (and I have already =
given some that Peter B has kindly responded to)......but fixing these =
will still not address our deeper arch concerns over MPLS
-	we are pleased to see service i/w removed at least.....though service =
i/w with PWs has no arch meaning IMO.

regards, Neil
=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 04:59:53 +0100
Lines: 76
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3FF41.A6F61565"
X-From: pwe3-admin@ietf.org Mon Mar 01 05:03:03 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3Lvg==
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 03:58:51.0718 (UTC) FILETIME=[82199E60:01C3FF41]
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3FF41.A6F61565
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,
=20
I presented OAM Msg Mapping status today in Seoul,
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
with a proposal to progress the draft as a Working Group item =20
=20
Whilst we had no opposition the room, I would like to ensure that there
is consensus on the list to progress the draft as a WG item.
=20
Essentially, the draft has been revised to reflect like-to-like
constructs as per the scope of PWE3 and, covers fault detection and
alarm message mapping as two separate elements.
=20
/Monique
=20
=20

------_=_NextPart_001_01C3FF41.A6F61565
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D114095103-01032004>I =
presented OAM Msg=20
Mapping status today in Seoul,&nbsp;<A=20
href=3D"http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map=
-04.txt">http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-ma=
p-04.txt</A>&nbsp;with=20
a proposal to progress the draft as a Working Group=20
item&nbsp;&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D114095103-01032004>Whilst =
we had no=20
opposition the room,&nbsp;I would like to ensure that there is consensus =
on the=20
list to progress the draft as a WG item.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D114095103-01032004>Essentially, the=20
draft has been revised to reflect like-to-like constructs as per the =
scope of=20
PWE3 and, covers fault detection and alarm message mapping as two =
separate=20
elements.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004>/Monique</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D114095103-01032004></SPAN></FONT>&nbsp;</DIV>
<DIV>
<DIV align=3Dleft><FONT face=3D"Book Antiqua"=20
size=3D2></FONT></DIV></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C3FF41.A6F61565--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "W. Mark Townsley" <townsley@cisco.com>
Subject: Re: Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt
 as a PWE3 WG Item
Date: Tue, 02 Mar 2004 12:04:27 +0100
Lines: 40
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF3321@i2km07-ukbr.domain1.systemhost.net> <6.0.3.0.2.20040301172308.02ed54f8@mail.comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: neil.2.harrison@bt.com, busschbach@lucent.com, mmorrow@cisco.com,
        pwe3@ietf.org, andy.bd.reid@bt.com, alan.mcguire@bt.com,
        peter.j.willis@bt.com, richard.spencer@bt.com,
        benjamin.niven-jenkins@bt.com, dave.milham@bt.com
X-From: pwe3-admin@ietf.org Tue Mar 02 12:07:06 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
To: "Andrew G. Malis" <andymalis@comcast.net>
In-Reply-To: <6.0.3.0.2.20040301172308.02ed54f8@mail.comcast.net>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Andrew G. Malis wrote:

> Neil,
> 
> Without re-quoting the email exchange (to save us all some BW and disk 
> space), it's clear that you have some technical problems with this 
> draft. :-)  However, are you opposed to this becoming a working group 
> draft solely on the technical grounds, or because you also feel that 
> it's not a valid WG work item because it doesn't fit within the charter 
> and/or because you feel that it's not a useful work item?  If your 
> objection is solely technical, then it can still become a WG draft, and 
> we can all work towards correcting the details.  Personally, I think 
> this fits within the WG charter (especially now since the interworking 
> aspects have been removed) and provides not just useful, but required, 
> functionality.

Much agreed, Andy.

Neil, your technical input certainly has an avenue for discussion and inclusion 
with this as a WG document. Reviewing your comments,  I'm sure the chairs would 
like to see a better focus on the specific question that was posed for this 
thread in order to weigh your opinion. Please don't make them wade through 
specific technical issues that can be addressed forthwith after the document is 
under the administration of the WG, or whether the PWE3 charter itself needs to 
be turned on end. Those discussions have their place, but not in response to 
this question.

- Mark

> 
> Cheers,
> Andy
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04. txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 15:30:04 +0100
Lines: 104
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40062.DABBB691"
Cc: "Shahram Davari" <Shahram_Davari@pmc-sierra.com>
X-From: pwe3-admin@ietf.org Tue Mar 02 15:33:15 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04. txt as a PWE3 WG Item
Thread-Index: AcQAMlgiClDkFPIWTyG6+R/Jt4OQRAAMF6pQ
To: "David Allan" <dallan@nortelnetworks.com>,
        "Busschbach, Peter B (Peter)" <busschbach@lucent.com>,
        <neil.2.harrison@bt.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 02 Mar 2004 14:29:01.0765 (UTC) FILETIME=[B50EAF50:01C40062]
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C40062.DABBB691
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dave,
=20
Certainly up for discussion -- would like to collaborate further.
=20
Thanks !
=20
/m

	-----Original Message-----
	From: David Allan [mailto:dallan@nortelnetworks.com]=20
	Sent: 02 March 2004 09:42
	To: 'Busschbach, Peter B (Peter)'; 'neil.2.harrison@bt.com';
Monique Morrow (mmorrow); pwe3@ietf.org
	Cc: Shahram Davari
	Subject: RE: [PWE3] Proposal to Progress
draft-nadeau-pwe3-oam-msg-map-04. txt as a PWE3 WG Item
=09
=09

	I'd like to suggest a more specific title,=20

	"Interworking of fault notifications for PWs", OAM is a BIG
subject....=20

	Neil does provide an important list of items to be addressed.
I'd specifically amplify that directional of notifications (AIS vs RDI)
needs to be preserved, a simple down indication is the degenerate case.

	I've also suggested that Y.1712 should be in the document....=20

	cheers=20
	Dave=20


------_=_NextPart_001_01C40062.DABBB691
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Dave,</FONT></SPAN></DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Certainly up for discussion -- would like to collaborate=20
further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Thanks=20
!</FONT></SPAN></DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D692042914-02032004><FONT face=3DArial color=3D#0000ff =

size=3D2>/m</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
David Allan=20
  [mailto:dallan@nortelnetworks.com] <BR><B>Sent:</B> 02 March 2004=20
  09:42<BR><B>To:</B> 'Busschbach, Peter B (Peter)'; =
'neil.2.harrison@bt.com';=20
  Monique Morrow (mmorrow); pwe3@ietf.org<BR><B>Cc:</B> Shahram=20
  Davari<BR><B>Subject:</B> RE: [PWE3] Proposal to Progress=20
  draft-nadeau-pwe3-oam-msg-map-04. txt as a PWE3 WG =
Item<BR><BR></FONT></DIV>
  <P><FONT size=3D2>I'd like to suggest a more specific title,</FONT> =
</P>
  <P><FONT size=3D2>"Interworking of fault notifications for PWs", OAM =
is a BIG=20
  subject....</FONT> </P>
  <P><FONT size=3D2>Neil does provide an important list of items to be =
addressed.=20
  I'd specifically amplify that directional of notifications (AIS vs =
RDI) needs=20
  to be preserved, a simple down indication is the degenerate =
case.</FONT></P>
  <P><FONT size=3D2>I've also suggested that Y.1712 should be in the=20
  document....</FONT> </P>
  <P><FONT size=3D2>cheers</FONT> <BR><FONT size=3D2>Dave</FONT>=20
</P></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C40062.DABBB691--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: RE: Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 15:42:37 +0100
Lines: 128
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <busschbach@lucent.com>, <pwe3@ietf.org>, <andy.bd.reid@bt.com>,
        <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>, <andymalis@comcast.net>
X-From: pwe3-admin@ietf.org Tue Mar 02 15:45:13 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/3SH3RlZ++x+PSmWPHFNsXWg5GAAATyqQACEyQMA=
To: <neil.2.harrison@bt.com>
X-OriginalArrivalTime: 02 Mar 2004 14:41:34.0328 (UTC) FILETIME=[759EAF80:01C40064]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Neil,

I would like to suggest that we focus on addressing the technical
concerns you may have for the draft itself - this seems most expedient
for all and defer the architecture discussion to the MPLS WG for
example. It may be that you might consider a draft pointing out what you
consider as architectural flaws with a technical proposal to address
these flaws.=20

As for this particular draft, we would like to work with you to resolve
some of the specific technical issues.

Regards,

Monique

-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
Sent: 02 March 2004 10:10
To: andymalis@comcast.net
Cc: busschbach@lucent.com; Monique Morrow (mmorrow); pwe3@ietf.org;
andy.bd.reid@bt.com; alan.mcguire@bt.com; peter.j.willis@bt.com;
richard.spencer@bt.com; benjamin.niven-jenkins@bt.com;
dave.milham@bt.com
Subject: RE: [PWE3] Proposal to Progress
draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item


> Neil,
>=20
> Without re-quoting the email exchange (to save us all some BW=20
> and disk=20
> space), it's clear that you have some technical problems with=20
> this draft.=20
> :-)  However, are you opposed to this becoming a working=20
> group draft solely=20
> on the technical grounds, or because you also feel that it's=20
> not a valid WG=20
> work item because it doesn't fit within the charter and/or=20
> because you feel=20
> that it's not a useful work item?  If your objection is=20
> solely technical,=20
> then it can still become a WG draft, and we can all work=20
> towards correcting=20
> the details.  Personally, I think this fits within the WG charter=20
> (especially now since the interworking aspects have been removed) and=20
> provides not just useful, but required, functionality.
>=20
> Cheers,
> Andy

Hi Andy,

Our concerns are not whether: (i) this work in/out charter?, and/or (ii)
this draft is technically correct?, and/or(iii) this is useful work
anyway?  We have a more fundamental issue regarding the efficacy of the
architecture and the functional components of the underpinning
technologies concerned.

Let me try and explain this.  I work closely with some of the guys who
did a lot of the G.805/809 functional architecture stuff.  We have a
deep passion about getting the net arch right. Why?  Well, bitter
experience has taught us that bad net arch will hurt downstream in many
ways.....esp when its consequences play right through to NMS/OSS.  We
have been here far too many times in the past.  So any technology that
(i) breaks the arch rules of the network mode considered and/or (ii) has
significant functional deficiences is going to start ringing alarms
bells for us.

Now folks here would not get too upset if this stuff stayed niche, but
when things like MPLS start to get discussed as a key core convergence
technology then we are going to take a far stronger interest in it.

(To save your hard disc) I won't repeat the arguments about what is
wrong with MPLS as-is, PWs not being a proper layer network, etc.  We
are sure of our ground here, but we also know there is no point arguing
with folks you don't understand the func arch language (or perhaps have
other reasons for not wanting to accept our arguments).=20

Currently we regard MPLS as not fit-for-purpose as a key convergence
technology.....and from discusssions we have had with engineers in
several other operators it seems we are not alone in this view (though
very few operators are active in standards these days, and even fewer
are prepared to say anything in public for various reasons).

You have heard me say in the past that we need all 3 networking modes,
and that the key challenge we have is working out how to make them work
together most optimally to deliver a full range of network services that
are fairly-priced, meaningful and secure in a future-proofed
architecture at min capex/opex.....and we have some ideas on how to do
this.  To us this starts with a good appreciation and respect of
G.805/809 principles (though its more than that).  We need some
technology to assume the co-ps role in this architecture, and in fact
this does not have to be MPLS.  But if MPLS can assume this role then
great.  But to do so the broken stuff needs to be deprecated over the
long-term and the missing stuff added (eg the need an OOB
control/management-plane that you/I briefly discussed a while ago when
you came to see us).  We would also like to see a simpler adaptation for
carrying clients over LSPs.  Put simply, we'd like to be able to do far
more with MPLS and *not* PWs.

Now let's get back to this draft.  Its not that long ago we tried to get
folks in IETF interested in adding an OAM functional component to MPLS.
Initially this idea was ridiculed......'go buy from a decent vendor and
don't fix bugs with more SW' was the gist of the initial rebuff. We then
tried running a BOF...little joy even then.  However, when deployed
stuff started breaking then suddenly MPLS OAM is back on the agenda.
And not only that, I am seeing stuff that looks like my own words being
played back now, eg don't use the control-plane to proxy for missing
data-plane OAM, mis-branch/merge defects need factoring-in (because its
a co-ps mode), etc.  Even Y.1710 requirements/principles is now getting
quoted.

So, in summary:
-	whether this draft is in/out of charter is irrelevant in our
view
-	the only thing that matters to us is whether MPLS is
architecturally fit-for-purpose or not as a key core convergence
technology, and this cannot be solved by any amount of tinkering with
this draft
-	I do have some technical concerns with the draft (and I have
already given some that Peter B has kindly responded to)......but fixing
these will still not address our deeper arch concerns over MPLS
-	we are pleased to see service i/w removed at least.....though
service i/w with PWs has no arch meaning IMO.

regards, Neil
=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: David Zelig <Davidz@corrigent.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and dra
	 ft-orly-pwe3-tdm-mib
Date: Tue, 2 Mar 2004 19:19:05 +0200
Lines: 108
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Cc: tnadeau@cisco.com, pwe3@ietf.org,
        Alexander Vainshtein
	 <sasha@axerra.com>
X-From: pwe3-admin@ietf.org Tue Mar 02 18:20:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Orly Nicklass'" <orly_n@rad.com>
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Orly,
Your proposed solution make sense too.

David

> -----Original Message-----
> From: Orly Nicklass [mailto:orly_n@rad.com]
> Sent: Tuesday, March 02, 2004 10:22 AM
> To: Alexander Vainshtein; David Zelig 
> Cc: tnadeau@cisco.com; pwe3@ietf.org
> Subject: RE: [PWE3] Proposal to Progress 
> draft-orly-pwe3-satop-mib and dra ft-orly-pwe3-tdm-mib
> 
> 
> Since the TDM draft indicates creating an entry in the TDM 
> generic table
> upon the value of 'TDM', if the 4 values suggested by Sasha 
> will become
> the solution, we can extend the generic entry to be created 
> based on one
> of the 4 values rather then based on a single value.   Obviously the
> process description will have to be modified in the draft, but it will
> not break the concept.
> 
> In any case the TDM generic entry was assumed to support all 
> types under
> single name so nothing is violated by providing more than a 
> single name.
> 
> The additional pointers in that table are also consistent with such
> solution.
> 
> -----Original Message-----
> From: Sasha Vainshtein [mailto:Sasha@AXERRA.com] 
> Sent: Tuesday, March 02, 2004 09:52
> To: 'David Zelig '; Orly Nicklass
> Cc: 'tnadeau@cisco.com '; 'pwe3@ietf.org '
> Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and
> dra ft-orly-pwe3-tdm-mib
> 
> David,
> I was not aware of the need of one-to-one mapping between the 
> PW service
> types used in the Martini FEC and pwVcType values in the MIB.
> You seem tospecify it as a mandatory requirement in your email.
> 
> Accommodating this requirement would, IMO, result in invalidating the
> "generic" TDM MIB and distributing its contents among many 
> specific MIB
> modules. 
> 
> Using just a single "TDM PW Service type" is probably possible, but
> would complicate the setup draft. Clearly some form of 
> compromise should
> be found.
> 
> Maybe we (you, Orly, Yaakov and myself) should meet and discuss the
> possibilities once we are back from Seoul.
> 
> Regards,
>                  Sasha
> 
> -----Original Message-----
> From: David Zelig
> To: 'Orly Nicklass'
> Cc: tnadeau@cisco.com; pwe3@ietf.org
> Sent: 3/2/2004 9:22 AM
> Subject: RE: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and
> dra ft-orly-pwe3-tdm-mib
> 
> Orly,
> There is an inconsistency between the MIB suggested and Sasha's draft
> draft-vainshtein-pwe3-tdm-control-protocol-extension-00.txt - 
> in the MIB
> module you ask for a single PW type and the later draft suggests a PW
> type per TDM mode. Since PwVcType should be one to one the PW type
> carried in the signaling message, one of the two methods 
> should be first
> selected.
> 
> In addition - I need a specific number allocated to whatever method  -
> so when a decision will be made where the signaling extension for TDM
> will be defined  - it should include suggested numbers and then I will
> update the tc draft.
>  
> Thanks
> David
> 
> 
> > -----Original Message-----
> > From: Orly Nicklass [mailto:orly_n@rad.com]
> > Sent: Tuesday, March 02, 2004 7:11 AM
> > To: tnadeau@cisco.com; pwe3@ietf.org
> > Subject: RE: [PWE3] Proposal to Progress 
> draft-orly-pwe3-satop-mib and
> 
> > draft-orly-pwe3-tdm-mib
> > 
> > 
> >  
> Snipped...
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Philip Yim <pyim@bodeganetworks.com>
Subject: RE: Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 10:01:17 -0800
Lines: 274
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: andymalis@comcast.net, busschbach@lucent.com, mmorrow@cisco.com,
        pwe3@ietf.org, andy.bd.reid@bt.com, alan.mcguire@bt.com,
        peter.j.willis@bt.com, richard.spencer@bt.com,
        benjamin.niven-jenkins@bt.com, dave.milham@bt.com
X-From: pwe3-admin@ietf.org Tue Mar 02 19:04:04 2004
Return-path: <pwe3-admin@ietf.org>
To: neil.2.harrison@bt.com
X-Mailer: Webmail Mirapoint Direct 3.2.2-GA
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

All, BT is a "proven network operator" and Neil et al raises =

some serious points that need to be addressed. In what forum =

I know not but to be sure MPLS will not become a core =

convergence technology unless it "correctly" deals with =

experienced operator views. =


Best

Philip

---- Original message ----
>Date: Tue, 2 Mar 2004 0=
9:09:32 -0000
>From: neil.2.harrison@bt.com  =

>Subject: RE: [PWE3] Proposal to Progress =A0draft-nadeau-pwe3-
oam-msg=
-map-04.txt as a PWE3 WG Item  =

>To: <andymalis@comcast.net>
>Cc: <busschbach@lucent.com>, <mmorrow@cis=
co.com>, =

<pwe3@ietf.org>, <andy.bd.reid@bt.com>, =

<alan.mcguire@bt.com>, <peter.j.willis@bt.com>, =

<richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>, =

<dave.milham@bt.com>
>
>> Neil,
>> =

>> Without re-quoting the email exchange (to save us all some =

BW =

>> and disk =

>> space), it's clear that you have some technical problems =

with =

>> this draft. =

>> :-)  However, are you opposed to this becoming a working =

>> group draft solely =

>> on the technical grounds, or because you also feel that =

it's =

>> not a valid WG =

>> work item because it doesn't fit within the charter and/or =

>> because you feel =

>> that it's not a useful work item?  If your objection is =

>> solely technical, =

>> then it can still become a WG draft, and we can all work =

>> towards correcting =

>> the details.  Personally, I think this fits within the WG =

charter =

>> (especially now since the interworking aspects have been =

removed) and =

>> provides not just useful, but required, functionality.
>> =

>> Cheers,
>> Andy
>
>Hi Andy,
>
>Our concerns are not whether: (i)=
 this work in/out charter?, =

and/or (ii) this draft is technically correct?, and/or(iii) =

this is useful work anyway?  We have a more fundamental issue =

regarding the efficacy of the architecture and the functional =

components of the underpinning technologies concerned.
>
>Let me try a=
nd explain this.  I work closely with some of =

the guys who did a lot of the G.805/809 functional =

architecture stuff.  We have a deep passion about getting the =

net arch right. Why?  Well, bitter experience has taught us =

that bad net arch will hurt downstream in many ways.....esp =

when its consequences play right through to NMS/OSS.  We have =

been here far too many times in the past.  So any technology =

that (i) breaks the arch rules of the network mode considered =

and/or (ii) has significant functional deficiences is going =

to start ringing alarms bells for us.
>
>Now folks here would not get =
too upset if this stuff stayed =

niche, but when things like MPLS start to get discussed as a =

key core convergence technology then we are going to take a =

far stronger interest in it.
>
>(To save your hard disc) I won't repea=
t the arguments about =

what is wrong with MPLS as-is, PWs not being a proper layer =

network, etc.  We are sure of our ground here, but we also =

know there is no point arguing with folks you don't =

understand the func arch language (or perhaps have other =

reasons for not wanting to accept our arguments). =

>
>Currently we regard MPLS as not fit-for-purpose as a key =

convergence technology.....and from discusssions we have had =

with engineers in several other operators it seems we are not =

alone in this view (though very few operators are active in =

standards these days, and even fewer are prepared to say =

anything in public for various reasons).
>
>You have heard me say in t=
he past that we need all 3 =

networking modes, and that the key challenge we have is =

working out how to make them work together most optimally to =

deliver a full range of network services that are fairly-
priced, meani=
ngful and secure in a future-proofed =

architecture at min capex/opex.....and we have some ideas on =

how to do this.  To us this starts with a good appreciation =

and respect of G.805/809 principles (though its more than =

that).  We need some technology to assume the co-ps role in =

this architecture, and in fact this does not have to be =

MPLS.  But if MPLS can assume this role then great.  But to =

do so the broken stuff needs to be deprecated over the long-
term and t=
he missing stuff added (eg the need an OOB =

control/management-plane that you/I briefly discussed a while =

ago when you came to see us).  We would also like to see a =

simpler adaptation for carrying clients over LSPs.  Put =

simply, we'd like to be able to do far more with MPLS and =

*not* PWs.
>
>Now let's get back to this draft.  Its not that long ago=
 we =

tried to get folks in IETF interested in adding an OAM =

functional component to MPLS.  Initially this idea was =

ridiculed......'go buy from a decent vendor and don't fix =

bugs with more SW' was the gist of the initial rebuff. We =

then tried running a BOF...little joy even then.  However, =

when deployed stuff started breaking then suddenly MPLS OAM =

is back on the agenda.  And not only that, I am seeing stuff =

that looks like my own words being played back now, eg don't =

use the control-plane to proxy for missing data-plane OAM, =

mis-branch/merge defects need factoring-in (because its a co-
ps mode),=
 etc.  Even Y.1710 requirements/principles is now =

getting quoted.
>
>So, in summary:
>-	whether this draft is in/out of=
 charter is irrelevant =

in our view
>-	the only thing that matters to us is whether MPLS is =

architecturally fit-for-purpose or not as a key core =

convergence technology, and this cannot be solved by any =

amount of tinkering with this draft
>-	I do have some technical concern=
s with the draft (and =

I have already given some that Peter B has kindly responded =

to)......but fixing these will still not address our deeper =

arch concerns over MPLS
>-	we are pleased to see service i/w removed at=
 =

least.....though service i/w with PWs has no arch meaning IMO.
>
>rega=
rds, Neil
> =

>
>_______________________________________________
>pwe3 mailing list
>pwe3@ietf.org
>https://www1.ietf.org/mailman/listinfo/pwe3
Philip Yim=


Bodega Networks, Inc.
Bus: 707-479-7640
Fax: 775-890-8293

www.b=
odeganetworks.com

This electronic message contains information from B=
odega Networks, Inc. which may be privileged or confidential. The inform=
ation is intended to be for the use of the individual(s) or entity named=
 above. If you are not the intended recipient be aware that any disclosu=
re,copying, distribution or use of the contents of this information is p=
rohibited.

If you have received this electronic message in error, ple=
ase notify us by telephone or email(to the numbers or address above) imm=
ediately.


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Tue, 2 Mar 2004 20:04:50 -0000
Lines: 184
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <busschbach@lucent.com>, <pwe3@ietf.org>, <andy.bd.reid@bt.com>,
        <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>, <andymalis@comcast.net>
X-From: pwe3-admin@ietf.org Tue Mar 02 21:08:06 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress  draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/3SH3RlZ++x+PSmWPHFNsXWg5GAAATyqQACEyQMAACu57AA==
To: <mmorrow@cisco.com>
X-OriginalArrivalTime: 02 Mar 2004 20:04:51.0631 (UTC) FILETIME=[9F503BF0:01C40091]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Monique....We have been discussing how to respond to you wrt this mail =
and your last mail; where you invited us to submit a draft with our =
proposals in it.....so sorry for the small delay in responding.

I am happy to work on the technical detail of this draft (in fact I have =
already submitted some comments that Peter B kindly responded to).  =
However, this assumes this draft is based on the right solution =
already.....and that is probably not the case.  In fact, the draft =
already shows that our main concern is true (ie that an adaptation of X =
to MPLS requires a different treatment to an adaptation of X to IP) by =
the various areas in the draft where different behaviours are noted both =
for the different defect types that can occur (ie MPLS server case =
different to IP server case) and how these may impact the different =
signalling cases.

Once we have concluded our internal discussions we will try and post =
something with our ideas in it....some will relate to MPLS per se and =
some will relate to the adaptation of clients into MPLS, so I am not =
sure where this best fits.  We'll think on it.

regards, Neil

> -----Original Message-----
> From: Monique Morrow (mmorrow) [mailto:mmorrow@cisco.com]
> Sent: 02 March 2004 14:43
> To: Harrison,N,Neil,IKR2 R
> Cc: busschbach@lucent.com; pwe3@ietf.org; Reid,ABD,Andy,NUJ91 R;
> Mcguire,A,Alan,XGH6 MCGUIRA R; Willis,PJ,Peter,CD WILLISPJ R;
> Spencer,R,Richard,XGH5 R; Niven-Jenkins,B,Ben,XGH5 R;
> Milham,DJ,Dave,XGJ1 MILHAMDJ R; andymalis@comcast.net
> Subject: RE: [PWE3] Proposal to Progress
> draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
>=20
>=20
> Neil,
>=20
> I would like to suggest that we focus on addressing the technical
> concerns you may have for the draft itself - this seems most expedient
> for all and defer the architecture discussion to the MPLS WG for
> example. It may be that you might consider a draft pointing=20
> out what you
> consider as architectural flaws with a technical proposal to address
> these flaws.=20
>=20
> As for this particular draft, we would like to work with you=20
> to resolve
> some of the specific technical issues.
>=20
> Regards,
>=20
> Monique
>=20
> -----Original Message-----
> From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
> Sent: 02 March 2004 10:10
> To: andymalis@comcast.net
> Cc: busschbach@lucent.com; Monique Morrow (mmorrow); pwe3@ietf.org;
> andy.bd.reid@bt.com; alan.mcguire@bt.com; peter.j.willis@bt.com;
> richard.spencer@bt.com; benjamin.niven-jenkins@bt.com;
> dave.milham@bt.com
> Subject: RE: [PWE3] Proposal to Progress
> draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
>=20
>=20
> > Neil,
> >=20
> > Without re-quoting the email exchange (to save us all some BW=20
> > and disk=20
> > space), it's clear that you have some technical problems with=20
> > this draft.=20
> > :-)  However, are you opposed to this becoming a working=20
> > group draft solely=20
> > on the technical grounds, or because you also feel that it's=20
> > not a valid WG=20
> > work item because it doesn't fit within the charter and/or=20
> > because you feel=20
> > that it's not a useful work item?  If your objection is=20
> > solely technical,=20
> > then it can still become a WG draft, and we can all work=20
> > towards correcting=20
> > the details.  Personally, I think this fits within the WG charter=20
> > (especially now since the interworking aspects have been=20
> removed) and=20
> > provides not just useful, but required, functionality.
> >=20
> > Cheers,
> > Andy
>=20
> Hi Andy,
>=20
> Our concerns are not whether: (i) this work in/out charter?,=20
> and/or (ii)
> this draft is technically correct?, and/or(iii) this is useful work
> anyway?  We have a more fundamental issue regarding the=20
> efficacy of the
> architecture and the functional components of the underpinning
> technologies concerned.
>=20
> Let me try and explain this.  I work closely with some of the guys who
> did a lot of the G.805/809 functional architecture stuff.  We have a
> deep passion about getting the net arch right. Why?  Well, bitter
> experience has taught us that bad net arch will hurt=20
> downstream in many
> ways.....esp when its consequences play right through to NMS/OSS.  We
> have been here far too many times in the past.  So any technology that
> (i) breaks the arch rules of the network mode considered=20
> and/or (ii) has
> significant functional deficiences is going to start ringing alarms
> bells for us.
>=20
> Now folks here would not get too upset if this stuff stayed niche, but
> when things like MPLS start to get discussed as a key core convergence
> technology then we are going to take a far stronger interest in it.
>=20
> (To save your hard disc) I won't repeat the arguments about what is
> wrong with MPLS as-is, PWs not being a proper layer network, etc.  We
> are sure of our ground here, but we also know there is no=20
> point arguing
> with folks you don't understand the func arch language (or=20
> perhaps have
> other reasons for not wanting to accept our arguments).=20
>=20
> Currently we regard MPLS as not fit-for-purpose as a key convergence
> technology.....and from discusssions we have had with engineers in
> several other operators it seems we are not alone in this view (though
> very few operators are active in standards these days, and even fewer
> are prepared to say anything in public for various reasons).
>=20
> You have heard me say in the past that we need all 3 networking modes,
> and that the key challenge we have is working out how to make=20
> them work
> together most optimally to deliver a full range of network=20
> services that
> are fairly-priced, meaningful and secure in a future-proofed
> architecture at min capex/opex.....and we have some ideas on how to do
> this.  To us this starts with a good appreciation and respect of
> G.805/809 principles (though its more than that).  We need some
> technology to assume the co-ps role in this architecture, and in fact
> this does not have to be MPLS.  But if MPLS can assume this role then
> great.  But to do so the broken stuff needs to be deprecated over the
> long-term and the missing stuff added (eg the need an OOB
> control/management-plane that you/I briefly discussed a while ago when
> you came to see us).  We would also like to see a simpler=20
> adaptation for
> carrying clients over LSPs.  Put simply, we'd like to be able=20
> to do far
> more with MPLS and *not* PWs.
>=20
> Now let's get back to this draft.  Its not that long ago we=20
> tried to get
> folks in IETF interested in adding an OAM functional=20
> component to MPLS.
> Initially this idea was ridiculed......'go buy from a decent=20
> vendor and
> don't fix bugs with more SW' was the gist of the initial=20
> rebuff. We then
> tried running a BOF...little joy even then.  However, when deployed
> stuff started breaking then suddenly MPLS OAM is back on the agenda.
> And not only that, I am seeing stuff that looks like my own=20
> words being
> played back now, eg don't use the control-plane to proxy for missing
> data-plane OAM, mis-branch/merge defects need factoring-in=20
> (because its
> a co-ps mode), etc.  Even Y.1710 requirements/principles is=20
> now getting
> quoted.
>=20
> So, in summary:
> -	whether this draft is in/out of charter is irrelevant in our
> view
> -	the only thing that matters to us is whether MPLS is
> architecturally fit-for-purpose or not as a key core convergence
> technology, and this cannot be solved by any amount of tinkering with
> this draft
> -	I do have some technical concerns with the draft (and I have
> already given some that Peter B has kindly responded=20
> to)......but fixing
> these will still not address our deeper arch concerns over MPLS
> -	we are pleased to see service i/w removed at least.....though
> service i/w with PWs has no arch meaning IMO.
>=20
> regards, Neil
> =20
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Luca Martini <lmartini@cisco.com>
Subject: Re: Pseudo Wire (PW) OAM Message Mapping
Date: Tue, 02 Mar 2004 14:37:59 -0700
Lines: 22
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Tue Mar 02 22:38:06 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029
X-Accept-Language: Italian [it],French/Canada [fr-CA],French/France [fr-FR],English/United States [en-US]
To: pwe3 <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yes, this is fine as the initial WG document on this topic.

Luca

Stewart Bryant wrote:

> Is there WG consensus for
>
> Pseudo Wire (PW) OAM Message Mapping
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>
> to be accepted as a WG draft?
>
> - Stewart
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>
>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: George Swallow <swallow@cisco.com>
Subject: Re: Pseudo Wire (PW) OAM Message Mapping
Date: Tue, 02 Mar 2004 16:55:10 -0500
Lines: 10
Sender: pwe3-admin@ietf.org
References: <4044FEB7.1060209@cisco.com>
Cc: pwe3 <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 02 22:58:04 2004
Return-path: <pwe3-admin@ietf.org>
To: Luca Martini <lmartini@cisco.com>
cc: swallow@cisco.com
In-reply-to: Your message of "Tue, 02 Mar 2004 14:37:59 MST."
             <4044FEB7.1060209@cisco.com> 
X-Mailer: MH-E 7.4.3; nmh 1.0.4; GNU Emacs 21.2.1
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

> Yes, this is fine as the initial WG document on this topic.

Agreed.

...George

========================================================================
George Swallow             Cisco Systems                  (978) 936-1398
                           1414 Massachusetts Avenue
                           Boxborough, MA 01719


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 00:46:42 +0000
Organization: Cisco Systems, Inc.
Lines: 37
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Wed Mar 03 01:49:05 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Here is the proposed change to 5.4.3 that was discussed
at the WG meeting. Also here is the corresponding change
to section 9.

The arch draft will become informational, and
I will post a pre-draft of the full document with all
the 07 changes incorporated some time next week.

Please consider this the start of a two week last
call on this change.

I will put together a draft for the CW text in the
next few days.

- Stewart
---------------------------------------------------


5.4.3. PW Packets Aliasing IP Packets

To allow accurate packet inspection in an MPLS PSN, and/or to operate
correctly over MPLS PSNs that have deployed equal-cost multiple-path
load-balancing (ECMP), a PW packet must not alias an IP packet.
IP packets are carried in MPLS label stacks without any protocol
identifier. The method of packet discrimination must therefore
be based on some unique characteristic of the IP packet header,
which PWE3 must not mimic.

This is the subject of work in progress.

-----------------------------------------------------


9.  IANA considerations

    IANA considerations will be identified in the PWE3 documents that
    define the PWE3 encapsulation, control and management protocols.


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 03:52:24 +0200
Lines: 40
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
X-From: pwe3-admin@ietf.org Wed Mar 03 02:58:04 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Stewart Bryant '" <stbryant@cisco.com>,
        "'pwe3@ietf.org '"
	 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart and all,
Basically fine, please see a couple of minor comments inline (marked
[Sasha]).

Regards,
                 Sasha. 
... snipped ...

5.4.3. PW Packets Aliasing IP Packets

To allow accurate packet inspection in an MPLS PSN, and/or to operate
correctly over MPLS PSNs that have deployed equal-cost multiple-path
load-balancing (ECMP), a PW packet must not alias an IP packet.
[Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.
IP packets are carried in MPLS label stacks without any protocol
identifier. The method of packet discrimination must therefore
be based on some unique characteristic of the IP packet header,
which PWE3 must not mimic.
[Sasha] I honestly believe no one will ever propose verifying the cheksum
[Sasha] of the first 20 bytes after the bottom label as "the unique
[Sasha] characteristic of the IP packet header". But worse things have
[Sasha] happened, so maybe we should explicitly block this.
This is the subject of work in progress.

-----------------------------------------------------


9.  IANA considerations

    IANA considerations will be identified in the PWE3 documents that
    define the PWE3 encapsulation, control and management protocols.





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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:39 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Pseudo Wire (PW) OAM Message Mapping
Date: Mon, 01 Mar 2004 04:14:39 +0000
Organization: Cisco Systems, Inc.
Lines: 8
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 01 05:18:10 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Is there WG consensus for

Pseudo Wire (PW) OAM Message Mapping
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Alia Atlas <aatlas@avici.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Tue, 02 Mar 2004 21:09:44 -0500
Lines: 52
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "'Stewart Bryant '" <stbryant@cisco.com>,
        "'pwe3@ietf.org '" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 03:11:04 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: aatlas@pop.avici.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Avici-MailScanner: Found to be clean
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

At 08:52 PM 3/2/2004, Sasha Vainshtein wrote:
>Stewart and all,
>Basically fine, please see a couple of minor comments inline (marked
>[Sasha]).
>
>Regards,
>                  Sasha.
>... snipped ...
>
>5.4.3. PW Packets Aliasing IP Packets
>
>To allow accurate packet inspection in an MPLS PSN, and/or to operate
>correctly over MPLS PSNs that have deployed equal-cost multiple-path
>load-balancing (ECMP), a PW packet must not alias an IP packet.
>[Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.
>IP packets are carried in MPLS label stacks without any protocol
>identifier. The method of packet discrimination must therefore
>be based on some unique characteristic of the IP packet header,
>which PWE3 must not mimic.
>[Sasha] I honestly believe no one will ever propose verifying the cheksum
>[Sasha] of the first 20 bytes after the bottom label as "the unique
>[Sasha] characteristic of the IP packet header". But worse things have
>[Sasha] happened, so maybe we should explicitly block this.

The checksum is legitimate to consider as a verification, if one doesn't 
want to depend on just the first nibble.

Alia

>This is the subject of work in progress.
>
>-----------------------------------------------------
>
>
>9.  IANA considerations
>
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
>
>
>
>
>
>_______________________________________________
>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 04:27:49 +0200
Lines: 69
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "''Stewart Bryant ' '" <stbryant@cisco.com>,
        "''pwe3@ietf.org ' '"
	 <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 03:33:15 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Alia Atlas '" <aatlas@avici.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Alia and all,
I agree that checksum is a valid method of verification (even if
occasionally it could fail). My understanding has been, however,
that we do not want to use it, and tried to block a possible
loophole.
Regards,
                      Sasha

-----Original Message-----
From: Alia Atlas
To: Sasha Vainshtein
Cc: 'Stewart Bryant '; 'pwe3@ietf.org '
Sent: 3/3/2004 4:09 AM
Subject: RE: [PWE3] Proposed new 5.4.3 for arch draft

At 08:52 PM 3/2/2004, Sasha Vainshtein wrote:
>Stewart and all,
>Basically fine, please see a couple of minor comments inline (marked
>[Sasha]).
>
>Regards,
>                  Sasha.
>... snipped ...
>
>5.4.3. PW Packets Aliasing IP Packets
>
>To allow accurate packet inspection in an MPLS PSN, and/or to operate
>correctly over MPLS PSNs that have deployed equal-cost multiple-path
>load-balancing (ECMP), a PW packet must not alias an IP packet.
>[Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.
>IP packets are carried in MPLS label stacks without any protocol
>identifier. The method of packet discrimination must therefore
>be based on some unique characteristic of the IP packet header,
>which PWE3 must not mimic.
>[Sasha] I honestly believe no one will ever propose verifying the
cheksum
>[Sasha] of the first 20 bytes after the bottom label as "the unique
>[Sasha] characteristic of the IP packet header". But worse things have
>[Sasha] happened, so maybe we should explicitly block this.

The checksum is legitimate to consider as a verification, if one doesn't

want to depend on just the first nibble.

Alia

>This is the subject of work in progress.
>
>-----------------------------------------------------
>
>
>9.  IANA considerations
>
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
>
>
>
>
>
>_______________________________________________
>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Mustapha Aissaoui <mustapha.aissaoui@alcatel.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Tue, 02 Mar 2004 21:29:27 -0500
Organization: Alcatel Networks Corporaton
Lines: 55
Sender: pwe3-admin@ietf.org
References: <40452AF2.3000802@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 03:33:21 2004
Return-path: <pwe3-admin@ietf.org>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
To: stbryant@cisco.com
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart,
see a question below.

Mustapha.
--------------
Stewart Bryant wrote:
> 
> Here is the proposed change to 5.4.3 that was discussed
> at the WG meeting. Also here is the corresponding change
> to section 9.
> 
> The arch draft will become informational, and
> I will post a pre-draft of the full document with all
> the 07 changes incorporated some time next week.
> 
> Please consider this the start of a two week last
> call on this change.
> 
> I will put together a draft for the CW text in the
> next few days.
> 
> - Stewart
> ---------------------------------------------------
> 
> 5.4.3. PW Packets Aliasing IP Packets
> 
> To allow accurate packet inspection in an MPLS PSN, and/or to operate
> correctly over MPLS PSNs that have deployed equal-cost multiple-path
> load-balancing (ECMP), a PW packet must not alias an IP packet.
> IP packets are carried in MPLS label stacks without any protocol
> identifier. The method of packet discrimination must therefore
> be based on some unique characteristic of the IP packet header,
> which PWE3 must not mimic.
> 
> This is the subject of work in progress.

MA> I am not clear about the impact of the above paragraph on the
rest of Section 5.4.3 and on Section 5.4.4. I understand that option
3 in your presentation Monday proposes a separate "PWE3 control word
registry" which will not allow values of 4 and 6. If so, why it that
not sufficient? 
Why add that "the method of discrimination should be based on some
unique characteristic of the IP packet header"? 
 
> -----------------------------------------------------
> 
> 9.  IANA considerations
> 
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Wed, 3 Mar 2004 05:06:40 +0200
Lines: 40
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
X-From: pwe3-admin@ietf.org Wed Mar 03 04:14:07 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Luca Martini '" <lmartini@cisco.com>, "'pwe3 '" <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I concur,
Regards,
              Sasha 

-----Original Message-----
From: Luca Martini
To: pwe3
Sent: 3/2/2004 11:37 PM
Subject: Re: [PWE3] Pseudo Wire (PW) OAM Message Mapping

Yes, this is fine as the initial WG document on this topic.

Luca

Stewart Bryant wrote:

> Is there WG consensus for
>
> Pseudo Wire (PW) OAM Message Mapping
>
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>
> to be accepted as a WG draft?
>
> - Stewart
>
>
> _______________________________________________
> 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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Andrew G. Malis" <andymalis@comcast.net>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Tue, 02 Mar 2004 22:42:55 -0500
Lines: 62
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "'Stewart Bryant '" <stbryant@cisco.com>,
        "'pwe3@ietf.org '" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 04:46:03 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: andymalis@comcast.net@mail.comcast.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
References: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Sasha,

Even if someone is silly enough to propose that (especially since there's a 
1/64K chance that the checksum will match in a random 20-byte bit 
pattern:-), I really don't thing the WG would be silly enough to include it 
in a WG document.  But if you explicitly block this bad idea, people will 
ask why you don't explicitly block other bad ideas as well (and then 
proceed to spend their time thinking up other bad ideas to block).

I'm happy with the text as is

Cheers,
Andy

---------

At 3/3/2004 03:52 AM +0200, Sasha Vainshtein wrote:
>Stewart and all,
>Basically fine, please see a couple of minor comments inline (marked
>[Sasha]).
>
>Regards,
>                  Sasha.
>... snipped ...
>
>5.4.3. PW Packets Aliasing IP Packets
>
>To allow accurate packet inspection in an MPLS PSN, and/or to operate
>correctly over MPLS PSNs that have deployed equal-cost multiple-path
>load-balancing (ECMP), a PW packet must not alias an IP packet.
>[Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.
>IP packets are carried in MPLS label stacks without any protocol
>identifier. The method of packet discrimination must therefore
>be based on some unique characteristic of the IP packet header,
>which PWE3 must not mimic.
>[Sasha] I honestly believe no one will ever propose verifying the cheksum
>[Sasha] of the first 20 bytes after the bottom label as "the unique
>[Sasha] characteristic of the IP packet header". But worse things have
>[Sasha] happened, so maybe we should explicitly block this.
>This is the subject of work in progress.
>
>-----------------------------------------------------
>
>
>9.  IANA considerations
>
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
>
>
>
>
>
>_______________________________________________
>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 04:33:59 +0000
Organization: Cisco Systems, Inc.
Lines: 89
Sender: pwe3-admin@ietf.org
References: <003801c400be$55c44990$805aa8c0@tnadeauvmware>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 05:37:07 2004
Return-path: <pwe3-admin@ietf.org>
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 D. Nadeau" <tnadeau@cisco.com>
In-Reply-To: <003801c400be$55c44990$805aa8c0@tnadeauvmware>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Thomas D. Nadeau wrote:

> 	Stewart,  you are aware that IP
> employs ECMP as well, yes?  

Of course.

> Seems more
> generic to just mention ECMP instead of
> MPLS, or mention MPLS as an example.

But this is an MPLS specific problem we are addressing.

ECMP in an IP network works just fine (provided you
ECMP per flow and not per packet).

BTW ECMP is just one example case of when you need to
discriminate between an IP packet and a non-IP packet
MPLS payload. IPFIX is another case.

- Stewart



> 
> 	--Tom
> 
> 
> 
> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of
> Stewart Bryant
> Sent: Tuesday, March 02, 2004 7:47 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Proposed new 5.4.3 for arch draft
> 
> 
> Here is the proposed change to 5.4.3 that was discussed
> at the WG meeting. Also here is the corresponding change
> to section 9.
> 
> The arch draft will become informational, and
> I will post a pre-draft of the full document with all
> the 07 changes incorporated some time next week.
> 
> Please consider this the start of a two week last
> call on this change.
> 
> I will put together a draft for the CW text in the
> next few days.
> 
> - Stewart
> ---------------------------------------------------
> 
> 
> 5.4.3. PW Packets Aliasing IP Packets
> 
> To allow accurate packet inspection in an MPLS PSN, and/or to operate
> correctly over MPLS PSNs that have deployed equal-cost multiple-path
> load-balancing (ECMP), a PW packet must not alias an IP packet. IP
> packets are carried in MPLS label stacks without any protocol
> identifier. he method of packet discrimination must therefore be based
> on some unique characteristic of the IP packet header, which PWE3 must
> not mimic.T
> 
> This is the subject of work in progress.
> 
> -----------------------------------------------------
> 
> 
> 9.  IANA considerations
> 
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 04:43:51 +0000
Organization: Cisco Systems, Inc.
Lines: 61
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "'pwe3@ietf.org '" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 05:47:03 2004
Return-path: <pwe3-admin@ietf.org>
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: Sasha Vainshtein <Sasha@AXERRA.com>
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E1059@TLV1>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Sasha Vainshtein wrote:

> Stewart and all,
> Basically fine, please see a couple of minor comments inline (marked
> [Sasha]).
> 
> Regards,
>                  Sasha. 
> ... snipped ...
> 
> 5.4.3. PW Packets Aliasing IP Packets
> 
> To allow accurate packet inspection in an MPLS PSN, and/or to operate
> correctly over MPLS PSNs that have deployed equal-cost multiple-path
> load-balancing (ECMP), a PW packet must not alias an IP packet.

> [Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.

The draft is going to be informational, so no capitals. This needs
to get fixed in the rest of the document.

> IP packets are carried in MPLS label stacks without any protocol
> identifier. The method of packet discrimination must therefore
> be based on some unique characteristic of the IP packet header,
> which PWE3 must not mimic.
> [Sasha] I honestly believe no one will ever propose verifying the cheksum
> [Sasha] of the first 20 bytes after the bottom label as "the unique
> [Sasha] characteristic of the IP packet header". But worse things have
> [Sasha] happened, so maybe we should explicitly block this.

If we start to define the solution here, we risk delaying the
draft. My thought was to use the most open definition possible and
thereby minimise the debate, both here and at IESG review.

The checksum solution does not work - there is still the 1/64K chance
of a clash.

- Stewart

> This is the subject of work in progress.
> 
> -----------------------------------------------------
> 
> 
> 9.  IANA considerations
> 
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 04:53:13 +0000
Organization: Cisco Systems, Inc.
Lines: 75
Sender: pwe3-admin@ietf.org
References: <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 05:56:04 2004
Return-path: <pwe3-admin@ietf.org>
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: Alia Atlas <aatlas@avici.com>
In-Reply-To: <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Alia Atlas wrote:

> At 08:52 PM 3/2/2004, Sasha Vainshtein wrote:
> 
>> Stewart and all,
>> Basically fine, please see a couple of minor comments inline (marked
>> [Sasha]).
>>
>> Regards,
>>                  Sasha.
>> ... snipped ...
>>
>> 5.4.3. PW Packets Aliasing IP Packets
>>
>> To allow accurate packet inspection in an MPLS PSN, and/or to operate
>> correctly over MPLS PSNs that have deployed equal-cost multiple-path
>> load-balancing (ECMP), a PW packet must not alias an IP packet.
>> [Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.
>> IP packets are carried in MPLS label stacks without any protocol
>> identifier. The method of packet discrimination must therefore
>> be based on some unique characteristic of the IP packet header,
>> which PWE3 must not mimic.
>> [Sasha] I honestly believe no one will ever propose verifying the cheksum
>> [Sasha] of the first 20 bytes after the bottom label as "the unique
>> [Sasha] characteristic of the IP packet header". But worse things have
>> [Sasha] happened, so maybe we should explicitly block this.
> 
> 
> The checksum is legitimate to consider as a verification, if one doesn't 
> want to depend on just the first nibble.
> 

However the primary decision is surely the first nibble, because
checksum is still ambiguous.

Once you think that you have an IP packet, then the normal IP
verificatuon rules apply, and surely we can just point to RFC 791
for how to parse an IP packet rather than spell it out in our
work?

- Stewart


> Alia
> 
>> This is the subject of work in progress.
>>
>> -----------------------------------------------------
>>
>>
>> 9.  IANA considerations
>>
>>     IANA considerations will be identified in the PWE3 documents that
>>     define the PWE3 encapsulation, control and management protocols.
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 04:57:22 +0000
Organization: Cisco Systems, Inc.
Lines: 76
Sender: pwe3-admin@ietf.org
References: <40452AF2.3000802@cisco.com> <40454307.EEBA383@alcatel.com>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 06:01:03 2004
Return-path: <pwe3-admin@ietf.org>
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: Mustapha Aissaoui <mustapha.aissaoui@alcatel.com>
In-Reply-To: <40454307.EEBA383@alcatel.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Mustapha Aissaoui wrote:

> Stewart,
> see a question below.
> 
> Mustapha.
> --------------
> Stewart Bryant wrote:
> 
>>Here is the proposed change to 5.4.3 that was discussed
>>at the WG meeting. Also here is the corresponding change
>>to section 9.
>>
>>The arch draft will become informational, and
>>I will post a pre-draft of the full document with all
>>the 07 changes incorporated some time next week.
>>
>>Please consider this the start of a two week last
>>call on this change.
>>
>>I will put together a draft for the CW text in the
>>next few days.
>>
>>- Stewart
>>---------------------------------------------------
>>
>>5.4.3. PW Packets Aliasing IP Packets
>>
>>To allow accurate packet inspection in an MPLS PSN, and/or to operate
>>correctly over MPLS PSNs that have deployed equal-cost multiple-path
>>load-balancing (ECMP), a PW packet must not alias an IP packet.
>>IP packets are carried in MPLS label stacks without any protocol
>>identifier. The method of packet discrimination must therefore
>>be based on some unique characteristic of the IP packet header,
>>which PWE3 must not mimic.
>>
>>This is the subject of work in progress.
> 
> 
> MA> I am not clear about the impact of the above paragraph on the
> rest of Section 5.4.3 and on Section 5.4.4. I understand that option
> 3 in your presentation Monday proposes a separate "PWE3 control word
> registry" which will not allow values of 4 and 6. If so, why it that
> not sufficient? 

It replaces 5.4.3 and 5.4.4 gets deleted.

> Why add that "the method of discrimination should be based on some
> unique characteristic of the IP packet header"? 

The plan is to make the Arch draft as uncontroversial as possible
in this area so as to allow it to get though review and unblock the
other drafts. Hence I was trying not to prejudge the solution here.
Hence the non-specific language.

- Stewart


>  
> 
>>-----------------------------------------------------
>>
>>9.  IANA considerations
>>
>>    IANA considerations will be identified in the PWE3 documents that
>>    define the PWE3 encapsulation, control and management protocols.
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Alia Atlas <aatlas@avici.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 00:07:13 -0500
Lines: 54
Sender: pwe3-admin@ietf.org
References: <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com>
 <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com> <404564B9.8040108@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 06:08:04 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: aatlas@pop.avici.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: stbryant@cisco.com
In-Reply-To: <404564B9.8040108@cisco.com>
References: <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com>
 <5.1.0.14.2.20040302210910.01d45a70@pop.avici.com>
X-Avici-MailScanner-Information: Please contact the ISP for more information
X-Avici-MailScanner: Found to be clean
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

At 11:53 PM 3/2/2004, Stewart Bryant wrote:


>Alia Atlas wrote:
>>
>>The checksum is legitimate to consider as a verification, if one doesn't 
>>want to depend on just the first nibble.
>
>However the primary decision is surely the first nibble, because
>checksum is still ambiguous.

Yes, absolutely.

>Once you think that you have an IP packet, then the normal IP
>verificatuon rules apply, and surely we can just point to RFC 791
>for how to parse an IP packet rather than spell it out in our
>work?

Sounds fine to me.  I was objecting to having it explicitly ruled out as an 
additional verification.

Alia


>- Stewart
>
>
>>Alia
>>
>>>This is the subject of work in progress.
>>>
>>>-----------------------------------------------------
>>>
>>>
>>>9.  IANA considerations
>>>
>>>     IANA considerations will be identified in the PWE3 documents that
>>>     define the PWE3 encapsulation, control and management protocols.
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Orly Nicklass" <orly_n@rad.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Date: Mon, 1 Mar 2004 08:59:18 +0200
Lines: 25
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Mon Mar 01 08:02:20 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3LvgABiXMg
To: <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
Hi All,=20

Following my presentation today in Seoul,=20
http://www.dspcsp.com/tdmoip/draft-orly-pwe3-satop-mib-00.txt

http://www.dspcsp.com/tdmoip/draft-orly-pwe3-TDM-mib-00.txt

I would like to proceed with a proposal to progress the drafts as
Working Group items.=20
Please comment.=20
=20

Orly Nicklass, PhD
Associate VP R&D,
RAD Data Communications Ltd,
24 Raoul Wallenberg St.
Tel Aviv, 69719, Israel
Tel : +972 3 765 9969; Fax : +972 3 644 0930
email: orly_n@rad.com
RAD's web site : www.rad.com



=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Tue, 2 Mar 2004 21:13:37 -0800
Lines: 63
Sender: pwe3-admin@ietf.org
References: <40452AF2.3000802@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Wed Mar 03 06:16:07 2004
Return-path: <pwe3-admin@ietf.org>
To: <stbryant@cisco.com>, <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <40452AF2.3000802@cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart,

Do you want to change to the following section 5.4.4, or intend to leave
it as is?

Thanks
Ron

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
> Behalf Of Stewart Bryant
> Sent: Tuesday, March 02, 2004 4:47 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Proposed new 5.4.3 for arch draft
> 
> 
> Here is the proposed change to 5.4.3 that was discussed
> at the WG meeting. Also here is the corresponding change
> to section 9.
> 
> The arch draft will become informational, and
> I will post a pre-draft of the full document with all
> the 07 changes incorporated some time next week.
> 
> Please consider this the start of a two week last
> call on this change.
> 
> I will put together a draft for the CW text in the
> next few days.
> 
> - Stewart
> ---------------------------------------------------
> 
> 
> 5.4.3. PW Packets Aliasing IP Packets
> 
> To allow accurate packet inspection in an MPLS PSN, and/or to operate
> correctly over MPLS PSNs that have deployed equal-cost multiple-path
> load-balancing (ECMP), a PW packet must not alias an IP packet.
> IP packets are carried in MPLS label stacks without any protocol
> identifier. The method of packet discrimination must therefore
> be based on some unique characteristic of the IP packet header,
> which PWE3 must not mimic.
> 
> This is the subject of work in progress.
> 
> -----------------------------------------------------
> 
> 
> 9.  IANA considerations
> 
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 05:21:01 +0000
Organization: Cisco Systems, Inc.
Lines: 81
Sender: pwe3-admin@ietf.org
References: <000601c400de$4b744fb0$e9e325da@lycium.net>
Reply-To: stbryant@cisco.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-admin@ietf.org Wed Mar 03 06:24:04 2004
Return-path: <pwe3-admin@ietf.org>
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: <000601c400de$4b744fb0$e9e325da@lycium.net>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Ron Cohen wrote:

> Stewart,
> 
> Do you want to change to the following section 5.4.4, or intend to leave
> it as is?

5.4.4 should be deleted. 5.4.4 does not make any sense if 5.4.3 is
modified as suggested.

The text that was formally Arch 5.3.4 and 5.4.4  would then be
the starting point for the new draft.

- Stewart

> 
> Thanks
> Ron
> 
> 
>>-----Original Message-----
>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
>>Behalf Of Stewart Bryant
>>Sent: Tuesday, March 02, 2004 4:47 PM
>>To: pwe3@ietf.org
>>Subject: [PWE3] Proposed new 5.4.3 for arch draft
>>
>>
>>Here is the proposed change to 5.4.3 that was discussed
>>at the WG meeting. Also here is the corresponding change
>>to section 9.
>>
>>The arch draft will become informational, and
>>I will post a pre-draft of the full document with all
>>the 07 changes incorporated some time next week.
>>
>>Please consider this the start of a two week last
>>call on this change.
>>
>>I will put together a draft for the CW text in the
>>next few days.
>>
>>- Stewart
>>---------------------------------------------------
>>
>>
>>5.4.3. PW Packets Aliasing IP Packets
>>
>>To allow accurate packet inspection in an MPLS PSN, and/or to operate
>>correctly over MPLS PSNs that have deployed equal-cost multiple-path
>>load-balancing (ECMP), a PW packet must not alias an IP packet.
>>IP packets are carried in MPLS label stacks without any protocol
>>identifier. The method of packet discrimination must therefore
>>be based on some unique characteristic of the IP packet header,
>>which PWE3 must not mimic.
>>
>>This is the subject of work in progress.
>>
>>-----------------------------------------------------
>>
>>
>>9.  IANA considerations
>>
>>    IANA considerations will be identified in the PWE3 documents that
>>    define the PWE3 encapsulation, control and management protocols.
>>
>>
>>
>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 07:23:17 +0200
Lines: 75
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: "''pwe3@ietf.org ' '" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 06:28:04 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Stewart Bryant '" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart and all,
Please see inline.
Regards,
                Sasha 

-----Original Message-----
From: Stewart Bryant
To: Sasha Vainshtein
Cc: 'pwe3@ietf.org '
Sent: 3/3/2004 6:43 AM
Subject: Re: [PWE3] Proposed new 5.4.3 for arch draft



Sasha Vainshtein wrote:

> Stewart and all,
> Basically fine, please see a couple of minor comments inline (marked
> [Sasha]).
> 
> Regards,
>                  Sasha. 
> ... snipped ...
> 
> 5.4.3. PW Packets Aliasing IP Packets
> 
> To allow accurate packet inspection in an MPLS PSN, and/or to operate
> correctly over MPLS PSNs that have deployed equal-cost multiple-path
> load-balancing (ECMP), a PW packet must not alias an IP packet.

> [Sasha] IMO it should be MUST NOT or, probably, SHOULD NOT.

The draft is going to be informational, so no capitals. This needs
to get fixed in the rest of the document.
[Sasha] Is the requirements draftthe Standards Track? 
[Sasha] (There is lots of capitalized MUSTs there:-).
> IP packets are carried in MPLS label stacks without any protocol
> identifier. The method of packet discrimination must therefore
> be based on some unique characteristic of the IP packet header,
> which PWE3 must not mimic.
> [Sasha] I honestly believe no one will ever propose verifying the
cheksum
> [Sasha] of the first 20 bytes after the bottom label as "the unique
> [Sasha] characteristic of the IP packet header". But worse things have
> [Sasha] happened, so maybe we should explicitly block this.

If we start to define the solution here, we risk delaying the
draft. My thought was to use the most open definition possible and
thereby minimise the debate, both here and at IESG review.

The checksum solution does not work - there is still the 1/64K chance
of a clash.

- Stewart

> This is the subject of work in progress.
> 
> -----------------------------------------------------
> 
> 
> 9.  IANA considerations
> 
>     IANA considerations will be identified in the PWE3 documents that
>     define the PWE3 encapsulation, control and management protocols.
> 
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Tue, 2 Mar 2004 21:55:52 -0800
Lines: 98
Sender: pwe3-admin@ietf.org
References: <40456B3D.5020009@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 07:00:35 2004
Return-path: <pwe3-admin@ietf.org>
To: <stbryant@cisco.com>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <40456B3D.5020009@cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart,

There are many follow-up question related to other parts of the draft
(e.g. fig 11 changes). It might be better to wait for you to send the
modified draft to the list and not comment only on section 5.4.3 text. 

Thanks
Ron



> > Stewart,
> > 
> > Do you want to change to the following section 5.4.4, or 
> intend to leave
> > it as is?
> 
> 5.4.4 should be deleted. 5.4.4 does not make any sense if 5.4.3 is
> modified as suggested.
> 
> The text that was formally Arch 5.3.4 and 5.4.4  would then be
> the starting point for the new draft.
> 
> - Stewart
> 
> > 
> > Thanks
> > Ron
> > 
> > 
> >>-----Original Message-----
> >>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
> >>Behalf Of Stewart Bryant
> >>Sent: Tuesday, March 02, 2004 4:47 PM
> >>To: pwe3@ietf.org
> >>Subject: [PWE3] Proposed new 5.4.3 for arch draft
> >>
> >>
> >>Here is the proposed change to 5.4.3 that was discussed
> >>at the WG meeting. Also here is the corresponding change
> >>to section 9.
> >>
> >>The arch draft will become informational, and
> >>I will post a pre-draft of the full document with all
> >>the 07 changes incorporated some time next week.
> >>
> >>Please consider this the start of a two week last
> >>call on this change.
> >>
> >>I will put together a draft for the CW text in the
> >>next few days.
> >>
> >>- Stewart
> >>---------------------------------------------------
> >>
> >>
> >>5.4.3. PW Packets Aliasing IP Packets
> >>
> >>To allow accurate packet inspection in an MPLS PSN, and/or 
> to operate
> >>correctly over MPLS PSNs that have deployed equal-cost multiple-path
> >>load-balancing (ECMP), a PW packet must not alias an IP packet.
> >>IP packets are carried in MPLS label stacks without any protocol
> >>identifier. The method of packet discrimination must therefore
> >>be based on some unique characteristic of the IP packet header,
> >>which PWE3 must not mimic.
> >>
> >>This is the subject of work in progress.
> >>
> >>-----------------------------------------------------
> >>
> >>
> >>9.  IANA considerations
> >>
> >>    IANA considerations will be identified in the PWE3 
> documents that
> >>    define the PWE3 encapsulation, control and management protocols.
> >>
> >>
> >>
> >>
> >>
> >>_______________________________________________
> >>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 08:42:44 +0200
Lines: 13
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 03 07:46:05 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQAuWsh6RRLr4cpQou73gbAjvGSswAL4WEg
To: <stbryant@cisco.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart

Why don't you try something easier?

For MPLS PSNs there is an additional constraint on the PW packet format.
In order to facilitate proper functioning of LSRs that detect IP packets
based=20
on the initial four bits of the packet content,=20
these bits in PW packets must not alias IP version numbers.

The use of this field for PWs is work in progress.

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 06:50:48 +0000
Organization: Cisco Systems, Inc.
Lines: 24
Sender: pwe3-admin@ietf.org
References: <27A0F290348F8E45AEF79889DDE65A52022C3DA0@exrad2.ad.rad.co.il>
Reply-To: stbryant@cisco.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-admin@ietf.org Wed Mar 03 07:54:02 2004
Return-path: <pwe3-admin@ietf.org>
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: Yaakov Stein <yaakov_s@rad.com>
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52022C3DA0@exrad2.ad.rad.co.il>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



Yaakov Stein wrote:

> Stewart
> 
> Why don't you try something easier?
> 
> For MPLS PSNs there is an additional constraint on the PW packet format.
> In order to facilitate proper functioning of LSRs that detect IP packets
> based 
> on the initial four bits of the packet content, 
> these bits in PW packets must not alias IP version numbers.
> 
> The use of this field for PWs is work in progress.
> 

I would be happy with that text.

- Stewart

> Y(J)S
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Wed, 3 Mar 2004 08:52:38 +0200
Lines: 31
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 03 07:56:02 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Pseudo Wire (PW) OAM Message Mapping
Thread-Index: AcP/pQJY9niE81PFQR+xZYmRGzq0CAAARDywAFFDi5A=
To: "Monique Morrow \(mmorrow\)" <mmorrow@cisco.com>,
        "Stewart" <stbryant@cisco.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Monique,=20

Now that the treatment has been limited to network interworking
I support using this draft as a starting point for PWE's OAM work.

I agree with Shahram that the title should be PW OAM interworking.

I strongly suggest trying to harmonize this work with that being
performed in ITU-T Q3/13.

I would be happy to help fill in the TBD in the section on TDM
Encapsulation.

Y(J)S

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Sunday, February 29, 2004 11:15 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping
>=20
>=20
> Is there WG consensus for
>=20
> Pseudo Wire (PW) OAM Message Mapping
>
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Wed, 3 Mar 2004 07:55:49 +0100
Lines: 44
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "Stewart Bryant (stbryant)" <stbryant@cisco.com>, <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 07:59:02 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: [PWE3] Pseudo Wire (PW) OAM Message Mapping
Thread-Index: AcP/pQJY9niE81PFQR+xZYmRGzq0CAAARDywAFFDi5AAAElPUA==
To: "Yaakov Stein" <yaakov_s@rad.com>
X-OriginalArrivalTime: 03 Mar 2004 06:55:50.0364 (UTC) FILETIME=[9021E9C0:01C400EC]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Cool -- looking forward to collaborating with you Yaakov!

All the best,

/Monique

-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: 03 March 2004 07:53
To: Monique Morrow (mmorrow); Stewart Bryant (stbryant); pwe3@ietf.org
Subject: RE: [PWE3] Pseudo Wire (PW) OAM Message Mapping


Monique,=20

Now that the treatment has been limited to network interworking
I support using this draft as a starting point for PWE's OAM work.

I agree with Shahram that the title should be PW OAM interworking.

I strongly suggest trying to harmonize this work with that being
performed in ITU-T Q3/13.

I would be happy to help fill in the TBD in the section on TDM
Encapsulation.

Y(J)S

> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Sunday, February 29, 2004 11:15 PM
> To: pwe3@ietf.org
> Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping
>=20
>=20
> Is there WG consensus for
>=20
> Pseudo Wire (PW) OAM Message Mapping
>
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 10:37:32 -0000
Lines: 14
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 11:41:17 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQA2piV04hPL4aASi+LJXa51QgRqgALxj1Q
To: <stbryant@cisco.com>, <Sasha@AXERRA.com>
X-OriginalArrivalTime: 03 Mar 2004 10:37:32.0715 (UTC) FILETIME=[88F397B0:01C4010B]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart Bryant wrote 03 March 2004 04:44
<snip>

> The checksum solution does not work - there is still the 1/64K chance
> of a clash.

NH=3D>Is there not always a possibility of a mistake here if undetected =
errors affect the 1st nibble solution?  Though I guess if this was =
*always* followed up by a checksum test (for *both* assumed IP client =
and assumed X (PW) client cases) this would at least verify/refute the =
case (subject to a further 1/64k prob of error).  If 1st nibble neither =
case then bin?

regards, Neil


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 10:37:30 -0000
Lines: 34
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 11:41:22 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQA2U0t2ORrTbBVQCOofPbhRPKVKQALSGYw
To: <stbryant@cisco.com>, <tnadeau@cisco.com>
X-OriginalArrivalTime: 03 Mar 2004 10:37:31.0718 (UTC) FILETIME=[885B7660:01C4010B]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart Bryant wrote 03 March 2004 04:34
> Thomas D. Nadeau wrote:
>=20
> > 	Stewart,  you are aware that IP
> > employs ECMP as well, yes? =20
>=20
> Of course.
>=20
> > Seems more
> > generic to just mention ECMP instead of
> > MPLS, or mention MPLS as an example.
>=20
> But this is an MPLS specific problem we are addressing.
NH=3D> Don't want to labour this one but.....if you think about what you =
are saying here Stewart, this is yet another example of why MPLS is not =
the same as IP.
>=20
> ECMP in an IP network works just fine (provided you
> ECMP per flow and not per packet).
NH=3D> I agree with Stewart here.  Load balancing is fine within a =
single layer network (any)....I believe its called TE ;-).  The problems =
occur when folks try and load balance over nested layered networks.  So =
if you start peeking inside the payload area of *any* layer network (I =
could apply this to SDH or OTNs in principle) to see what the clients =
are then you can expect problems.  This another consequence of mp2p LDP =
due to this just doing SPF routing.  Even our IP design teams wish ECMP =
did not exist in MPLS (esp when one considers all the fault-management =
problems it creates too).

As an aside, I think we ought to be looking for solutions that don't =
promulgate past errors of judgement....if we can find any of course.

regards, Neil
<snipped>


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and dra
	ft-orly-pwe3-tdm-mib
Date: Mon, 1 Mar 2004 09:03:21 +0200
Lines: 51
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Mon Mar 01 08:08:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Orly Nicklass'" <orly_n@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

I support this proposal.

----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com <mailto:sasha@axerra.com> 
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)


> -----Original Message-----
> From: Orly Nicklass [mailto:orly_n@rad.com]
> Sent: Monday, March 01, 2004 8:59 AM
> To: pwe3@ietf.org
> Subject: RE: [PWE3] Proposal to Progress 
> draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
> 
> 
>  
> Hi All, 
> 
> Following my presentation today in Seoul, 
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-satop-mib-00.txt
> 
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-TDM-mib-00.txt
> 
> I would like to proceed with a proposal to progress the drafts as
> Working Group items. 
> Please comment. 
>  
> 
> Orly Nicklass, PhD
> Associate VP R&D,
> RAD Data Communications Ltd,
> 24 Raoul Wallenberg St.
> Tel Aviv, 69719, Israel
> Tel : +972 3 765 9969; Fax : +972 3 644 0930
> email: orly_n@rad.com
> RAD's web site : www.rad.com
> 
> 
> 
>  
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: neil.2.harrison@bt.com
Subject: RE: Pseudo Wire (PW) OAM Message Mapping
Date: Wed, 3 Mar 2004 10:37:29 -0000
Lines: 119
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <Maarten.Vissers@alcatel.de>, <alan.mcguire@bt.com>
X-From: pwe3-admin@ietf.org Wed Mar 03 11:41:25 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Pseudo Wire (PW) OAM Message Mapping
Thread-Index: AcP/pQJY9niE81PFQR+xZYmRGzq0CAAARDywAFFDi5AAAu8P8A==
To: <yaakov_s@rad.com>, <mmorrow@cisco.com>, <stbryant@cisco.com>,
        <pwe3@ietf.org>
X-OriginalArrivalTime: 03 Mar 2004 10:37:29.0623 (UTC) FILETIME=[871BCA70:01C4010B]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi Yaakov.....I am also generally OK with these restrictions now.  But =
let me just remind folks of the correct arch interpretation of 'network =
i/w' (which is an awful term IMO.....I think we should try and encourage =
folks to use the term 'client/server i/w'):

1.	the client and server layers must be independent in all =
aspects.....this applies to the data-plane, control-plane and =
management-plane;
2.	the client (all aspects, not just the traffic's data-plane) should be =
carried transparently over the server layer;
3.	defects detected at the server layer's trail termination point should =
be mapped (at the server->client adaptation function) to the client =
layer's semantic/syntax for FDI (Forward Defect Indication) in =
each/every client layer signal that is affected.

Note - I have used word 'should' above in rules 2 and 3 because not all =
cases will be satisfied for several reasons.  For example:
-	some clients don't (for historical reasons) have the required =
data-plane FDI function (or more general OAM functions), eg FR;
-	I know some folks will break (and indeed already have broken) these =
rules.....now this might be OK providing all parties affected understand =
and accept the consequences of doing this, but for some organisations =
these consequences might not be acceptable.

Why do we need these rules?

In case of 1, the most obvious reason is when the client and server =
layers are owned by different operating parties....so this is not just a =
technical requirement, it is an essential commercial requirement.  A =
further (more technical) reason is to allow independent protocol (in any =
plane) addition/change/removal.

In the case of 2, we don't want the server layer (at some =
client<->server adaptation point) to be terminating/processing specific =
client layer characteristic information (CI).  Moreover, client BW =
squeezing is not a key requirement, reducing complexity and opex costs =
are however.

In the case of 3, the primary intention is to prevent operational folks =
chasing inappropriate alarm indications, ie the key purpose of FDI is to =
tell higher layer clients that the failure lies in a lower layer =
network.  Note that this is a recursive behaviour upwards into any =
further higher layer layer networks that are supported.  Unless this is =
addressesd the inappropriate reporting of alarms can be geographically =
and organisationally widespread.  Finally, note that FDI should ideally =
be an OAM function of the data-plane because (i) trails may be set-up by =
NMS and not a signalling protocol and (ii) the indications should work =
even if the signalling function is not working.

Note the above is effectively embodied within G.805/809 (though these =
cover more than this, eg same-layer partitioning).  G.805/809 are =
generic for the 3 networking modes. Specific technologies are covered in =
their own Recs, eg ethernet is described in G.8010, and one of my =
colleagues is currently modelling the various flavours of MPLS.

One of the key issues to address when considering these client/server =
relationships are the 2 end-stops of the recursion.  One occurs at the =
bottom of the stack in terms of the 'physicals' (this is easy to deal =
with) and one occurs at the top of the stack where we have to interface =
to applications (this is harder to deal with).  We do not, as yet, have =
a common adaptation function agreed that has all the right properties =
for all cases.....and it is something we, as an industry, need to better =
understand and address.  To date each technology has done its own thing =
here.  This is also the key problem for properly coming to terms with =
(the so-called, again badly IMO) 'service i/w' case.  I will say no more =
on this here, though its something that needs considering by both IETF =
and ITU folks.....and I agree with Yaakov below when he urges that we =
should try and work together as an industry on this (though I also urge =
that we all should try and use G.805/809, as this is the starting point =
of achieving such a better understanding of what is really going on).

regards, Neil

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org]On Behalf Of
> Yaakov Stein
> Sent: 03 March 2004 06:53
> To: Monique Morrow (mmorrow); Stewart; pwe3@ietf.org
> Subject: RE: [PWE3] Pseudo Wire (PW) OAM Message Mapping
>=20
>=20
> Monique,=20
>=20
> Now that the treatment has been limited to network interworking
> I support using this draft as a starting point for PWE's OAM work.
>=20
> I agree with Shahram that the title should be PW OAM interworking.
>=20
> I strongly suggest trying to harmonize this work with that being
> performed in ITU-T Q3/13.
>=20
> I would be happy to help fill in the TBD in the section on TDM
> Encapsulation.
>=20
> Y(J)S
>=20
> > -----Original Message-----
> > From: Stewart Bryant [mailto:stbryant@cisco.com]
> > Sent: Sunday, February 29, 2004 11:15 PM
> > To: pwe3@ietf.org
> > Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping
> >=20
> >=20
> > Is there WG consensus for
> >=20
> > Pseudo Wire (PW) OAM Message Mapping
> >
> http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-
map-04.txt

to be accepted as a WG draft?

- Stewart


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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed new 5.4.3 for arch draft
Date: Wed, 03 Mar 2004 11:24:46 +0000
Organization: Cisco Systems, Inc.
Lines: 41
Sender: pwe3-admin@ietf.org
References: <0536FC9B908BEC4597EE721BE6A3538904EF333C@i2km07-ukbr.domain1.systemhost.net>
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 12:28:03 2004
Return-path: <pwe3-admin@ietf.org>
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: neil.2.harrison@bt.com
In-Reply-To: <0536FC9B908BEC4597EE721BE6A3538904EF333C@i2km07-ukbr.domain1.systemhost.net>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



neil.2.harrison@bt.com wrote:

> Stewart Bryant wrote 03 March 2004 04:44
> <snip>
> 
>>The checksum solution does not work - there is still the 1/64K chance
>>of a clash.
> 
> 
> NH=>Is there not always a possibility of a mistake here if 
   undetected errors affect the 1st nibble solution?

Yes

   Though
   I guess if this was *always* followed up by a checksum test
   (for *both* assumed IP client and assumed X (PW) client cases)
   this would at least verify/refute the case (subject to a
   further 1/64k prob of error).  If 1st nibble neither case
   then bin?

I think that it would be better to leave it to the application
to decide how important it is to trap undetected datalink and
memory error. If it is important, then check the checksum (not
that the checksum is a very strong check) otherwise don't.
The point about the nibble vs the checksum is that if we control
the nibble, the application gets to choose the certainty of
identification.


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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 13:36:29 +0200
Lines: 48
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 03 12:40:13 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQA2U0t2ORrTbBVQCOofPbhRPKVKQALSGYwAALeN9A=
To: <neil.2.harrison@bt.com>, <stbryant@cisco.com>, <tnadeau@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> > > Seems more generic to just mention ECMP instead of MPLS, or
mention MPLS as an=20
> > > example.
> >=20
> > But this is an MPLS specific problem we are addressing.

> NH=3D> Don't want to labour this one but.....if you think about=20
> what you are saying here Stewart, this is yet another example=20
> of why MPLS is not the same as IP.
> >=20
> > ECMP in an IP network works just fine (provided you ECMP per flow
and=20
> > not per packet).

> NH=3D> I agree with Stewart here.  Load balancing is fine=20
> within a single layer network (any)....I believe its called=20
> TE ;-).  The problems occur when folks try and load balance=20
> over nested layered networks.  So if you start peeking inside=20
> the payload area of *any* layer network (I could apply this=20
> to SDH or OTNs in principle) to see what the clients are then=20
> you can expect problems.  This another consequence of mp2p=20
> LDP due to this just doing SPF routing.  Even our IP design=20
> teams wish ECMP did not exist in MPLS (esp when one considers=20
> all the fault-management problems it creates too).

Isn't it refreshing to see Neil agree with Stewart ?

Stewart - It isn't completely clear to me why and how an IP network
performs load balancing on a per-flow rather than per-packet basis.
Is this done by IP source and destination address?
What if we have several PWs between these two IP addresses?

Neil - One of the initial justifications of MPLS was to solve
the IP equal-cost problem. Of course this could be done
by only allowing MPLS-TE solutions, and that may be what operators
like yourself need.=20

But there are a lot of best-effort uses for MPLS as well,=20
and these shouldn't have to suffer from overloaded links
when there are underloaded ones available.=20
Admittedly peaking into client layer headers is a hack,
but it is such a useful one that it may qualify as one of those
rare exceptions where the rules can be broken
(or better, the MPLS rules should be modified by adding a type
identifier).

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: =?iso-8859-1?Q?Bj=F6rn_Bergl=F6f?= <Bjorn.Berglof@xelerated.com>
Subject: 16 bit interpretation of sequence checking?
Date: Wed, 3 Mar 2004 12:38:33 +0100
Lines: 68
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 03 12:42:03 2004
Return-path: <pwe3-admin@ietf.org>
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Thread-Topic: 16 bit interpretation of sequence checking?
Thread-Index: AcQBFA8kEjiwrm9ETLecIQN4cUdj3A==
To: <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


BACKGROUND:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
In "draft-ietf-pwe3-atm-encap-04.txt" section 4.3.4 describes
the sequence number processing as:
     =
----------------------------------------------------------------------
     - if the sequence number on the packet is 0, then the packet passes
       the sequence number check.

     - otherwise if the packet sequence number >=3D the expected =
sequence
       number and the packet sequence number - the expected sequence
       number < 32768, then the packet is in order.

     - otherwise if the packet sequence number < the expected sequence
       number and the expected sequence number - the packet sequence
       number >=3D 32768, then the packet is in order.

     - otherwise the packet is out of order.

   If a packet is in order then, it can be delivered immediately. If the
   packet is in order, then the expected sequence number MUST be set
   using the algorithm:

   expected_sequence_number :=3D packet_sequence_number + 1 mod 2**16
   if (expected_sequence_number =3D 0) then expected_sequence_number:=3D =
1;
     =
----------------------------------------------------------------------

QUESTION 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Is "the packet passes the sequence number check" the same as=20
"the packet is in order" ? I.e, Should the expected_sequence_number
be updated if the sequence number i 0 ?

QUESTION 2:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I enterpret this rather complex description above as a way to map 16 bit =

behaviour into a 32 bit environment. As a hardware designer I have=20
a hard time convincing myself (and others) that the above is equivalent=20
to the following psueudo-code:

      diff =3D SeqNo - ExpNo;
      if ((SeqNo=3D0) or (diff[15]=3D0) then OK;
      else NOT_OK;
      end if;
      if OK then NewExpNo =3D (SeqNo=3DFFFF) ? 1 : SeqNo+1;
      end if;

where all variables are 16 bit and count operations allow wrap-around.
All comments are appreciated.
      / Bj=F6rn


     =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    / Bj=F6rn 'Mr Bear' Bergl=F6f
   /  Xelerated:   08  - 506 257 94  mailto:bjorn.berglof@xelerated.com
  /   Mobile:      0733- 277 808     http://www.mrbear.se
 /    Home office: 08  - 532 532 69  mailto:bjorn@mrbear.se
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: 16 bit interpretation of sequence checking?
Date: Wed, 3 Mar 2004 15:46:29 +0200
Lines: 54
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 03 14:49:07 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] 16 bit interpretation of sequence checking?
Thread-Index: AcQBFA8kEjiwrm9ETLecIQN4cUdj3AAEDGSQ
To: "Bj?rn Bergl?f" <Bjorn.Berglof@xelerated.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

> QUESTION 1:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Is "the packet passes the sequence number check" the same as=20
> "the packet is in order" ? I.e, Should the=20
> expected_sequence_number be updated if the sequence number i 0 ?

Passes the sequence number check =3D=3D is in order =3D=3D has not =
arrived
later than a packet sent earlier (although packets may be missing).

If the sequence number is zero, it is IMMEDIATELY incremented
before the test. After the test passes the expected sequence number
is incremented. If the test fails (i.e. the packet received was sent
earlier
than a packet previously received) then the epected number is not
incremented.
=20
> QUESTION 2:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> I enterpret this rather complex description above as a way to=20
> map 16 bit behaviour into a 32 bit environment. As a hardware=20
> designer I have a hard time convincing myself (and others)=20
> that the above is equivalent to the following psueudo-code:
>=20
>       diff =3D SeqNo - ExpNo;
>       if ((SeqNo=3D0) or (diff[15]=3D0) then OK;
>       else NOT_OK;
>       end if;
>       if OK then NewExpNo =3D (SeqNo=3DFFFF) ? 1 : SeqNo+1;
>       end if;
>=20
> where all variables are 16 bit and count operations allow wrap-around.

You are have a hard time because it isn't the same.
You are checking for equality with the next packet number,
while the test in the draft is for equal OR AFTER the expected
sequence number.

Try thinking about it in the following way:

   if received =3D expected then
       treat packet as in-order=20
       set expected =3D (received + 1) mod 2^16
   else
       calculate D =3D ( (expected-received) mod 2^16 ) - 2^15
       if D > 0 then
           packets expected, expected+1, ... received-1 have not been
received=20
           set expected =3D (received + 1) mod 2^16
       else =20
           late packet arrived
           do NOT update expected

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: benjamin.niven-jenkins@bt.com
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Wed, 3 Mar 2004 15:45:52 -0000
Lines: 36
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Wed Mar 03 16:50:19 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQA2U0t2ORrTbBVQCOofPbhRPKVKQALSGYwAALeN9AACMKcYA==
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 03 Mar 2004 15:45:52.0640 (UTC) FILETIME=[9BC42000:01C40136]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

> Neil - One of the initial justifications of MPLS was to solve
> the IP equal-cost problem. Of course this could be done
> by only allowing MPLS-TE solutions, and that may be what operators
> like yourself need.=20
>=20
> But there are a lot of best-effort uses for MPLS as well,=20
> and these shouldn't have to suffer from overloaded links
> when there are underloaded ones available.=20

I maybe missing something but I don't see how using a best-effort =
flavour of MPLS (i.e. any non-P2P non-co-ps mode of MPLS) can really =
solve the IP equal-cost problem when it introduces it's own equal-cost =
problem (because it tracks the IP IGP).  It's just shifting the problem =
to somewhere else in the network stack.

Under what circumstances does a cl-ps best-effort flavour of MPLS add =
value above and beyond what could be achieved using cl-ps best-effort IP =
(I can't think of any)?

> Admittedly peaking into client layer headers is a hack,
> but it is such a useful one that it may qualify as one of those
> rare exceptions where the rules can be broken

Useful to whom?  I would argue that if you consider its full =
implications (including OAM, fault finding/diagnosis, SLA tracking and =
NMS/OSS implications) then it isn't that useful to service providers, =
it's just a complicated pain in the backside.

IMO it's a case of treating the symptoms and not the cause, this is =
further compounded by the additional OAM etc. hacks required to fault =
manage the original ECMP hack.  IMO time would be better spent =
deprecating the hack and concentrating on how to migrate away from it =
than producing new hacks that try and fix the old hacks.


Ben


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed new 5.4.3 for arch draft
Date: Thu, 4 Mar 2004 15:00:40 +0200
Lines: 59
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Thu Mar 04 14:03:06 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed new 5.4.3 for arch draft
Thread-Index: AcQA2U0t2ORrTbBVQCOofPbhRPKVKQALSGYwAALeN9AACMKcYAAsefIA
To: <benjamin.niven-jenkins@bt.com>, <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Ben,=20
=20
> I maybe missing something but I don't see how using a=20
> best-effort flavour of MPLS (i.e. any non-P2P non-co-ps mode=20
> of MPLS) can really solve the IP equal-cost problem when it=20
> introduces it's own equal-cost problem (because it tracks the=20
> IP IGP).  It's just shifting the problem to somewhere else in=20
> the network stack.

What I meant was that one could define the FEC based on more
than just the destination IP address, e.g. using the source IP address
as well. Then the LER could assign a label and solve "fish diagram"
overload problems for best-effort IP.

> Under what circumstances does a cl-ps best-effort flavour of=20
> MPLS add value above and beyond what could be achieved using=20
> cl-ps best-effort IP (I can't think of any)?

Continuing my previous remark, the performance of such a network
is better than an IP ECMP scheme that sends packets along different
routes on a packet-by-packet basis, based only on IP destination
address.

Of course the MPLS network is being used in "CO mode",
even though there is no TE.=20
I really don't know what "CL MPLS" is,
unless you mean that MPLS switches can also forward unlabeled IP
packets,=20
but then they are functioning as an IP routers.

> > Admittedly peaking into client layer headers is a hack, but  it is
such=20
> > a useful one that it may qualify as one of those rare exceptions
where=20
> > the rules can be broken
=20
> Useful to whom?  I would argue that if you consider its full=20
> implications (including OAM, fault finding/diagnosis, SLA=20
> tracking and NMS/OSS implications) then it isn't that useful=20
> to service providers, it's just a complicated pain in the backside.

Once again, I am not forcing you to use ECMP
for well-engineered operator networks with TE.=20
But this mechanism IS useful for best-effort traffic,
and there is an awful lot of best-effort traffic out there.
=20
> IMO it's a case of treating the symptoms and not the cause,=20
> this is further compounded by the additional OAM etc. hacks=20
> required to fault manage the original ECMP hack.  IMO time=20
> would be better spent deprecating the hack and concentrating=20
> on how to migrate away from it than producing new hacks that=20
> try and fix the old hacks.

The question is whether MPLS can still be changed,
e.g. whether it is still possible to add type ECN fields.
However, the PWE list is not the best place to ask that question.


Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: raymond zhang <zhangr@info.net>
Subject: Pseudo Wire (PW) OAM Message Mapping
Date: Thu, 04 Mar 2004 14:23:09 -0800
Lines: 25
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-From: pwe3-admin@ietf.org Fri Mar 05 20:18:07 2004
Return-path: <pwe3-admin@ietf.org>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: pwe3@ietf.org
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Hi,

Yes, this would be fine as a WG doc....

Regards,
Raymond



-----Original Message-----
From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On Behalf Of Stewart
Bryant
Sent: Sunday, February 29, 2004 11:15 PM
To: pwe3@ietf.org
Subject: [PWE3] Pseudo Wire (PW) OAM Message Mapping


Is there WG consensus for

Pseudo Wire (PW) OAM Message Mapping
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

to be accepted as a WG draft?

- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Dimitri.Papadimitriou@alcatel.be
Subject: Re: Pseudo Wire (PW) OAM Message Mapping
Date: Sat, 06 Mar 2004 21:16:28 +0100
Lines: 43
Sender: pwe3-admin@ietf.org
References: <4042B8AF.5060204@cisco.com> <20040301211245.P54800@sapphire.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Stewart Bryant <stbryant@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Sat Mar 06 21:17:13 2004
Return-path: <pwe3-admin@ietf.org>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5) Gecko/20030925
X-Accept-Language: en-us, en
To: Rahul Aggarwal <rahul@juniper.net>
In-Reply-To: <20040301211245.P54800@sapphire.juniper.net>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 03/06/2004 21:14:40,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 03/06/2004 21:14:41,
	Serialize complete at 03/06/2004 21:14:41
X-Alcanet-MTA-scanned-and-authorized: yes
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

rahul, i agree this document provides a reasonable
basis for initiating discussion on this topic -

therefore, yes it should accepted as a wg document

thanks,
- dimitri.

Rahul Aggarwal wrote:
> Hi Stewart,
> 
> On Mon, 1 Mar 2004, Stewart Bryant wrote:
> 
> 
>>Is there WG consensus for
>>
>>Pseudo Wire (PW) OAM Message Mapping
>>http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
>>
>>to be accepted as a WG draft?
>>
> 
> 
> This draft provides a reasonable starting point for bringing this work in
> the WG. Hence yes.
> 
> rahul
> 
> 
>>- Stewart
>>
>>
>>_______________________________________________
>>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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: draft-ietf-pwe3-tdm-requirements-04.txt last call
Date: Mon, 08 Mar 2004 19:21:34 +0000
Organization: Cisco Systems, Inc.
Lines: 8
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 08 20:24:07 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is the start of the two week last call for:

Requirements for Edge-to-Edge Emulation of TDM Circuits
over Packet Switching Networks (PSN)

- Stewart

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-requirements-04.txt


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Date: Mon, 1 Mar 2004 09:29:18 +0200
Lines: 20
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Mon Mar 01 08:32:05 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3LvgABiXMgAAWEpRA=
To: <pwe3@ietf.org>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> Hi All,=20
>=20
> Following my presentation today in Seoul,=20
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-satop-mib-00.txt
>=20
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-TDM-mib-00.txt
>=20
> I would like to proceed with a proposal to progress the=20
> drafts as Working Group items.=20
> Please comment.=20

Of course, I support the proposal.

These MIB drafts need to be standards track.

We will later need MIBs for the two informational drafts
(CESoPSN and TDMoIP).

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Arch draft updated
Date: Tue, 09 Mar 2004 20:15:01 +0000
Organization: Cisco Systems, Inc.
Lines: 143
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Tue Mar 09 21:17:24 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

As presented at IETF59 and mostly as already presented to the
list as individual items I have updated the PWE3 Architecture
description with the changes described below.

The latest version is at

ftp://ftpeng.cisco.com/stbryant/PRE-draft-ietf-pwe3-arch-07.txt

This is the start of a two week last call on the changes which
I describe below. If these changes are acceptable to the WG I
will submit version 07 to ietf-drafts and give the draft back
to the IESG.

- Stewart


--------

1) Changes to remove the references to IP version number
    and detailed control word text:

a) Removed the PWE3 Payload Type Identifier from Fig 11
    which now looks as follows:

    /=====================\
    H Payload Convergence H--+
    H---------------------H  |       +--------------------------------+
    H       Timing        H--------->|              RTP               |
    H---------------------H  |       +--------------------------------+
    H     Sequencing      H--+------>| Flags, Frag, Len, Seq #, etc   |
    \=====================/  |       +--------------------------------+
    |  PW Demultiplexer   |--------->|           PW Label             |
    +---------------------+  |       +--------------------------------+
    |  PSN Convergence    |--+  +--->| Outer Label or MPLS-in-IP encap|
    +---------------------+     |    +--------------------------------+
    |        PSN          |-----+
    +---------------------+
    |      Data-link      |
    +---------------------+
    |       Physical      |
    +---------------------+

      Figure 11: PWE3 over an MPLS PSN using a control word

b) Deleted the following sentence from 5.4.2

Where the design of the control word would alias an IP
packet, a PWE3 Payload Type Identifier (PWE3 PID) should
be interposed between the PW label and the control word (see 5.4.4).


c) Replaced 5.4.3 with the following and deleted 5.4.4

5.4.3. PW-IP Packet Discrimination

    For MPLS PSNs there is an additional constraint on the PW packet
    format.  In order to facilitate proper functioning of label switched
    routers that detect IP packets based on the initial four bits of the
    packet content, these bits in PW packets must not be the same as an
    IP version number in current use.

    The use of this field for PWs is work in progress.


d) Simplified the IANA consideration section to:

    IANA considerations will be identified in the PWE3 documents that
    define the PWE3 encapsulation, control and management protocols.


--------

2) Editorials


a) Deleted the capitalised keyword text which I believe
    to be the normal convention for and arch/framework
    text

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].

b) Changed corresponding main text to lowercase.

c) In Fig 2 changed PW End Service to Access Circuit (outstanding
    edit error from last pass)

--------

3) Reference cleanup

a) Deleted the text:

    For example, this capability is needed in [PPPoL2TP]
    (PPP negotiation has to be split between the two ends of the
    tunnel).  PWE3 may also need this type of control channel to

 From 5.1.2 example 1, which now reads:

    1. A reliable control channel for signaling line events, status
       indications, and, in some exceptional cases, CE-CE events
       that must be translated and sent reliably between PEs.
       PWE3 may need this type of control channel to
       provide faithful emulation of complex data-link protocols.

Reason - PPPoL2TP is a dead reference.


b) Also deleted the reference from the list of references.

c) Brought the references up to the latest revision level


------

4) MIB cleanup following MIB doctor review

    Replaced the MIB text (section 8.2)


------

5) Clean up security section following IESG comments

a) In the security section deleted non-repudiation from the
    following sentence:

IPSec MAY provide authentication, integrity, non-repudiation, and
confidentiality of data transferred between two PEs.

b) In the security section replaced

The access controls that are in place in the PE to
protect and validate its configuration will be sufficient to ensure
that the NSP performs as expected.

with the text:

A PE designed and managed to best current practise
will have controls in place that protect and validate its
configuration and these will be sufficient to ensure that the NSP
behaves as expected.


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: Setup of TDM PWs: Follow-up for the Seoul meeting
Date: Wed, 10 Mar 2004 11:16:27 +0200
Lines: 62
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Cc: "Stewart Bryant (E-mail)" <stbryant@cisco.com>,
        "Danny McPherson (E-mail)" <danny@tcb.net>,
        Alik Shimelmits
	 <alik@AXERRA.com>,
        Sharon Galtzur <sharon@AXERRA.com>,
        "'Riegel Maximilian' (E-mail)" <Maximilian.Riegel@icn.siemens.de>,
        "PWE3 WG (E-mail)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 10 10:22:09 2004
Return-path: <pwe3-admin@ietf.org>
To: "Luca Martini (E-mail)" <lmartini@cisco.com>,
        "Mark Townsley (E-mail)"
	 <townsley@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Luca, Mark and all,
Following my presentation at the Seoul WG session and our discussions there,
I;d like to ask you to update the PWE3 IANA Allocation draft (it expires
in April anyway:-) like following:

1. In Section 2 (PW Type), continume the list of PW Types like following:
...
0x0010   SONET/SDH Circuit Emulation over Packet (CEP) -- this is the last
entry so far
0x0011   Structure-agnostic E1 over Packet (SAToP)
0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP) 
0x0013   Structure-agnostic E3 over Packet (SAToP) 
0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP) 
0x0015   Structure-aware Basic NxDS0 (CESoPSN, TDMoIP)
0x0016   Structure-aware Trunk-specific NxDS0 with CAS (CESoPSN, TDMoIP)

Please note that this list corresponds to the list of services in the
TDM Requirements draft. Different MF formats for NxDS0 with CAS
will be accommodated in the next version of the TDM Control Protocol
Extensions
draft.

2. In Section 3 (Interface Parameters field), please continue the list of
Interface Parameters like following:
...
       0x09         2       Fragmentation indicator -- this is the last
entry so far
       0x10    4, 8 or 12   TDM Options [ref]

In addition, please change the name of the existing interface parameter
from CEP Payload Bytes to CEP/TDM Payload Bytes in the corresponding entry.
It would be really nice if you could accommodate this change also in the 
PWE3 Control Protocol draft.

Note: I seem to remember that somebody has asked for a new Interface
Parameter ID
already, so value 0x10 can be already allocated. If this is so, there would
be
no problem with using the next free value.

3. In Section 4 (LDP Status codes), please continuke the list of LDP Status
codes
as following:
...
           0x00000027 "CEP mis-configuration" -- this is the last entry so
far
           0x00000028 "TDM mis-configuration".


4. Add references to the SAToP, CESoPSN, TDMoIP and TDM Control Protocol
Extensions draft to the Section 8 (References).

I would like to update the TDM Control Protocol Extensions draft and re-post
it
ASAP, so I would highly appreciate your timely feedback.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Setup of TDM PWs: Follow-up for the Seoul meeting
Date: Wed, 10 Mar 2004 12:12:33 +0200
Lines: 45
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "Stewart Bryant \(E-mail\)" <stbryant@cisco.com>,
        "Danny McPherson \(E-mail\)" <danny@tcb.net>,
        "Alik Shimelmits" <alik@axerra.com>,
        "Sharon Galtzur" <sharon@axerra.com>,
        "'Riegel Maximilian' \(E-mail\)" <Maximilian.Riegel@icn.siemens.de>,
        "PWE3 WG \(E-mail\)" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Wed Mar 10 11:15:15 2004
Return-path: <pwe3-admin@ietf.org>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: [PWE3] Setup of TDM PWs: Follow-up for the Seoul meeting
Thread-Index: AcQGgUBerYhqwAC5QvKruM+OQ41q7QAAYNKA
To: "Alexander Vainshtein" <sasha@axerra.com>,
        "Luca Martini \(E-mail\)" <lmartini@cisco.com>,
        "Mark Townsley \(E-mail\)" <townsley@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> Luca, Mark and all,
> Following my presentation at the Seoul WG session and our=20
> discussions there, I'd like to ask you to update the PWE3=20
> IANA Allocation draft (it expires in April anyway:-) like following:
>=20
> 1. In Section 2 (PW Type), continume the list of PW Types=20
> like following:
> ...
> 0x0010   SONET/SDH Circuit Emulation over Packet (CEP) --=20
> this is the last
> entry so far
> 0x0011   Structure-agnostic E1 over Packet (SAToP)
> 0x0012   Structure-agnostic T1 (DS1) over Packet (SAToP)=20
> 0x0013   Structure-agnostic E3 over Packet (SAToP)=20
> 0x0014   Structure-agnostic T3 (DS3) over Packet (SAToP)=20
> 0x0015   Structure-aware Basic NxDS0 (CESoPSN, TDMoIP)
> 0x0016   Structure-aware Trunk-specific NxDS0 with CAS (CESoPSN,
TDMoIP)

I agree in principle, but we should separate the CESoPSN and TDMoIP
cases.

> Please note that this list corresponds to the list of=20
> services in the TDM Requirements draft. Different MF formats=20
> for NxDS0 with CAS will be accommodated in the next version=20
> of the TDM Control Protocol Extensions draft.
>=20
> 2. In Section 3 (Interface Parameters field), please continue=20
> the list of Interface Parameters like following:
> ...
>        0x09         2       Fragmentation indicator -- this=20
> is the last entry so far
>        0x10    4, 8 or 12   TDM Options [ref]
>=20
> In addition, please change the name of the existing interface=20
> parameter from CEP Payload Bytes to CEP/TDM Payload Bytes in=20
> the corresponding entry.
> It would be really nice if you could accommodate this change=20
> also in the PWE3 Control Protocol draft.

I think calling it TDM is enough
(the TDM requirements draft defines TDM as including SONET/SDH!)

 Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Tim.Frost@Zarlink.Com
Subject: Re: draft-ietf-pwe3-tdm-requirements-04.txt last call
Date: Mon, 15 Mar 2004 17:25:42 +0000
Lines: 139
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 005FBAC880256E58_="
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, pwe3-admin@ietf.org
X-From: pwe3-admin@ietf.org Mon Mar 15 18:29:50 2004
Return-path: <pwe3-admin@ietf.org>
To: stbryant@cisco.com, maximilian.riegel@siemens.com
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
X-MIMETrack: Serialize by Router on ottmta01/Zarlink(Release 6.5.1|January 21, 2004) at
 03/15/2004 12:25:46 PM,
	Serialize complete at 03/15/2004 12:25:46 PM
X-Spam-Score: 1.19 (*) HTML_20_30,HTML_MESSAGE,NO_REAL_NAME
X-Scanned-By: MIMEDefang 2.38
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multipart message in MIME format.
--=_alternative 005FBAC880256E58_=
Content-Type: text/plain; charset="us-ascii"

Stewart, Max,

I've re-read the document, and I support its progression towards RFC.

During my reading, I noticed the following minor editorial points that 
could be improved, but these shouldn't impede the further progression of 
the document.

1. Introduction: "This document specified the specific requirements..."
   - might read better if it said "This document defines the specific requirements..."

2. Section 1.1. para 3, change "...there are always 8000 such frames per second..." to "...there are normally 8000 such frames per second...". 
   - the frame rate of a T3 stream is not 8000 (see G.704)

4. Section 1.1, para 4, "period" should be "periodic"

5. Section 2, bullet 1 sub-bullet 2, "...in spite of..." would read better 
as "...in the presence of..." 
   - "spite" seems a strange word to find in standards documents

6. Section 4.3, Figure 1 - I think there is an extraneous, U-shaped arrow 
in the bottom right corner of PE1 (linking the Enc and Phy sections, next 
to the arrow for clock B).  In earlier versions of this document, this 
arrow was referenced, but the reference has now been removed and the arrow 
should be removed too.

7. Section 4.3, top of page 11 states clocks B and E must be the same 
frequency. This should also apply to clocks H and J.

8. Section 4.3.2, page 13, under Figure 4, "...and the incoming like clock "A")..." 
   - the word "like" is superfluous.

Regards,
Tim






Stewart Bryant <stbryant@cisco.com>
Sent by: pwe3-admin@ietf.org
08-Mar-2004 07:21 PM
Please respond to stbryant

 
        To:     "pwe3@ietf.org" <pwe3@ietf.org>
        cc: 
        Subject:        [PWE3] draft-ietf-pwe3-tdm-requirements-04.txt last call


This is the start of the two week last call for:

Requirements for Edge-to-Edge Emulation of TDM Circuits
over Packet Switching Networks (PSN)

- Stewart

http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-requirements-04.txt


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



--=_alternative 005FBAC880256E58_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Stewart, Max,</font>
<br>
<br><font size=2 face="sans-serif">I've re-read the document, and I support its progression towards RFC.</font>
<br>
<br><font size=2 face="sans-serif">During my reading, I noticed the following minor editorial points that could be improved, but these shouldn't impede the further progression of the document.</font>
<br>
<br><font size=2 face="sans-serif">1. Introduction: &quot;This document specified the specific requirements...&quot;</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;- might read better if it said &quot;This document <i>defines </i>the specific requirements...&quot;</font>
<br>
<br><font size=2 face="sans-serif">2. Section 1.1. para 3, change &quot;...there are <i>always </i>8000 such frames per second...&quot; to &quot;...there are <i>normally </i>8000 such frames per second...&quot;. </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;- the frame rate of a T3 stream is not 8000 (see G.704)</font>
<br>
<br><font size=2 face="sans-serif">4. Section 1.1, para 4, &quot;period&quot; should be &quot;periodic&quot;</font>
<br>
<br><font size=2 face="sans-serif">5. Section 2, bullet 1 sub-bullet 2, &quot;...in spite of...&quot; would read better as &quot;...in the presence of...&quot; </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;- &quot;spite&quot; seems a strange word to find in standards documents</font>
<br>
<br><font size=2 face="sans-serif">6. Section 4.3, Figure 1 - I think there is an extraneous, U-shaped arrow in the bottom right corner of PE1 (linking the Enc and Phy sections, next to the arrow for clock B). &nbsp;In earlier versions of this document, this arrow was referenced, but the reference has now been removed and the arrow should be removed too.</font>
<br>
<br><font size=2 face="sans-serif">7. Section 4.3, top of page 11 states clocks B and E must be the same frequency. This should also apply to clocks H and J.</font>
<br>
<br><font size=2 face="sans-serif">8. Section 4.3.2, page 13, under Figure 4, &quot;...and the incoming <i>like </i>clock &quot;A&quot;)...&quot; </font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;- the word &quot;like&quot; is superfluous.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Tim</font>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Stewart Bryant &lt;stbryant@cisco.com&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: pwe3-admin@ietf.org</font>
<p><font size=1 face="sans-serif">08-Mar-2004 07:21 PM</font>
<br><font size=1 face="sans-serif">Please respond to stbryant</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&quot;pwe3@ietf.org&quot; &lt;pwe3@ietf.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[PWE3] draft-ietf-pwe3-tdm-requirements-04.txt last call</font></table>
<br>
<br>
<br><font size=2 face="Courier New">This is the start of the two week last call for:<br>
<br>
Requirements for Edge-to-Edge Emulation of TDM Circuits<br>
over Packet Switching Networks (PSN)<br>
<br>
- Stewart<br>
<br>
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-tdm-requirements-04.txt<br>
<br>
<br>
_______________________________________________<br>
pwe3 mailing list<br>
pwe3@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/pwe3<br>
</font>
<br>
<br>
--=_alternative 005FBAC880256E58_=--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: draft-ietf-pwe3-tdm-requirements-04.txt last call
Date: Mon, 15 Mar 2004 20:27:18 +0200
Lines: 64
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40ABB.2610626F"
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 15 19:30:55 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] draft-ietf-pwe3-tdm-requirements-04.txt last call
Thread-Index: AcQKsx9bjdZVNWERTPWf+Ra5nUJiIwAB51gg
To: <Tim.Frost@Zarlink.Com>, <stbryant@cisco.com>,
        <maximilian.riegel@siemens.com>
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C40ABB.2610626F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

2. Section 1.1. para 3, change "...there are always 8000 such frames per
second..." to "...there are normally 8000 such frames per second...".=20
   - the frame rate of a T3 stream is not 8000 (see G.704)=20

Although you are quite correct that this is misworded,
the word "normally" is abnormal here.
=20
The sentence should say "the bitrate is always a multiple of 8000."
=20
Y(J)S
=20

------_=_NextPart_001_01C40ABB.2610626F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3Dsans-serif size=3D2>2. Section 1.1. para 3, change =
"...there are=20
<I>always </I>8000 such frames per second..." to "...there are =
<I>normally=20
</I>8000 such frames per second...". </FONT><BR><FONT face=3Dsans-serif=20
size=3D2>&nbsp; &nbsp;- the frame rate of a T3 stream is not 8000 (see=20
G.704)</FONT>&nbsp;<BR><BR><SPAN class=3D981212418-15032004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Although you are quite correct that this is=20
misworded,</FONT></SPAN></DIV>
<DIV><SPAN class=3D981212418-15032004><FONT face=3DArial color=3D#0000ff =
size=3D2>the=20
word "normally" is abnormal here.</FONT></SPAN></DIV>
<DIV><SPAN class=3D981212418-15032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D981212418-15032004><SPAN =
class=3D981212418-15032004><FONT=20
face=3DArial color=3D#0000ff size=3D2>The sentence should say =
"</FONT></SPAN><SPAN=20
class=3D981212418-15032004><FONT face=3DArial color=3D#0000ff =
size=3D2>the bitrate is=20
always a multiple of 8000."</FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=3D981212418-15032004><SPAN =
class=3D981212418-15032004><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D981212418-15032004><SPAN =
class=3D981212418-15032004><FONT=20
face=3DArial color=3D#0000ff size=3D2>Y(J)S</FONT></SPAN></DIV>
<DIV><SPAN class=3D981212418-15032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV></SPAN></BODY></HTML>

------_=_NextPart_001_01C40ABB.2610626F--


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Amy Katherine" <amyk@foretec.com>
Subject: Re: [iesg-secretary #20172] Liaison statement from ITU-T SG 13 to IETF PWE3 on TDM-MPLS netwo
Date: Mon, 15 Mar 2004 13:23:29 -0500
Lines: 11
Sender: pwe3-admin@ietf.org
Reply-To: iesg-secretary@ietf.org
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Tue Mar 16 20:43:07 2004
Return-path: <pwe3-admin@ietf.org>
X-Authentication-Warning: www1.ietf.org: nobody set sender to iesg-secretary@ietf.org using -f
To: nadine.joubert@itu.int
X-Loop: WREQ 2
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Your request #20172 was updated by amyk:

Dear Georges,

Your Liaison Statement entitled "TDM - MPLS network interworking"
has been posted on the "Liaison Statements" Web page
(http://www.ietf.org/IESG/liaison.html).

Thank you,

The IETF Secretariat


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Proposed change to 5..4.1 of PWE3 architecture
Date: Fri, 19 Mar 2004 16:36:33 +0000
Organization: Cisco Systems, Inc.
Lines: 123
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Fri Mar 19 17:40:05 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

After discussions with Yaakov Stein regarding the use of UDP/IP
as a PW mechanism (used by both TDM approaches), it is proposed
that 5.4.1 be amended as shown below.

Is this acceptable to the WG?

- Stewart

New text:

5.4.1. PWE3 over an IP PSN

    The protocol definition of PWE3 over an IP PSN should employ existing
    IETF protocols where possible.

        +---------------------+              +-------------------------+
        |      Payload        |------------->| Raw payload if possible |
        /=====================\              +-------------------------+
        H Payload Convergence H-----------+->|     Flags, seq # etc    |
        H---------------------H          /   +-------------------------+
        H       Timing        H---------/--->|            RTP          |
        H---------------------H        /     +-------------+           |
        H     Sequencing      H----one of    |             |
        \=====================/        \     |             +-----------+
        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS etc.     |
        +---------------------+              +-------------------------+
        |  PSN Convergence    |------------->|       Not needed        |
        +---------------------+              +-------------------------+
        |        PSN          |------------->|            IP           |
        +---------------------+              +-------------------------+
        |      Data-link      |------------->|         Data-link       |
        +---------------------+              +-------------------------+
        |       Physical      |------------->|          Physical       |
        +---------------------+              +-------------------------+

      Figure 10: PWE3 over an IP PSN

    Figure 10 shows the protocol layering for PWE3 over an IP PSN. As a
    rule, the payload should be carried as received from the NSP, with
    the Payload Convergence Layer provided when needed.  However in
    certain circumstances it may be justifiable to transmit the payload
    in some processed form. The reasons for this must be documented in
    the Encapsulation Layer definition for that payload type.

    Where appropriate, explicit timing is provided by RTP [RFC3550],
    which when used also provides a sequencing service.  When the PSN is
    UDP/IP, the RTP header follows the UDP header and precedes the PW
    control field, while for all other cases the RTP header follows the
    PW control header.

    The encapsulation layer may additionally carry a sequence number;
    sequencing is to be provided either by RTP, or by the PW
    encapsulation layer but not both.

    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols,  e.g. an MPLS label, an
    L2TP session ID, or a UDP port number.

    When PWs are carried over IP the PSN Convergence Layer will not be
    needed.

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 can be used instead of the
    protocol architecture of this section.
=======================================================================

For reference the following is the text that appears in the -06 draft.

5.4.1. PWE3 over an IP PSN

    The protocol definition of PWE3 over an IP PSN SHOULD employ existing
    IETF protocols where possible.

        +---------------------+              +-------------------------+
        |      Payload        |------------->| Raw payload if possible |
        /=====================\              +-------------------------+
        H Payload Convergence H-----------+->|        As Needed        |
        H---------------------H          /   +-------------------------+
        H       Timing        H---------/--->|            RTP          |
        H---------------------H        /     +-------------+           |
        H     Sequencing      H----one of    |             |
        \=====================/        \     |             +-----------+
        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS etc.     |
        +---------------------+              +-------------------------+
        |  PSN Convergence    |------------->|       Not needed        |
        +---------------------+              +-------------------------+
        |        PSN          |------------->|            IP           |
        +---------------------+              +-------------------------+
        |      Data-link      |------------->|         Data-link       |
        +---------------------+              +-------------------------+
        |       Physical      |------------->|          Physical       |
        +---------------------+              +-------------------------+

      Figure 10: PWE3 over an IP PSN

    Figure 10 shows the protocol layering for PWE3 over an IP PSN. As a
    rule, the payload SHOULD be carried as received from the NSP, with
    the Payload Convergence Layer provided when needed.  (It is accepted
    that there MAY sometimes be good reason not to follow this rule, but
    the exceptional circumstances need to be documented in the
    Encapsulation Layer definition for that payload type).

    Where appropriate, timing is provided by RTP [RFC3550], which when
    used also provides a sequencing service.  PW Demultiplexing may be
    provided by a number of existing IETF tunnel protocols.  Some of
    these tunnel protocols provide an optional sequencing service.
    (Sequencing is provided either by RTP, or by the PW Demultiplexer
    Layer, but not both).

    RTP is normally carried over UDP, however the tunnel protocols that
    are capable of carrying a PW, provide sufficient functionality to
    carry RTP without an intervening transport layer.  UDP MAY therefore
    be omitted from the protocol stack.

    A PSN Convergence Layer is not needed, because all the tunnel
    protocols shown above are designed to operate directly over an IP
    PSN.

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 can be used instead of the
    protocol architecture of this section.

=========================================================================


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Fri, 19 Mar 2004 09:29:55 -0800
Lines: 222
Sender: pwe3-admin@ietf.org
References: <405B2191.3050104@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Fri Mar 19 18:32:08 2004
Return-path: <pwe3-admin@ietf.org>
To: <stbryant@cisco.com>, <pwe3@ietf.org>
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.2800.1165
In-Reply-To: <405B2191.3050104@cisco.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart,

Since we no longer have a PSN convergence layer either in IP or in MPLS,
I suggest we remove it altogether.

In reference to:

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 can be used instead of the
    protocol architecture of this section.

I find this disturbing. Either people have the ECMP or ECMP-like problem
here as well or they don't. If they do we should better know this in
advance on not find out after another year has passed. 

Following that, I suggest that we change the layering diagram such that
the layers include only: Physical, Data-link, PSN, PW-Multiplexing,
Payload Convergence, Payload (where payload convergence include timing,
sequencing, etc but the decomposition is not explicitly shown on the
figure). The payload convergence includes RTP and the control word. 

We write a single architecture layer section which is good for both IP
and MPLS, since we don't specify the internal order of RTP and Control
word within the convergence layer in this section.

We write another section that describes the Convergence layer
decomposition and specify (unfortunately) that the RTP and control word
order changes depending on the demulplexing layer. If MPLS is used as
demultiplexing layer RTP is after control word, else RTP before control
word, or whatever)

Regards
Ron

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
> Behalf Of Stewart Bryant
> Sent: Friday, March 19, 2004 8:37 AM
> To: pwe3@ietf.org
> Subject: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> After discussions with Yaakov Stein regarding the use of UDP/IP
> as a PW mechanism (used by both TDM approaches), it is proposed
> that 5.4.1 be amended as shown below.
> 
> Is this acceptable to the WG?
> 
> - Stewart
> 
> New text:
> 
> 5.4.1. PWE3 over an IP PSN
> 
>     The protocol definition of PWE3 over an IP PSN should 
> employ existing
>     IETF protocols where possible.
> 
>         +---------------------+              
> +-------------------------+
>         |      Payload        |------------->| Raw payload if 
> possible |
>         /=====================\              
> +-------------------------+
>         H Payload Convergence H-----------+->|     Flags, seq 
> # etc    |
>         H---------------------H          /   
> +-------------------------+
>         H       Timing        H---------/--->|            RTP 
>          |
>         H---------------------H        /     +-------------+  
>          |
>         H     Sequencing      H----one of    |             |
>         \=====================/        \     |             
> +-----------+
>         |  PW Demultiplexer   |---------+--->|     L2TP, MPLS 
> etc.     |
>         +---------------------+              
> +-------------------------+
>         |  PSN Convergence    |------------->|       Not 
> needed        |
>         +---------------------+              
> +-------------------------+
>         |        PSN          |------------->|            IP  
>          |
>         +---------------------+              
> +-------------------------+
>         |      Data-link      |------------->|         
> Data-link       |
>         +---------------------+              
> +-------------------------+
>         |       Physical      |------------->|          
> Physical       |
>         +---------------------+              
> +-------------------------+
> 
>       Figure 10: PWE3 over an IP PSN
> 
>     Figure 10 shows the protocol layering for PWE3 over an IP 
> PSN. As a
>     rule, the payload should be carried as received from the NSP, with
>     the Payload Convergence Layer provided when needed.  However in
>     certain circumstances it may be justifiable to transmit 
> the payload
>     in some processed form. The reasons for this must be documented in
>     the Encapsulation Layer definition for that payload type.
> 
>     Where appropriate, explicit timing is provided by RTP [RFC3550],
>     which when used also provides a sequencing service.  When 
> the PSN is
>     UDP/IP, the RTP header follows the UDP header and precedes the PW
>     control field, while for all other cases the RTP header 
> follows the
>     PW control header.
> 
>     The encapsulation layer may additionally carry a sequence number;
>     sequencing is to be provided either by RTP, or by the PW
>     encapsulation layer but not both.
> 
>     PW Demultiplexing is provided by the PW label, which may take the
>     form specified in a number of IETF protocols,  e.g. an 
> MPLS label, an
>     L2TP session ID, or a UDP port number.
> 
>     When PWs are carried over IP the PSN Convergence Layer will not be
>     needed.
> 
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 can be used instead of the
>     protocol architecture of this section.
> ==============================================================
> =========
> 
> For reference the following is the text that appears in the -06 draft.
> 
> 5.4.1. PWE3 over an IP PSN
> 
>     The protocol definition of PWE3 over an IP PSN SHOULD 
> employ existing
>     IETF protocols where possible.
> 
>         +---------------------+              
> +-------------------------+
>         |      Payload        |------------->| Raw payload if 
> possible |
>         /=====================\              
> +-------------------------+
>         H Payload Convergence H-----------+->|        As 
> Needed        |
>         H---------------------H          /   
> +-------------------------+
>         H       Timing        H---------/--->|            RTP 
>          |
>         H---------------------H        /     +-------------+  
>          |
>         H     Sequencing      H----one of    |             |
>         \=====================/        \     |             
> +-----------+
>         |  PW Demultiplexer   |---------+--->|     L2TP, MPLS 
> etc.     |
>         +---------------------+              
> +-------------------------+
>         |  PSN Convergence    |------------->|       Not 
> needed        |
>         +---------------------+              
> +-------------------------+
>         |        PSN          |------------->|            IP  
>          |
>         +---------------------+              
> +-------------------------+
>         |      Data-link      |------------->|         
> Data-link       |
>         +---------------------+              
> +-------------------------+
>         |       Physical      |------------->|          
> Physical       |
>         +---------------------+              
> +-------------------------+
> 
>       Figure 10: PWE3 over an IP PSN
> 
>     Figure 10 shows the protocol layering for PWE3 over an IP 
> PSN. As a
>     rule, the payload SHOULD be carried as received from the NSP, with
>     the Payload Convergence Layer provided when needed.  (It 
> is accepted
>     that there MAY sometimes be good reason not to follow 
> this rule, but
>     the exceptional circumstances need to be documented in the
>     Encapsulation Layer definition for that payload type).
> 
>     Where appropriate, timing is provided by RTP [RFC3550], which when
>     used also provides a sequencing service.  PW Demultiplexing may be
>     provided by a number of existing IETF tunnel protocols.  Some of
>     these tunnel protocols provide an optional sequencing service.
>     (Sequencing is provided either by RTP, or by the PW Demultiplexer
>     Layer, but not both).
> 
>     RTP is normally carried over UDP, however the tunnel 
> protocols that
>     are capable of carrying a PW, provide sufficient functionality to
>     carry RTP without an intervening transport layer.  UDP 
> MAY therefore
>     be omitted from the protocol stack.
> 
>     A PSN Convergence Layer is not needed, because all the tunnel
>     protocols shown above are designed to operate directly over an IP
>     PSN.
> 
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 can be used instead of the
>     protocol architecture of this section.
> 
> ==============================================================
> ===========
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: Re: Proposed change to 5..4.1 of PWE3 architecture
Date: Fri, 19 Mar 2004 19:17:05 +0000
Organization: Cisco Systems, Inc.
Lines: 255
Sender: pwe3-admin@ietf.org
References: <002501c40dd7$cc594a30$230110ac@lycium.net>
Reply-To: stbryant@cisco.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-admin@ietf.org Fri Mar 19 20:20:19 2004
Return-path: <pwe3-admin@ietf.org>
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: <002501c40dd7$cc594a30$230110ac@lycium.net>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Ron

Please see inline:

Ron Cohen wrote:

> Stewart,
> 
> Since we no longer have a PSN convergence layer either in IP or in MPLS,
> I suggest we remove it altogether.

The reserved nibble and the length are both PSN convergence elements
of the CW, and so there is still a need for MPLS PSN convergence.

> 
> In reference to:
> 
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 can be used instead of the
>     protocol architecture of this section.
> 
> I find this disturbing. Either people have the ECMP or ECMP-like problem
> here as well or they don't. If they do we should better know this in
> advance on not find out after another year has passed. 

I am not quite sure I follow your argument. The proposed change is
in the IP section, and there is no ECMP issue in IP unless you
run per packet ECMP, but that breaks so many other things that in
practise no one runs it.

> 
> Following that, I suggest that we change the layering diagram such that
> the layers include only: Physical, Data-link, PSN, PW-Multiplexing,
> Payload Convergence, Payload (where payload convergence include timing,
> sequencing, etc but the decomposition is not explicitly shown on the
> figure). The payload convergence includes RTP and the control word. 
> 
> We write a single architecture layer section which is good for both IP
> and MPLS, since we don't specify the internal order of RTP and Control
> word within the convergence layer in this section.
> 
> We write another section that describes the Convergence layer
> decomposition and specify (unfortunately) that the RTP and control word
> order changes depending on the demulplexing layer. If MPLS is used as
> demultiplexing layer RTP is after control word, else RTP before control
> word, or whatever)

How important are these changes?

If we make this level of change we really risk a significant delay in
getting the document back to the IESG, and since this document gates all
the encapsulation and control drafts we delay them also.

Perhaps it would be better to rule Yaakov's proposal out of scope
for a draft that has already passed last call on this text?

- Stewart

> 
> Regards
> Ron
> 
> 
>>-----Original Message-----
>>From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
>>Behalf Of Stewart Bryant
>>Sent: Friday, March 19, 2004 8:37 AM
>>To: pwe3@ietf.org
>>Subject: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
>>
>>
>>After discussions with Yaakov Stein regarding the use of UDP/IP
>>as a PW mechanism (used by both TDM approaches), it is proposed
>>that 5.4.1 be amended as shown below.
>>
>>Is this acceptable to the WG?
>>
>>- Stewart
>>
>>New text:
>>
>>5.4.1. PWE3 over an IP PSN
>>
>>    The protocol definition of PWE3 over an IP PSN should 
>>employ existing
>>    IETF protocols where possible.
>>
>>        +---------------------+              
>>+-------------------------+
>>        |      Payload        |------------->| Raw payload if 
>>possible |
>>        /=====================\              
>>+-------------------------+
>>        H Payload Convergence H-----------+->|     Flags, seq 
>># etc    |
>>        H---------------------H          /   
>>+-------------------------+
>>        H       Timing        H---------/--->|            RTP 
>>         |
>>        H---------------------H        /     +-------------+  
>>         |
>>        H     Sequencing      H----one of    |             |
>>        \=====================/        \     |             
>>+-----------+
>>        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS 
>>etc.     |
>>        +---------------------+              
>>+-------------------------+
>>        |  PSN Convergence    |------------->|       Not 
>>needed        |
>>        +---------------------+              
>>+-------------------------+
>>        |        PSN          |------------->|            IP  
>>         |
>>        +---------------------+              
>>+-------------------------+
>>        |      Data-link      |------------->|         
>>Data-link       |
>>        +---------------------+              
>>+-------------------------+
>>        |       Physical      |------------->|          
>>Physical       |
>>        +---------------------+              
>>+-------------------------+
>>
>>      Figure 10: PWE3 over an IP PSN
>>
>>    Figure 10 shows the protocol layering for PWE3 over an IP 
>>PSN. As a
>>    rule, the payload should be carried as received from the NSP, with
>>    the Payload Convergence Layer provided when needed.  However in
>>    certain circumstances it may be justifiable to transmit 
>>the payload
>>    in some processed form. The reasons for this must be documented in
>>    the Encapsulation Layer definition for that payload type.
>>
>>    Where appropriate, explicit timing is provided by RTP [RFC3550],
>>    which when used also provides a sequencing service.  When 
>>the PSN is
>>    UDP/IP, the RTP header follows the UDP header and precedes the PW
>>    control field, while for all other cases the RTP header 
>>follows the
>>    PW control header.
>>
>>    The encapsulation layer may additionally carry a sequence number;
>>    sequencing is to be provided either by RTP, or by the PW
>>    encapsulation layer but not both.
>>
>>    PW Demultiplexing is provided by the PW label, which may take the
>>    form specified in a number of IETF protocols,  e.g. an 
>>MPLS label, an
>>    L2TP session ID, or a UDP port number.
>>
>>    When PWs are carried over IP the PSN Convergence Layer will not be
>>    needed.
>>
>>    As a special case, if the PW Demultiplexer is an MPLS label, the
>>    protocol architecture of section 5.4.2 can be used instead of the
>>    protocol architecture of this section.
>>==============================================================
>>=========
>>
>>For reference the following is the text that appears in the -06 draft.
>>
>>5.4.1. PWE3 over an IP PSN
>>
>>    The protocol definition of PWE3 over an IP PSN SHOULD 
>>employ existing
>>    IETF protocols where possible.
>>
>>        +---------------------+              
>>+-------------------------+
>>        |      Payload        |------------->| Raw payload if 
>>possible |
>>        /=====================\              
>>+-------------------------+
>>        H Payload Convergence H-----------+->|        As 
>>Needed        |
>>        H---------------------H          /   
>>+-------------------------+
>>        H       Timing        H---------/--->|            RTP 
>>         |
>>        H---------------------H        /     +-------------+  
>>         |
>>        H     Sequencing      H----one of    |             |
>>        \=====================/        \     |             
>>+-----------+
>>        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS 
>>etc.     |
>>        +---------------------+              
>>+-------------------------+
>>        |  PSN Convergence    |------------->|       Not 
>>needed        |
>>        +---------------------+              
>>+-------------------------+
>>        |        PSN          |------------->|            IP  
>>         |
>>        +---------------------+              
>>+-------------------------+
>>        |      Data-link      |------------->|         
>>Data-link       |
>>        +---------------------+              
>>+-------------------------+
>>        |       Physical      |------------->|          
>>Physical       |
>>        +---------------------+              
>>+-------------------------+
>>
>>      Figure 10: PWE3 over an IP PSN
>>
>>    Figure 10 shows the protocol layering for PWE3 over an IP 
>>PSN. As a
>>    rule, the payload SHOULD be carried as received from the NSP, with
>>    the Payload Convergence Layer provided when needed.  (It 
>>is accepted
>>    that there MAY sometimes be good reason not to follow 
>>this rule, but
>>    the exceptional circumstances need to be documented in the
>>    Encapsulation Layer definition for that payload type).
>>
>>    Where appropriate, timing is provided by RTP [RFC3550], which when
>>    used also provides a sequencing service.  PW Demultiplexing may be
>>    provided by a number of existing IETF tunnel protocols.  Some of
>>    these tunnel protocols provide an optional sequencing service.
>>    (Sequencing is provided either by RTP, or by the PW Demultiplexer
>>    Layer, but not both).
>>
>>    RTP is normally carried over UDP, however the tunnel 
>>protocols that
>>    are capable of carrying a PW, provide sufficient functionality to
>>    carry RTP without an intervening transport layer.  UDP 
>>MAY therefore
>>    be omitted from the protocol stack.
>>
>>    A PSN Convergence Layer is not needed, because all the tunnel
>>    protocols shown above are designed to operate directly over an IP
>>    PSN.
>>
>>    As a special case, if the PW Demultiplexer is an MPLS label, the
>>    protocol architecture of section 5.4.2 can be used instead of the
>>    protocol architecture of this section.
>>
>>==============================================================
>>===========
>>
>>
>>_______________________________________________
>>pwe3 mailing list
>>pwe3@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pwe3
>>
> 
> 
> 
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Sun, 21 Mar 2004 16:47:04 +0200
Lines: 47
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Sun Mar 21 15:50:09 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQN502rybYcPWbbSvm9JSeHSl27vQBa3UhQ
To: <stbryant@cisco.com>, "Ron Cohen" <ronc@lyciumnetworks.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> > Following that, I suggest that we change the layering diagram such=20
> > that the layers include only: Physical, Data-link, PSN,=20
> > PW-Multiplexing, Payload Convergence, Payload (where payload=20
> > convergence include timing, sequencing, etc but the decomposition is

> > not explicitly shown on the figure). The payload convergence
includes RTP and the control word.
> >=20
> > We write a single architecture layer section which is good for both
IP=20
> > and MPLS, since we don't specify the internal order of RTP and
Control=20
> > word within the convergence layer in this section.
> >=20
> > We write another section that describes the Convergence layer=20
> > decomposition and specify (unfortunately) that the RTP and control=20
> > word order changes depending on the demulplexing layer. If MPLS is=20
> > used as demultiplexing layer RTP is after control word, else RTP=20
> > before control word, or whatever)
>=20
> How important are these changes?
>=20
> If we make this level of change we really risk a significant=20
> delay in getting the document back to the IESG, and since=20
> this document gates all the encapsulation and control drafts=20
> we delay them also.
>=20
> Perhaps it would be better to rule Yaakov's proposal out of=20
> scope for a draft that has already passed last call on this text?

While I think that Ron's suggestions=20
(having first a common section, and thereafter separate IP and MPLS
ones)
are sensible, they seem to be basically editorial in nature.

At this late date I wouldn't want to hold everything up for
such editorial changes.

On the other hand, the use of UDP/IP has been in our
charter from the very beginning, even if most of the work
has been MPLS-oriented.=20

I would therefore object to removing the use of pure UDP/IP
from the architecture document.

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: neil.2.harrison@bt.com
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 12:54:42 -0000
Lines: 192
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 13:57:09 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3LvgAKDCgg
To: <mmorrow@cisco.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 12:54:44.0140 (UTC) FILETIME=[5E6FDEC0:01C3FF8C]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

<converted to plain text from original HTML format>

Monique Morrow wrote 01 March 2004 04:00
I presented OAM Msg Mapping status today in Seoul, =
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt =
with a proposal to progress the draft as a Working Group item =20
=20
Whilst we had no opposition the room, I would like to ensure that there =
is consensus on the list to progress the draft as a WG item.
=20
Essentially, the draft has been revised to reflect like-to-like =
constructs as per the scope of PWE3 and, covers fault detection and =
alarm message mapping as two separate elements.
=3D=3D=3D=3D

We (ie BT) cannot support this document as it stands for several =
reasons....for example:

1	No defects are defined anywhere (not just in here but in any other =
IETF draft/rfc) in terms of clear entry/exit criteria and consequent =
actions.  Note that the defects in MPLS are different to the defects in =
IP.....which should not be surprising as their modes are different, and =
even this draft recognises that fact (also see 4).  CF Y.1711 where =
these are specified.


2	There is no demarcation between the available state and unavailable =
state for network trail entities.  This means there is no temporal basis =
for the specification of an availability SLA or a network performance =
SLA, noting that the latter is only relevant to the available state.  =
These impact network element specifications and thus have consequential =
impact on NMS/OSS.  NE and NMS/OSS considerations are important for an =
operator to see correctly executed.  CF Y.1711 where the unavailable =
state is specified (as a consequential persistence of defects).


3	Seq Nos cannot be left 'open-ended' wrt aberration handling.  At some =
degree of persistent corruption a defect state must be declared.  This =
therefore requires entry/exit criteria and consequent actions =
specifying.  We note this is at least recognised as an open issue in =
section 4.1.1.


4	A PW is *not* a networked entity....it is just an adaptation function =
(now whether it is a good adaptation function for the server layer =
considered is a different consideration).  An LSP however is a networked =
path entity in the case of using MPLS (co-ps mode).  Similarly, an IP =
pkt is also a networked entity (in the case of an IP cl-ps mode server =
layer).  XoverMPLS is therefore not the same as XoverIP....I am =
perplexed as to why this fact so hard for some folks to grok/accept.  Is =
it to make the work palatable to IETF folks?  But who is kidding who =
here?  Whilst this stance might be necessary to 'sell' this stuff in =
IETF, speaking as an operator we can't afford to base future network =
investments on such misplaced ideologies....we need this stuff properly =
architecting else it will impact our costs (both capex and opex) and the =
efficacy of the services we can offer. =20

This distinction between MPLS and IP is even recognised in the =
draft.....for example, in section 4.1 it says:

"In case of MPLS there are additional failures (see also [ITU-T=20
   Y.1710]). E.g.=20
   =20
   . PW mislabeling, which could be due to a failure on the ingress PE=20
     or due to an over-writing of the PW label value somewhere along=20
     the way=20
   =20
   . Label swapping or LSP mismerge in the PSN network, which could=20
     result in the termination of a PW at the wrong egress PE.=20

   . Unintended self-replication (e.g. due to loops or denial-of-
     Service attacks) "

This is of course correct. Note that these defects *cannot* occur in a =
cl-ps server layer like IP, which is precisely what the above text =
implies, because a cl-ps server layer must always have a network =
significant DA/SA pair in each packet.  However, when using a co-ps =
forwarding mode like MPLS this is not the case.  Here we have a trail =
entity (ie an LSP) that is constructed between addressable (ie network =
significant) access points by the concatenation of a sequence of single =
link-connection (downstream only) significant identifiers.

So given this is even recognised in the draft now (and as one reads =
through the draft it becomes increasingly clear that the MPLS server =
layer case is being treated quite differently to the IP server layer =
case), then why not go the extra step and come clean by accepting that =
we don't have to force XoverMPLS to be the same as XoverIP?  We could =
have a nice/simple adaptation for carrying clients over arch compliant =
MPLS now and really start to leverage the latent potential of MPLS.

Can someone please explain to us why this can't this be done (and please =
don't use mp2p and PHP as excuses....we know these are broken arch =
flavours of MPLS, we just have to live with these and move on....we =
should not keep making further mistakes on the back of past mistakes)?


5	Can someone please explain to us why Y.1710 (which is largely about =
principles/requirements) is at long last recognised in this draft but =
Y.1711 is not recognised as a valid OAM solution for MPLS?  This is =
especially puzzling for us as Y.1711 is simple and complete (wrt defect =
and availability specifications) and was written by an operator.....so =
one might get the hint here that it was something that we 'required' ;-) =
 It seems quite bizarre that this is not included (even for completeness =
of reference), especially noting this remark at the end of section =
4.2.2:

"Based on these observations, it is clear that a Service Provider has =
the disposal of a variety of tools. There are many factors that =
influence which combination of tools best meets its needs."=20

Is there some specific technical (or other) reason why Y.1711 cannot be =
referenced?


6	In section 4.4 it says:

"Besides reporting PW failures, PW status is used to propagate AC =
failures. When and how to use those messages is dependent on the =
emulated protocol and will be explained in the subsequent paragraphs 5.3 =
and 6.3)."

This is generally incorrect.  If one respects the client/server =
architectural requirements (in particular client and server layer =
independence, and client layer transparency) then a failure of a client =
layer network should have no consequential impact on any server layer.  =
The above statement is violating layer independence and it is therefore =
not a good idea.  It's the same as asking a SDH network to carry an ATM =
client (or any other client) layer's failure indications.

And what happens if the client and server layers are own by different =
operating parties?  This is obviously a wrong behaviour here.

Each layer network must be self-contained and in a client/server =
relationship they must be independent.

=20
7	In section 4.7 it says:

"PWs can fail in a single direction or in both directions. PEs SHOULD =
keep track of the status of each individual direction. In other words, a =
PE SHOULD be able to distinguish between the following states: "PW UP", =
"PW Transmit Direction Down", "PW Receive Direction Down", "PW Receive =
and Transmit Down".=20
  =20
The next two sections discuss under which conditions a PE enters and =
exits these states. To avoid an unnecessarily complicated description, =
only the states "PW UP" and "PW DOWN" are discussed without further =
analysis whether it applies to one or two directions of the PW."

Be careful here.  Performance metrics apply unidirectionally and only to =
the available state.  However, for many applications the failure of one =
direction effectively means *both* directions must be considered as =
failed.  Thus even if only a single direction fails (though to be =
accurate, this actually means if one direction enters the unavailable =
state) then the collection of performance metrics of *both* directions =
should be suspended....at least wrt to their meaning against any =
performance SLAs that are being measured.  Have a read of Y.1711, as =
this explains what is required here.


8	In section 4.7.1 it says:

"Note that if the control session between the PEs fails, the PW is torn =
down and needs to be re-established. As a consequence, control session =
failure leads to disappearance of the PW, not to a PW Down state."=20

This should not be taken as a general requirement.  Failures of =
control-plane components should not necessarily remove data-plane trails =
that have been set-up.  This is particularly true in the case of =
S-PVC-like constructs.


9	Towards the end of section 5.2 FR 'port-mode' is mentioned.  Similarly =
in section 6.2 wrt ATM 'transparent mapping' it says:

"In case of transparent mapping, where the PE does not keep track of the =
status of individual ATM VPCs or VCCs, it is possible that a PE does not =
know which VPCs and/or VCCs are active. In such a case there is a need =
for another fault indication mechanism on the AC. This is beyond the =
scope of this document."

'Port-mode' has no meaning in functional architecture terms.....and for =
a good reason as the extract above demonstrates....and really ought not =
to be used for any client case.


.....so far.....regards, Neil



=20
=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Sun, 21 Mar 2004 17:07:43 +0200
Lines: 88
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Sun Mar 21 16:13:03 2004
Return-path: <pwe3-admin@ietf.org>
To: "'stbryant@cisco.com'" <stbryant@cisco.com>,
        Ron Cohen
	 <ronc@lyciumnetworks.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart, Ron and all,
Please see inline below.

----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com <mailto:sasha@axerra.com> 
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Friday, March 19, 2004 9:17 PM
> To: Ron Cohen
> Cc: pwe3@ietf.org
> Subject: Re: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> Ron
> 
> Please see inline:
> 
> Ron Cohen wrote:
> 
> > Stewart,
> > 
> > Since we no longer have a PSN convergence layer either in 
> IP or in MPLS,
> > I suggest we remove it altogether.
> 
> The reserved nibble and the length are both PSN convergence elements
> of the CW, and so there is still a need for MPLS PSN convergence.
>
Not that this is really important - but I'd say that there is 
need of the PSN convergence layer in case of MPLS because
it there neither protocol nor length in the MPLS iself, and
this layer is represented by the reserved first nibble and LEN field
of the CW.  
>
> > 
> > In reference to:
> > 
> >     As a special case, if the PW Demultiplexer is an MPLS label, the
> >     protocol architecture of section 5.4.2 can be used 
> instead of the
> >     protocol architecture of this section.
> > 
> > I find this disturbing. Either people have the ECMP or 
> ECMP-like problem
> > here as well or they don't. If they do we should better know this in
> > advance on not find out after another year has passed. 
>
I assume that the intention here was to treat MPLS in IP or GRE as
an a special case of PW over IP. If this is correct, I find the 
situation where the demultiplexing "tail" wags the tunneling "dog"
somewhat worrying: e.g., if you suddenly need the PSN convergence
layer (i.e., the reserved nibble and the LEN field) with an IP PSN! 
>
> I am not quite sure I follow your argument. The proposed change is
> in the IP section, and there is no ECMP issue in IP unless you
> run per packet ECMP, but that breaks so many other things that in
> practise no one runs it.
> 
> > 
... snipped ...
> >>    Where appropriate, explicit timing is provided by RTP [RFC3550],
> >>    which when used also provides a sequencing service.  When 
> >>the PSN is
> >>    UDP/IP, the RTP header follows the UDP header and 
> precedes the PW
> >>    control field, while for all other cases the RTP header 
> >>follows the
> >>    PW control header.
>
The original reason for placing RTP after the CW in case of MPLS
was the need to make the encapsulation ECMP-safe (plus the worry
about 0100 in the first nibble being allocated by IANA for some
experiment ages ago without any evidence of existing
deployments anywhere). Since this need does not exist for an 
IP PSN (as explained by Stewart above), I do not see any need 
in one more "branch" ( aspecial rule for UDP demultiplexing vs. 
another rule for, say L2TPv3 demultiplexing).
>
> >>
... snipped to the end ...


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Sun, 21 Mar 2004 17:09:12 +0200
Lines: 34
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Sun Mar 21 16:14:02 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>, stbryant@cisco.com,
        Ron Cohen
	 <ronc@lyciumnetworks.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yaakov, Stewart, Ron and all,
Please see inline below.

----------------------------------------------------------------------------
--------
With best regards,
                          Sasha Vainshtein
email:   sasha@axerra.com <mailto:sasha@axerra.com> 
phone:  +972-3-7659993 (office)
            +972-8-9254948 (home)
            +972-58-674833 (cellular)


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Sunday, March 21, 2004 4:47 PM
> To: stbryant@cisco.com; Ron Cohen
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
...
> 
> I would therefore object to removing the use of pure UDP/IP
> from the architecture document.
> 
[Sasha] I concur.
>
> Y(J)S
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Ron Cohen" <ronc@lyciumnetworks.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Sun, 21 Mar 2004 12:11:46 -0800
Lines: 70
Sender: pwe3-admin@ietf.org
References: <AF5018AC03D1D411ABB70002A5091326015E10B2@TLV1>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Sun Mar 21 21:13:05 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Sasha Vainshtein'" <Sasha@AXERRA.com>,
        "'Yaakov Stein'" <yaakov_s@rad.com>, <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.2800.1165
In-Reply-To: <AF5018AC03D1D411ABB70002A5091326015E10B2@TLV1>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



1. Never suggested to remove support for IP/UDP encapsulation. Where did
this come from?

2. It seems more consistent to have the order of RTP and control word be
dependent on the demultiplexing layer (MPLS vs. L2TP or UDP) and not PSN
layer (IP or MPLS), as potentially the PSN layer tunneling technique may
change along the path without a need to change the upper payload
convergence layer. As a minimal change I therefore suggest to change the
'can' to a 'must' in the following text:

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 can be used instead of the
    protocol architecture of this section.

3. The rest of the changes I suggested are editorial.  

Ron

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org] On 
> Behalf Of Sasha Vainshtein
> Sent: Sunday, March 21, 2004 7:09 AM
> To: 'Yaakov Stein'; stbryant@cisco.com; Ron Cohen
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> Yaakov, Stewart, Ron and all,
> Please see inline below.
> 
> --------------------------------------------------------------
> --------------
> --------
> With best regards,
>                           Sasha Vainshtein
> email:   sasha@axerra.com <mailto:sasha@axerra.com> 
> phone:  +972-3-7659993 (office)
>             +972-8-9254948 (home)
>             +972-58-674833 (cellular)
> 
> 
> > -----Original Message-----
> > From: Yaakov Stein [mailto:yaakov_s@rad.com]
> > Sent: Sunday, March 21, 2004 4:47 PM
> > To: stbryant@cisco.com; Ron Cohen
> > Cc: pwe3@ietf.org
> > Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> > 
> ...
> > 
> > I would therefore object to removing the use of pure UDP/IP
> > from the architecture document.
> > 
> [Sasha] I concur.
> >
> > Y(J)S
> > 
> > _______________________________________________
> > 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-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 09:35:29 +0000
Organization: Cisco Systems, Inc.
Lines: 63
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 22 10:39:09 2004
Return-path: <pwe3-admin@ietf.org>
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@ietf.org" <pwe3@ietf.org>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Following Ron's input, the proposed new text for 5.4.1 is:


5.4.1. PWE3 over an IP PSN

    The protocol definition of PWE3 over an IP PSN should employ existing
    IETF protocols where possible.

        +---------------------+              +-------------------------+
        |      Payload        |------------->| Raw payload if possible |
        /=====================\              +-------------------------+
        H Payload Convergence H-----------+->|     Flags, seq # etc    |
        H---------------------H          /   +-------------------------+
        H       Timing        H---------/--->|            RTP          |
        H---------------------H        /     +-------------+           |
        H     Sequencing      H----one of    |             |
        \=====================/        \     |             +-----------+
        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS etc.     |
        +---------------------+              +-------------------------+
        |  PSN Convergence    |------------->|       Not needed        |
        +---------------------+              +-------------------------+
        |        PSN          |------------->|            IP           |
        +---------------------+              +-------------------------+
        |      Data-link      |------------->|         Data-link       |
        +---------------------+              +-------------------------+
        |       Physical      |------------->|          Physical       |
        +---------------------+              +-------------------------+

      Figure 10: PWE3 over an IP PSN

    Figure 10 shows the protocol layering for PWE3 over an IP PSN. As a
    rule, the payload should be carried as received from the NSP, with
    the Payload Convergence Layer provided when needed.  However in
    certain circumstances it may be justifiable to transmit the payload
    in some processed form. The reasons for this must be documented in
    the Encapsulation Layer definition for that payload type.

    Where appropriate, explicit timing is provided by RTP [RFC3550],
    which when used also provides a sequencing service.  When the PSN is
    UDP/IP, the RTP header follows the UDP header and precedes the PW
    control field, while for all other cases the RTP header follows the
    PW control header.

    The encapsulation layer may additionally carry a sequence number;
    sequencing is to be provided either by RTP, or by the PW
    encapsulation layer but not both.

    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols,  e.g. an MPLS label, an
    L2TP session ID, or a UDP port number.

    When PWs are carried over IP the PSN Convergence Layer will not be
    needed.

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 must be used instead of the
    protocol architecture of this section.

========================

This differs from the previous CHANGED text in the last sentence in that
it used to read "section 5.4.2 can be used" and now reads "section 5.4.2
must be used"


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 12:18:30 +0200
Lines: 90
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Mon Mar 22 11:24:18 2004
Return-path: <pwe3-admin@ietf.org>
To: "'stbryant@cisco.com'" <stbryant@cisco.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Stewart and all,
Please see inline.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Monday, March 22, 2004 11:35 AM
> To: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> Following Ron's input, the proposed new text for 5.4.1 is:
> 
> 
> 5.4.1. PWE3 over an IP PSN
> 
... snipped ...
>
>     Figure 10 shows the protocol layering for PWE3 over an IP 
> PSN. As a
>     rule, the payload should be carried as received from the NSP, with
>     the Payload Convergence Layer provided when needed.  However in
>     certain circumstances it may be justifiable to transmit 
> the payload
>     in some processed form. The reasons for this must be documented in
>     the Encapsulation Layer definition for that payload type.
> 
>     Where appropriate, explicit timing is provided by RTP [RFC3550],
>     which when used also provides a sequencing service.  When 
> the PSN is
>     UDP/IP, the RTP header follows the UDP header and precedes the PW
>     control field, while for all other cases the RTP header 
> follows the
>     PW control header.
>
[Sasha] I do not think that UDP/IP is a special kind of PSN (at least the WG

Charter does not say so). And I do not see any reason for difference in
the relative position of the CW and RTP headers for any kind of
demultiplexing 
over an IP PSN with the possible exception of MPLS-in-IP as noted in the
last
para of this section.
> 
>     The encapsulation layer may additionally carry a sequence number;
>     sequencing is to be provided either by RTP, or by the PW
>     encapsulation layer but not both.
> 
>     PW Demultiplexing is provided by the PW label, which may take the
>     form specified in a number of IETF protocols,  e.g. an 
> MPLS label, an
>     L2TP session ID, or a UDP port number.
>
[Sasha] IMO explicit references to MPLS-in-IP and L2TPv3
specs would be helpful here.
> 
>     When PWs are carried over IP the PSN Convergence Layer will not be
>     needed.
> 
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 must be used instead of the
>     protocol architecture of this section.
> 
[Sasha] The above-mentioned explicit reference to the MPLS-in-IP spec
would make it clear that using an MPLS label as a demultiplexer actually
makes PWs using them MPLS PWs regardless of the actuall tunneling mechanism.
> ========================
> 
> This differs from the previous CHANGED text in the last 
> sentence in that
> it used to read "section 5.4.2 can be used" and now reads 
> "section 5.4.2
> must be used"
> 
> 
> 
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 13:06:49 +0200
Lines: 30
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 22 12:10:06 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQPgLX8V9z4dI5yRbe7NRdoBrOKvQAfGB+w
To: "Ron Cohen" <ronc@lyciumnetworks.com>,
        "Alexander Vainshtein" <sasha@axerra.com>, <stbryant@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> 1. Never suggested to remove support for IP/UDP=20
> encapsulation. Where did this come from?

This is what Stewart suggested if the changes were too radical.

=20
> 2. It seems more consistent to have the order of RTP and=20
> control word be dependent on the demultiplexing layer (MPLS=20
> vs. L2TP or UDP) and not PSN layer (IP or MPLS), as=20
> potentially the PSN layer tunneling technique may change=20
> along the path without a need to change the upper payload=20
> convergence layer. As a minimal change I therefore suggest to=20
> change the 'can' to a 'must' in the following text:
>=20
>     As a special case, if the PW Demultiplexer is an MPLS label, the
>     protocol architecture of section 5.4.2 can be used instead of the
>     protocol architecture of this section.

The reason the differentiation was based on IP was simple.
In the IP world the RTP header has a well-known location,
and it is not for use to change this, although it is inconvenient
for the MPLS case. Hence we based the decision on IP vs MPLS.

However, I agree that your comment is valid and it is more consistent to

base the positioning on the multiplexing layer.  I am just wondering
if anyone else has a problem with this (AVT or L2TPEXT WGs ...)

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 13:21:18 +0200
Lines: 20
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 22 12:24:23 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQP98jg+GIVyWf3QZaAu2XxYPQViwABgwog
To: "Alexander Vainshtein" <sasha@axerra.com>, <stbryant@cisco.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> [Sasha] The above-mentioned explicit reference to the=20
> MPLS-in-IP spec would make it clear that using an MPLS label=20
> as a demultiplexer actually makes PWs using them MPLS PWs=20
> regardless of the actual tunneling mechanism.

That's the problem!

I know that I have lost this battle multiple times,
but I still don't buy the idea that the obvious tactic of using=20
a double word header as the PW demux label =20
makes the PSN into MPLS.

In particular, does the use of this format for the PW label
mean that one MUST support label stacking?
(I don't see how you can rule that out in an MPLS network.)

Does it rule out non-LDP control protocols for PW setup?

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 15:14:47 +0200
Lines: 86
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org
X-From: pwe3-admin@ietf.org Mon Mar 22 14:20:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>, stbryant@cisco.com
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yaakov, Stewart and all,
Please see inline.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Monday, March 22, 2004 1:21 PM
> To: Sasha Vainshtein; stbryant@cisco.com
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
>  
> > [Sasha] The above-mentioned explicit reference to the 
> > MPLS-in-IP spec would make it clear that using an MPLS label 
> > as a demultiplexer actually makes PWs using them MPLS PWs 
> > regardless of the actual tunneling mechanism.
> 
> That's the problem!
> 
> I know that I have lost this battle multiple times,
> but I still don't buy the idea that the obvious tactic of using 
> a double word header as the PW demux label  
> makes the PSN into MPLS.
>
I am not sure I follow you. Stewart's text (to which my comment
refers) says:

<quote>
    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols,  e.g. an MPLS label, an
    L2TP session ID, or a UDP port number.
<end quote>

Let's start from a simple point: if PW label over an IP PSN
is an MPLS label, what protocol number must be set in
the IP header of the corresponding packets?

I see two options:

1) It is MPLS-in-IP protocol number (still to be assigned by IANA).
   If this is the case, then MPLS-in-IP encapsulation mechanism
   as described in draft-ietf-mpls-in-ip-or-gre-07 fully applies.
   Of course in this case the demultiplexor is an MPLS label, and,
   IMO, this is the only way to use an MPLS label as a demultiplexer
   for PWs over an IP PSN.

2) It is some new, not yet specified protocol (let's call it
   PW-in-IP). If this is the case, you may use any 32-bit 
   demultiplexer (a.k.a PW label) you wish but, IMHO, you 
   MUST NOT call this demultiplexer an MPLS label.
   (Of course, it would be also nice to specify such a protocol
   and to provide justification for adding it to the 
   set of already existing tunneling mechanisms.:-)
> 
> In particular, does the use of this format for the PW label
> mean that one MUST support label stacking?
> (I don't see how you can rule that out in an MPLS network.)
>
Of course, I may be totally wrong, but, IMHO, you are asking
the following question:

	Is it possible to terminate MPLS-in-IP PWs in PEs that
	do not support MPLS?

The answer depends on what you are going to do with such a device:
- you clearly cannot use it in MPLS networks
- you can, IMO< easily use it in IP networks for termination of MPLS-in-IP
  PWs.
> 
> Does it rule out non-LDP control protocols for PW setup?
>
IMO, no. You can always use manual PW setup. 
>

> 
> Y(J)S
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Roy, Anindya (Anindya)" <anroy@lucent.com>
Subject: PWE3 state information in context to ATM
Date: Mon, 22 Mar 2004 10:00:42 -0500
Lines: 51
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-8"
X-From: pwe3-admin@ietf.org Mon Mar 22 16:04:11 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>



-----Original Message-----
From: Sasha Vainshtein [mailto:Sasha@AXERRA.com]
Sent: Monday, March 22, 2004 8:15 AM
To: 'Yaakov Stein'; stbryant@cisco.com
Cc: pwe3@ietf.org
Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture


Yaakov, Stewart and all,
Please see inline.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Monday, March 22, 2004 1:21 PM
> To: Sasha Vainshtein; stbryant@cisco.com
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
>  
> > [Sasha] The above-mentioned explicit reference to the 
> > MPLS-in-IP spec would make it clear that using an MPLS label 
> > as a demultiplexer actually makes PWs using them MPLS PWs 
Hi All,
	 
Would like to get the groups view on the following issue.

PWs can fail in a single direction or in both directions.However this may not be acceptable when the PWE3 are used to emulate ATM Layer2 connections, to maintain the integrity of the  bidirectional property of ATM connections.

My understanding is in order to preserve the integrity of the BI-DIRECTIONAL property of ATM VC/VP, any or both of the  following MUSTBE supported.

(1) If a PWE3 is emulating a ATM Layer 2 service, the PW must be bound to a *bi-directional* PSN tunnel because of the ATM's  bidirectional connection properties ?

(2) Incase the PW is allowed to setup over two disjoint unidirectional tunnels in each direction, then the implementation must maintain state information of both the tunnels in order to synchronize the operational state of the ATM VC's in both the  direction to handle situations of PSN failures in single direction.

 
If there is already a proposed solution can someone please provide a pointer.

Thanks.
Anindya


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Roy, Anindya (Anindya)" <anroy@lucent.com>
Subject: PWE3 state information in context to ATM
Date: Mon, 22 Mar 2004 10:12:23 -0500
Lines: 18
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-8"
X-From: pwe3-admin@ietf.org Mon Mar 22 16:15:05 2004
Return-path: <pwe3-admin@ietf.org>
To: "Roy, Anindya (Anindya)" <anroy@lucent.com>,
        "'pwe3@ietf.org'"
	 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Hi All,
	 
Would like to get the groups view on the following issue.

PWs can fail in a single direction or in both directions.However this may not be acceptable when the PWE3 are used to emulate ATM Layer2 connections, to maintain the integrity of the  bidirectional property of ATM connections.

My understanding is in order to preserve the integrity of the BI-DIRECTIONAL property of ATM VC/VP, any or both of the  following MUSTBE supported.

(1) If a PWE3 is emulating a ATM Layer 2 service, the PW must be bound to a *bi-directional* PSN tunnel because of the ATM's  bidirectional connection properties ?

(2) Incase the PW is allowed to setup over two disjoint unidirectional tunnels in each direction, then the implementation must maintain state information of both the tunnels in order to synchronize the operational state of the ATM VC's in both the  direction to handle situations of PSN failures in single direction.

 
If there is already a proposed solution can someone please provide a pointer.

Thanks.
Anindya


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Proposal to Progress draft-orly-pwe3-satop-mib and draft-orly-pwe3-tdm-mib
Date: Mon, 1 Mar 2004 08:32:13 -0500
Organization: Cisco Systems, inc.
Lines: 83
Sender: pwe3-admin@ietf.org
References: <27A0F290348F8E45AEF79889DDE65A52022C3AFE@exrad2.ad.rad.co.il>
Reply-To: <tnadeau@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 01 14:35:11 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Orly Nicklass'" <orly_n@rad.com>, <pwe3@ietf.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <27A0F290348F8E45AEF79889DDE65A52022C3AFE@exrad2.ad.rad.co.il>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


	A few comments. First, they are both short and sweet, which
I like. 8)   Second, Although both MIB modules state that they
fit into the existing MIB framework, and have
figures that show that they do, it is unclear to me
as to how they do. For exaple, they both seem to define their
own indexing, and do not describe how this interacts with
the PW-MIB as well as the native TDM (DSx) MIBs. For
example, the way all of the existing service "glue" MIBs
work is to use the PwIndex as common index:

  pwVcEnetEntry  OBJECT-TYPE 
      SYNTAX     PwVcEnetEntry 
      MAX-ACCESS  not-accessible 
      STATUS     current 
      DESCRIPTION  
          "This table is indexed by the same index that was created  
          for the associated entry in the PW Table in the PW MIB. 
          The PwVcIndex and the pwVcEnetPwVlan are used as indexes  
          to allow multiple VLANs to exist on the same PW. 
                           
          An entry is created in this table by the agent for every  
          entry in the pwVcTable with a pwVcType of 'ethernetTagged' 
          or 'ethernet'. Additional rows may be created by the  
          operator or the agent if multiple entries are required for 
          the same PW. 
        
          This table provides Ethernet port mapping and VLAN  
          configuration for each Ethernet PW." 
   
      INDEX { pwVcIndex, pwVcEnetPwVlan } 
      ::= { pwVcEnetTable 1 } 

	This allows one to look at the PW in the PW-MIB based on
the PwIndex and then look at the pwVcType associated with that
entry and quickly know how to find either the PSN or service
"glue" MIB entry because it uses that same entry. Please
make sure you use this.

	Please make sure these MIBs are aligned for configuration 
with the existing MIBs.

	Finally, please check the PwVcType TC in
draft-ietf-pwe3-pw-tc-mib-04.txt
to make sure that the appopriate Vc Types are defined there to
support your new modules as described above.

	So as long a the above are completed, I see no
reason why these both shouldn't be made WG drafts.

	--Tom



> Hi All, 
> 
> Following my presentation today in Seoul, 
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-satop-mib-00.txt
> 
> http://www.dspcsp.com/tdmoip/draft-orly-pwe3-TDM-mib-00.txt

I would like to proceed with a proposal to progress the drafts as
Working Group items. 
Please comment. 
 

Orly Nicklass, PhD
Associate VP R&D,
RAD Data Communications Ltd,
24 Raoul Wallenberg St.
Tel Aviv, 69719, Israel
Tel : +972 3 765 9969; Fax : +972 3 644 0930
email: orly_n@rad.com
RAD's web site : www.rad.com



 

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


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Busschbach, Peter B (Peter)" <busschbach@lucent.com>
Subject: RE: PWE3 state information in context to ATM
Date: Mon, 22 Mar 2004 10:32:24 -0500
Lines: 54
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
X-From: pwe3-admin@ietf.org Mon Mar 22 16:35:08 2004
Return-path: <pwe3-admin@ietf.org>
To: "Roy, Anindya (Anindya)" <anroy@lucent.com>,
        "'pwe3@ietf.org'"
	 <pwe3@ietf.org>
X-Mailer: Internet Mail Service (5.5.2657.72)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Anindya,

See draft-nadeau-pwe3-oam-msg-map-04.txt

Section 6 covers the mapping of PW failures and alarms to ATM alarms and vice versa. Section 4.7 discusses some issues regarding the bi-directional nature of Pseudo Wires.

One point that is not clearly covered in the current draft and that was pointed out by Neil Harrison is that even if only one direction of a PW is down, from a perspective of SLAs and Performance Monitoring the entire emulated ATM VC must be considered failed.

Peter

> -----Original Message-----
> From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> Sent: Monday, March 22, 2004 10:12 AM
> To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> Subject: [PWE3] PWE3 state information in context to ATM
> 
> 
> 
> Hi All,
> 	 
> Would like to get the groups view on the following issue.
> 
> PWs can fail in a single direction or in both 
> directions.However this may not be acceptable when the PWE3 
> are used to emulate ATM Layer2 connections, to maintain the 
> integrity of the  bidirectional property of ATM connections.
> 
> My understanding is in order to preserve the integrity of the 
> BI-DIRECTIONAL property of ATM VC/VP, any or both of the  
> following MUSTBE supported.
> 
> (1) If a PWE3 is emulating a ATM Layer 2 service, the PW must 
> be bound to a *bi-directional* PSN tunnel because of the 
> ATM's  bidirectional connection properties ?
> 
> (2) Incase the PW is allowed to setup over two disjoint 
> unidirectional tunnels in each direction, then the 
> implementation must maintain state information of both the 
> tunnels in order to synchronize the operational state of the 
> ATM VC's in both the  direction to handle situations of PSN 
> failures in single direction.
> 
>  
> If there is already a proposed solution can someone please 
> provide a pointer.
> 
> Thanks.
> Anindya
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Danny McPherson <danny@tcb.net>
Subject: IETF59 PWE3 Minutes
Date: Mon, 22 Mar 2004 08:50:38 -0700
Lines: 15
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 22 16:53:02 2004
Return-path: <pwe3-admin@ietf.org>
To: pwe3@ietf.org
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Folks,
The minutes from the PWE3 IETF59 meeting in Seoul
are available here:

http://pwe3.tcb.net/meetings/ietf59/minutes.txt

Please provide comments by Friday, March 26.

(yes, yes, and apologies for the late distribution of the
minutes).

Thanks!

-danny


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 18:11:15 +0200
Lines: 97
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Mon Mar 22 17:14:13 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQQD8tjyWnK/O5BQUa7veZ/9MrvSAAFDZEQ
To: <stbryant@cisco.com>, "Alexander Vainshtein" <sasha@axerra.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Sasha,

As conventional, my remarks are in-lined.=20

<snip>
> Let's start from a simple point: if PW label over an IP PSN=20
> is an MPLS label, what protocol number must be set in the IP=20
> header of the corresponding packets?
>=20
> I see two options:
>=20
> 1) It is MPLS-in-IP protocol number (still to be assigned by IANA).
>    If this is the case, then MPLS-in-IP encapsulation mechanism
>    as described in draft-ietf-mpls-in-ip-or-gre-07 fully applies.
>    Of course in this case the demultiplexor is an MPLS label, and,
>    IMO, this is the only way to use an MPLS label as a demultiplexer
>    for PWs over an IP PSN.
>=20
> 2) It is some new, not yet specified protocol (let's call it
>    PW-in-IP). If this is the case, you may use any 32-bit=20
>    demultiplexer (a.k.a PW label) you wish but, IMHO, you=20
>    MUST NOT call this demultiplexer an MPLS label.
>    (Of course, it would be also nice to specify such a protocol
>    and to provide justification for adding it to the=20
>    set of already existing tunneling mechanisms.:-)

This is the same debate we had regarding Ethertypes
in another forum ...

It seems obvious to me that when using UDP/IP the IP protocol type=20
is set to obviously 11H, signifying UDP. Then the UDP destination
port MUST be set to an application identifier assigned
by IANA to the PW type being used. As you know,
IANA has assigned 085EH to TDMoIP for this purpose.
We should request port numbers for the various PW types.

If you choose NOT to use UDP, rather L2TP,
then the protocol is set to 73H.=20
Similarly, if use use MPLS-in-IP, then you use=20
whatever IANA decides.

The question arises - where is the PW label=20
for the UDP case? Well, this is the function of the UDP
port, but that has already been taken, so the only sensible
thing to do is to use the UDP source port.

This actually makes a lot of sense, since it=20
1) allows standard use of the UDP destination port
   (solving the problem you raised)
2) doesn't require an additional field (there is already a=20
   16 bit field sitting there...)
3) according to our standard use the PW label is a=20
   downstream (source) identifier.


> In particular, does the use of this format for the PW label=20
> mean that one MUST support label stacking?
> > (I don't see how you can rule that out in an MPLS network.)
> >
> Of course, I may be totally wrong, but, IMHO, you are asking=20
> the following question:
>=20
> 	Is it possible to terminate MPLS-in-IP PWs in PEs that
> 	do not support MPLS?

Why such a complex way of reading an easy question.
You stated (and have defended this view in the past)
that by using an MPLS-like label, we are effectively creating
an MPLS network. In that case, the network has to act like an MPLS
network.
=20
> The answer depends on what you are going to do with such a device:
> - you clearly cannot use it in MPLS networks
> - you can, IMO, easily use it in IP networks for termination of
MPLS-in-IP PWs.

... or could you terminate the IP layer and launch the MPLS packets
into an MPLS network ?

> >=20
> > Does it rule out non-LDP control protocols for PW setup?
> >
> IMO, no. You can always use manual PW setup.=20

Yes, of course. But I was asking whether alternative
control PROTOCOLS are ruled out.=20

Although UDP/IP has been with us in PWE from the beginning,
we have tacitly assumed MPLS in almost everything we have done.
In particular, the control protocol is LDP based.

Of course, there is nothing wrong with using targetted LDP
in a pure IP network for this purpose. But perhaps we may want
to do something else (I intend writing a draft before the next
meeting on this subject).

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 18:32:41 +0200
Lines: 41
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>, <stbryant@cisco.com>
X-From: pwe3-admin@ietf.org Mon Mar 22 17:37:20 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQQKboOcidqb6R/S4OOinW/Fbj6OAAAJzEA
To: "Alexander Vainshtein" <sasha@axerra.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Sasha,=20

<snip>
> Sorry, but I do not follow you. The ORIGINAL question
> (AFAIK) has been usage of an MPLS label as  a demultiplexer=20
> (a.k.a. PW label) in PWs over an IP PSN. I have suggested=20
> that the (only, IMO) correct way to do that is by using=20
> MPLS-in-IP (with all the implications). How is your=20
> explanation above related to that?

The original question (AFAIK) was where to put the PW
label in the UDP/IP case, and what effect that decision
has on the protocols.

I suggested that there was no good reason
to interpose an MPLS-like label
(except in cases where 16 bits are not enough, but 20 are).

(Similarly, although off-topic here,
 I think that VLAN tags could be used,
 assuming that 4K labels are enough.)

> I'd say that the control protocol for distribution of PW=20
> labels depends on the nature of these labels. E.g., LDP is=20
> one of the native choices for distributing MPLS labels=20
> serving as a PW label; and L2TPv3 uses its own way of=20
> distributing Session IDs.

I'll go along with that, except that for pure UDP/IP
we don't have a protocol yet.

> In both cases the point is not inventing a new protocol.
> IMO, if you want to use UDP as the demultiplexing layer, and=20
> define correctly which UDP port is used as the demultiplexer,=20
> you can reuse some suitable protocol as well.

What do you mean by correctly (source or destination) ?

What protocol do you suggest?

Y)J(S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 18:20:53 +0200
Lines: 106
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, stbryant@cisco.com
X-From: pwe3-admin@ietf.org Mon Mar 22 17:38:31 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Yaakov and all,
Please see inline.
With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Monday, March 22, 2004 6:11 PM
> To: stbryant@cisco.com; Sasha Vainshtein
> Cc: pwe3@ietf.org
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> Sasha,
> 
> As conventional, my remarks are in-lined. 
> 
> <snip>
> > Let's start from a simple point: if PW label over an IP PSN 
> > is an MPLS label, what protocol number must be set in the IP 
> > header of the corresponding packets?
> > 
> > I see two options:
> > 
> > 1) It is MPLS-in-IP protocol number (still to be assigned by IANA).
> >    If this is the case, then MPLS-in-IP encapsulation mechanism
> >    as described in draft-ietf-mpls-in-ip-or-gre-07 fully applies.
> >    Of course in this case the demultiplexor is an MPLS label, and,
> >    IMO, this is the only way to use an MPLS label as a demultiplexer
> >    for PWs over an IP PSN.
> > 
> > 2) It is some new, not yet specified protocol (let's call it
> >    PW-in-IP). If this is the case, you may use any 32-bit 
> >    demultiplexer (a.k.a PW label) you wish but, IMHO, you 
> >    MUST NOT call this demultiplexer an MPLS label.
> >    (Of course, it would be also nice to specify such a protocol
> >    and to provide justification for adding it to the 
> >    set of already existing tunneling mechanisms.:-)
> 
> This is the same debate we had regarding Ethertypes
> in another forum ...
> 
> It seems obvious to me that when using UDP/IP the IP protocol type 
> is set to obviously 11H, signifying UDP. Then the UDP destination
> port MUST be set to an application identifier assigned
> by IANA to the PW type being used. As you know,
> IANA has assigned 085EH to TDMoIP for this purpose.
> We should request port numbers for the various PW types.
> 
> If you choose NOT to use UDP, rather L2TP,
> then the protocol is set to 73H. 
> Similarly, if use use MPLS-in-IP, then you use 
> whatever IANA decides.
>
Sorry, but I do not follow you. The ORIGINAL question
(AFAIK) has been usage of an MPLS label as  a demultiplexer
(a.k.a. PW label) in PWs over an IP PSN. I have suggested 
that the (only, IMO) correct way to do that is by using 
MPLS-in-IP (with all the implications). How is your explanation
above related to that?
> 
> The question arises - where is the PW label 
> for the UDP case? Well, this is the function of the UDP
> port, but that has already been taken, so the only sensible
> thing to do is to use the UDP source port.
>
This is a different question that has not been even asked 
in the architecture document. I suggest to discuss it in another 
thread. As you know, I keep different opinion wrt to what
does and what does not makes sense here. 
>
... snipped ...
> > > Does it rule out non-LDP control protocols for PW setup?
> > >
> > IMO, no. You can always use manual PW setup. 
> 
> Yes, of course. But I was asking whether alternative
> control PROTOCOLS are ruled out. 
> 
> Although UDP/IP has been with us in PWE from the beginning,
> we have tacitly assumed MPLS in almost everything we have done.
> In particular, the control protocol is LDP based.
> 
> Of course, there is nothing wrong with using targetted LDP
> in a pure IP network for this purpose. But perhaps we may want
> to do something else (I intend writing a draft before the next
> meeting on this subject).
>
I'd say that the control protocol for distribution of PW labels
depends on the nature of these labels. E.g., LDP is one of
the native choices for distributing MPLS labels serving as a
PW label; and L2TPv3 uses its own way of distributing Session IDs.
In both cases the point is not inventing a new protocol.
IMO, if you want to use UDP as the demultiplexing layer, and
define correctly which UDP port is used as the demultiplexer, you
can reuse some suitable protocol as well.
> 
> Y(J)S
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: neil.2.harrison@bt.com
Subject: RE: PWE3 state information in context to ATM
Date: Mon, 22 Mar 2004 17:56:34 -0000
Lines: 133
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Content-Transfer-Encoding: quoted-printable
X-From: pwe3-admin@ietf.org Mon Mar 22 18:59:16 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
Thread-Topic: [PWE3] PWE3 state information in context to ATM
Thread-Index: AcQQI1aw31X3fgz+TWWCpX28CqzHhAADDX+w
To: <busschbach@lucent.com>, <anroy@lucent.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 22 Mar 2004 17:56:34.0971 (UTC) FILETIME=[04021EB0:01C41037]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Thanks Peter....small additional remark in-line....regards, Neil

> -----Original Message-----
> From: pwe3-admin@ietf.org [mailto:pwe3-admin@ietf.org]On=20
> Behalf Of Busschbach, Peter B (Peter)
> Sent: 22 March 2004 15:32
> To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> Subject: RE: [PWE3] PWE3 state information in context to ATM
>=20
>=20
> Anindya,
>=20
> See draft-nadeau-pwe3-oam-msg-map-04.txt
>=20
> Section 6 covers the mapping of PW failures and alarms to ATM=20
> alarms and vice versa. Section 4.7 discusses some issues=20
> regarding the bi-directional nature of Pseudo Wires.
>=20
> One point that is not clearly covered in the current draft=20
> and that was pointed out by Neil Harrison is that even if=20
> only one direction of a PW is down, from a perspective of=20
> SLAs and Performance Monitoring the entire emulated ATM VC=20
> must be considered failed.

NH=3D> Peter is right to mention this.  But it is also dependent on =
having consistent interpretations wrt processing events.  That is, there =
is a clear 'ordering' behaviour here which goes along these lines:

1	Get the arch of the mode in question right first.....

2	If you don't do this then you will not be able to correctly identify =
the relevant defects....the defects of a cl-ps mode (eg IP) are not the =
same as those that can occur in a co-ps mode (eg MPLS), and these are =
also not the same as the defects that can occur in a co-cs mode (eg =
SDH).  Now if you violate the arch of the mode (eg mp2p or PHP in MPLS) =
then you are asking for trouble, as the defects now get rather complex =
to detect/diagnose/handle (understatement).......hopefully many of you =
should know the story from here on in by now ;-)

3	You then need to define suitable OAM that can consistently and =
automatically detect/handle the identified defects, ie we need known =
entry/exit criteria and consequent actions specifying.

4	Now you can specify the unavailable entry/exit state of the trails =
based on defect persistency.....and this is where the 'ORing' of =
unidirectional failures that Peter mentioned is important because.......

5	Net Performance metrics (ie loss, errors, delay) are only meaningful =
whilst the trail is in the available state.  These are unidirectional in =
context whilst both directions are in the available state, but on =
failure of any direction then Net Perf measurements of both directions =
are no longer meaningful (at least wrt to any Net Perf SLA context).

6	Finally (though this should also be thought about up-front....well I =
did this anyway when drafting Y.1710/11), one needs to take a holistic =
view across all the possible client/server relationships to ensure there =
is some harmonised sense of consistency wrt what is being specified in =
each layer network in terms of defects, unavailability and Net Perf =
metrics.  This can't be totally aligned because each of the 3 modes are =
different.  However, some consideration of the harmonisation of these =
aspects is important because it has commercial implications for operator =
interworking and the services being offered.  Further, if MPLS is ever =
to achieve its potential to become a key convergence technology (and a =
few things need to happen for this to be true in our view), we operators =
will also need to think about global reference connections and the fair =
allocations of objectives in a horizontally partitioned sense, ie same =
layer network, between operators.  And how well one can address this is =
predicated on getting the ordering and consistency (of specification) as =
described above right.

Unfortunately PWs don't really help in any of this if you think about =
it....we need to do this wrt to the entity that is being =
*networked*....so that is a cl-ps pkt in IP and a co-ps trail in MPLS.  =
I wish folks would wise up on this sooner rather than later.

Now I don't think you can do this lot much simpler than what has been =
specified in Y.1711.

regards, Neil

>=20
> Peter
>=20
> > -----Original Message-----
> > From: Roy, Anindya (Anindya) [mailto:anroy@lucent.com]
> > Sent: Monday, March 22, 2004 10:12 AM
> > To: Roy, Anindya (Anindya); 'pwe3@ietf.org'
> > Subject: [PWE3] PWE3 state information in context to ATM
> >=20
> >=20
> >=20
> > Hi All,
> > 	=20
> > Would like to get the groups view on the following issue.
> >=20
> > PWs can fail in a single direction or in both=20
> > directions.However this may not be acceptable when the PWE3=20
> > are used to emulate ATM Layer2 connections, to maintain the=20
> > integrity of the  bidirectional property of ATM connections.
> >=20
> > My understanding is in order to preserve the integrity of the=20
> > BI-DIRECTIONAL property of ATM VC/VP, any or both of the =20
> > following MUSTBE supported.
> >=20
> > (1) If a PWE3 is emulating a ATM Layer 2 service, the PW must=20
> > be bound to a *bi-directional* PSN tunnel because of the=20
> > ATM's  bidirectional connection properties ?
> >=20
> > (2) Incase the PW is allowed to setup over two disjoint=20
> > unidirectional tunnels in each direction, then the=20
> > implementation must maintain state information of both the=20
> > tunnels in order to synchronize the operational state of the=20
> > ATM VC's in both the  direction to handle situations of PSN=20
> > failures in single direction.
> >=20
> > =20
> > If there is already a proposed solution can someone please=20
> > provide a pointer.
> >=20
> > Thanks.
> > Anindya
> >=20
> > _______________________________________________
> > pwe3 mailing list
> > pwe3@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pwe3
> >=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>=20


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: draft-nadeau-pwe3-oam-msg-map-04.txt
Date: Mon, 22 Mar 2004 21:30:04 +0000
Organization: Cisco Systems, Inc.
Lines: 9
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-From: pwe3-admin@ietf.org Mon Mar 22 22:34:07 2004
Return-path: <pwe3-admin@ietf.org>
X-BrightmailFiltered: true
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@ietf.org" <pwe3@ietf.org>,
        "Monique Morrow (mmorrow)" <mmorrow@cisco.com>,
        "Tom Nadeau (tnadeau)" <tnadeau@cisco.com>,
        Danny McPherson <danny@arbor.net>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

The comments to the list indicated that there is WG consensus
to make

http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt

a WG draft. Please will the authors resubmit with the standard
WG title, copying the WG chairs.

- Stewart


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Sasha Vainshtein <Sasha@AXERRA.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Tue, 23 Mar 2004 10:41:48 +0200
Lines: 100
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-8"
Cc: pwe3@ietf.org, stbryant@cisco.com
X-From: pwe3-admin@ietf.org Tue Mar 23 09:49:09 2004
Return-path: <pwe3-admin@ietf.org>
To: "'Yaakov Stein'" <yaakov_s@rad.com>
X-Mailer: Internet Mail Service (5.5.2653.19)
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

Yaakov and all,
Please see some answers inline.

With best regards,
                                   Sasha Vainshtein
email:     sasha@axerra.com <mailto:sasha@axerra.com> 
tel:       +972-3-7659993 (office)
           +972-8-9254948 (res.)
           +972-58-674833 (cell.)
 


> -----Original Message-----
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Monday, March 22, 2004 6:33 PM
> To: Sasha Vainshtein
> Cc: pwe3@ietf.org; stbryant@cisco.com
> Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
> 
> 
> Sasha, 
> 
> <snip>
> > Sorry, but I do not follow you. The ORIGINAL question
> > (AFAIK) has been usage of an MPLS label as  a demultiplexer 
> > (a.k.a. PW label) in PWs over an IP PSN. I have suggested 
> > that the (only, IMO) correct way to do that is by using 
> > MPLS-in-IP (with all the implications). How is your 
> > explanation above related to that?
> 
> The original question (AFAIK) was where to put the PW
> label in the UDP/IP case, and what effect that decision
> has on the protocols.
>
This may well be so. However, it did not, IMHO, leave any mark
in the text of the updated architecture draft beyond the basic 
point of declaring UDP as a valid PW demultiplexer mechanism for 
IP PSNs. As I have said already, I support this.
> 
> I suggested that there was no good reason
> to interpose an MPLS-like label
> (except in cases where 16 bits are not enough, but 20 are).
> 
> (Similarly, although off-topic here,
>  I think that VLAN tags could be used,
>  assuming that 4K labels are enough.)
>
Sorry, I did not understand that - neither from the text of
the draft nor from the previous emails.
Just to make this point clear: do you object to using MPLS-in-IP 
as a valid mechanism for PWs over an IP PSN?
>
> > I'd say that the control protocol for distribution of PW 
> > labels depends on the nature of these labels. E.g., LDP is 
> > one of the native choices for distributing MPLS labels 
> > serving as a PW label; and L2TPv3 uses its own way of 
> > distributing Session IDs.
> 
> I'll go along with that, except that for pure UDP/IP
> we don't have a protocol yet.
>
I agree. 
>
> > In both cases the point is not inventing a new protocol.
> > IMO, if you want to use UDP as the demultiplexing layer, and 
> > define correctly which UDP port is used as the demultiplexer, 
> > you can reuse some suitable protocol as well.
> 
> What do you mean by correctly (source or destination) ?
>
I think that using source UDP port as the PW demultiplexer, 
does not match the PWE3 architecture, while the destination UDP 
port for the same purpose does. 

I suggest to move this discussion to a separate email thread 
because it is not, IMO, related to the contents of Section 5.4.1 
of the PW Architecture draft as this Section stands now.
> 
> What protocol do you suggest?
>
I am not sure that one is needed. I have not found a suitable
existing protocol (but, maybe, my search went wrong:-), and
development of a brand new protocol with properties similar to
these of the L2TPv3 control plane does not seem justified.
(At the moment even the requirements for such a protocol have
not been clearly specified, but I believe that they should
include reliable transport, tie-breaking, ability to convey
status of attachment circuits etc. - in short, they would
be very similar to any other control protocol with the only
difference being the pool from which the PW demultiplexers
are allocated).

So if you need a control plane for PWs over IP - and I believe
one is often required, and if the requirements for such a control
plane are similar to thoses met by the L2TPv3 control plane,
why not to use L2TPv3 in the data plane as well and save the
development effort?
> 
> Y)J(S
> 


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Yaakov Stein" <yaakov_s@rad.com>
Subject: RE: Proposed change to 5..4.1 of PWE3 architecture
Date: Tue, 23 Mar 2004 11:32:29 +0200
Lines: 58
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <pwe3@ietf.org>, <stbryant@cisco.com>
X-From: pwe3-admin@ietf.org Tue Mar 23 10:36:12 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
Thread-Topic: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Thread-Index: AcQQs0V8pgwa0DXFQVaIFuWD3EQV3gABXI3g
To: "Alexander Vainshtein" <sasha@axerra.com>
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>

=20
> Sorry, I did not understand that - neither from the text of=20
> the draft nor from the previous emails.
> Just to make this point clear: do you object to using=20
> MPLS-in-IP as a valid mechanism for PWs over an IP PSN?

No, I believe MPLS-in-IP is a valid mechanism.

<snip>

> I think that using source UDP port as the PW demultiplexer,=20
> does not match the PWE3 architecture, while the destination=20
> UDP port for the same purpose does.=20

If by PWE architecture you mean what is stated in the PWE3 architecture
draft,
then I would like to see where precisely in the architecture draft you
see
anything relevant.

The whole issue started by my stating that I couldn't find
anything in the architecture draft that mentioned the use
of UDP ports, one way or the other.


> I am not sure that one is needed. I have not found a suitable=20
> existing protocol (but, maybe, my search went wrong:-), and=20
> development of a brand new protocol with properties similar=20
> to these of the L2TPv3 control plane does not seem justified.

I assume that you agree that one is needed for MPLS
and for L2TP, so why is it not clear that one is needed here?
=20
> (At the moment even the requirements for such a protocol have=20
> not been clearly specified,=20

They have been specified as clearly as they have been for MPLS.

> but I believe that they should=20
> include reliable transport, tie-breaking, ability to convey=20
> status of attachment circuits etc. - in short, they would be=20
> very similar to any other control protocol with the only=20
> difference being the pool from which the PW demultiplexers=20
> are allocated).
>=20
> So if you need a control plane for PWs over IP - and I=20
> believe one is often required, and if the requirements for=20
> such a control plane are similar to thoses met by the L2TPv3=20
> control plane, why not to use L2TPv3 in the data plane as=20
> well and save the development effort?

So we agree that a control protocol is required.

I am not ruling out use of L2TP, but I believe that pure UDP/IP
is a perfectly valid data payload format, and one that I have been
tacitly assuming all along (see all versions of draft-anavi).

Y(J)S


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: Stewart Bryant <stbryant@cisco.com>
Subject: [Fwd: RE: Proposed change to 5..4.1 of PWE3 architecture]
Date: Tue, 23 Mar 2004 16:31:00 +0000
Organization: Cisco Systems, Inc.
Lines: 93
Sender: pwe3-admin@ietf.org
Reply-To: stbryant@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
X-From: pwe3-admin@ietf.org Tue Mar 23 17:37:36 2004
Return-path: <pwe3-admin@ietf.org>
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>,
        "'Sasha Vainshtein'" <Sasha@axerra.com>,
        Yaakov Stein <yaakov_s@rad.com>
Content-Transfer-Encoding: 7bit
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


I lost track in some of the thread that followed this.

Sasha wants references to UDP, L2TP etc. These I can add.

There was some discussion about control protocols for UDP.
These are not excluded by the proposed text, and we do
not have a proposal for such a protocol.

I think that you all agreed that although not optimal
the text is technicall correct.

Can we live with this and move on?

If not, please can we focus on specific edit proposals
to this section.

Thanks

Stewart


-------- Original Message --------
Subject: RE: [PWE3] Proposed change to 5..4.1 of PWE3 architecture
Date: Mon, 22 Mar 2004 09:35:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
Reply-To: stbryant@cisco.com
Organization: Cisco Systems, Inc.
To: pwe3@ietf.org <pwe3@ietf.org>

Following Ron's input, the proposed new text for 5.4.1 is:


5.4.1. PWE3 over an IP PSN

    The protocol definition of PWE3 over an IP PSN should employ existing
    IETF protocols where possible.

        +---------------------+              +-------------------------+
        |      Payload        |------------->| Raw payload if possible |
        /=====================\              +-------------------------+
        H Payload Convergence H-----------+->|     Flags, seq # etc    |
        H---------------------H          /   +-------------------------+
        H       Timing        H---------/--->|            RTP          |
        H---------------------H        /     +-------------+           |
        H     Sequencing      H----one of    |             |
        \=====================/        \     |             +-----------+
        |  PW Demultiplexer   |---------+--->|     L2TP, MPLS etc.     |
        +---------------------+              +-------------------------+
        |  PSN Convergence    |------------->|       Not needed        |
        +---------------------+              +-------------------------+
        |        PSN          |------------->|            IP           |
        +---------------------+              +-------------------------+
        |      Data-link      |------------->|         Data-link       |
        +---------------------+              +-------------------------+
        |       Physical      |------------->|          Physical       |
        +---------------------+              +-------------------------+

      Figure 10: PWE3 over an IP PSN

    Figure 10 shows the protocol layering for PWE3 over an IP PSN. As a
    rule, the payload should be carried as received from the NSP, with
    the Payload Convergence Layer provided when needed.  However in
    certain circumstances it may be justifiable to transmit the payload
    in some processed form. The reasons for this must be documented in
    the Encapsulation Layer definition for that payload type.

    Where appropriate, explicit timing is provided by RTP [RFC3550],
    which when used also provides a sequencing service.  When the PSN is
    UDP/IP, the RTP header follows the UDP header and precedes the PW
    control field, while for all other cases the RTP header follows the
    PW control header.

    The encapsulation layer may additionally carry a sequence number;
    sequencing is to be provided either by RTP, or by the PW
    encapsulation layer but not both.

    PW Demultiplexing is provided by the PW label, which may take the
    form specified in a number of IETF protocols,  e.g. an MPLS label, an
    L2TP session ID, or a UDP port number.

    When PWs are carried over IP the PSN Convergence Layer will not be
    needed.

    As a special case, if the PW Demultiplexer is an MPLS label, the
    protocol architecture of section 5.4.2 must be used instead of the
    protocol architecture of this section.

========================

This differs from the previous CHANGED text in the last sentence in that
it used to read "section 5.4.2 can be used" and now reads "section 5.4.2
must be used"


From pwe3-admin@ietf.org  Wed Dec 27 17:03:40 2006
From: "Monique Morrow (mmorrow)" <mmorrow@cisco.com>
Subject: RE: Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Date: Mon, 1 Mar 2004 15:10:12 +0100
Lines: 221
Sender: pwe3-admin@ietf.org
Mime-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: <andy.bd.reid@bt.com>, <alan.mcguire@bt.com>, <peter.j.willis@bt.com>,
        <richard.spencer@bt.com>, <benjamin.niven-jenkins@bt.com>,
        <dave.milham@bt.com>
X-From: pwe3-admin@ietf.org Mon Mar 01 15:39:05 2004
Return-path: <pwe3-admin@ietf.org>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
Thread-Topic: [PWE3] Proposal to Progress draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item
Thread-Index: AcP/QaZLxoiOGyWlT5qnfT6ESC3LvgAKDCggAAsWmkA=
To: <neil.2.harrison@bt.com>, <pwe3@ietf.org>
X-OriginalArrivalTime: 01 Mar 2004 14:10:13.0680 (UTC) FILETIME=[EA40D300:01C3FF96]
Content-Transfer-Encoding: quoted-printable
Errors-To: pwe3-admin@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
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>


Neil,

Note the authors of the document are large and part carriers who have
contributed to it --

I have not seen your contribution/draft proposal in the IETF yet
(hopefully this is forthcoming).

I would also like to note for the record, that this draft had been
proposed as WG item post IETF 58.

We have aligned the document as per the current scope of PWE3.

Regards,

/Monique
-----Original Message-----
From: neil.2.harrison@bt.com [mailto:neil.2.harrison@bt.com]=20
Sent: 01 March 2004 13:55
To: Monique Morrow (mmorrow); pwe3@ietf.org
Cc: andy.bd.reid@bt.com; alan.mcguire@bt.com; peter.j.willis@bt.com;
richard.spencer@bt.com; benjamin.niven-jenkins@bt.com;
dave.milham@bt.com
Subject: RE: [PWE3] Proposal to Progress
draft-nadeau-pwe3-oam-msg-map-04.txt as a PWE3 WG Item


<converted to plain text from original HTML format>

Monique Morrow wrote 01 March 2004 04:00
I presented OAM Msg Mapping status today in Seoul,
http://www.ietf.org/internet-drafts/draft-nadeau-pwe3-oam-msg-map-04.txt
with a proposal to progress the draft as a Working Group item =20
=20
Whilst we had no opposition the room, I would like to ensure that there
is consensus on the list to progress the draft as a WG item.
=20
Essentially, the draft has been revised to reflect like-to-like
constructs as per the scope of PWE3 and, covers fault detection and
alarm message mapping as two separate elements.
=3D=3D=3D=3D

We (ie BT) cannot support this document as it stands for several
reasons....for example:

1	No defects are defined anywhere (not just in here but in any
other IETF draft/rfc) in terms of clear entry/exit criteria and
consequent actions.  Note that the defects in MPLS are different to the
defects in IP.....which should not be surprising as their modes are
different, and even this draft recognises that fact (also see 4).  CF
Y.1711 where these are specified.


2	There is no demarcation between the available state and
unavailable state for network trail entities.  This means there is no
temporal basis for the specification of an availability SLA or a network
performance SLA, noting that the latter is only relevant to the
available state.  These impact network element specifications and thus
have consequential impact on NMS/OSS.  NE and NMS/OSS considerations are
important for an operator to see correctly executed.  CF Y.1711 where
the unavailable state is specified (as a consequential persistence of
defects).


3	Seq Nos cannot be left 'open-ended' wrt aberration handling.  At
some degree of persistent corruption a defect state must be declared.
This therefore requires entry/exit criteria and consequent actions
specifying.  We note this is at least recognised as an open issue in
section 4.1.1.


4	A PW is *not* a networked entity....it is just an adaptation
function (now whether it is a good adaptation function for the server
layer considered is a different consideration).  An LSP however is a
networked path entity in the case of using MPLS (co-ps mode).
Similarly, an IP pkt is also a networked entity (in the case of an IP
cl-ps mode server layer).  XoverMPLS is therefore not the same as
XoverIP....I am perplexed as to why this fact so hard for some folks to
grok/accept.  Is it to make the work palatable to IETF folks?  But who
is kidding who here?  Whilst this stance might be necessary to 'sell'
this stuff in IETF, speaking as an operator we can't afford to base
future network investments on such misplaced ideologies....we need this
stuff properly architecting else it will impact our costs (both capex
and opex) and the efficacy of the services we can offer. =20

This distinction between MPLS and IP is even recognised in the
draft.....for example, in section 4.1 it says:

"In case of MPLS there are additional failures (see also [ITU-T=20
   Y.1710]). E.g.=20
   =20
   . PW mislabeling, which could be due to a failure on the ingress PE=20
     or due to an over-writing of the PW label value somewhere along=20
     the way=20
   =20
   . Label swapping or LSP mismerge in the PSN network, which could=20
     result in the termination of a PW at the wrong egress PE.=20

   . Unintended self-replication (e.g. due to loops or denial-of-
     Service attacks) "

This is of course correct. Note that these defects *cannot* occur in a
cl-ps server layer like IP, which is precisely what the above text
implies, because a cl-ps server layer must always have a network
significant DA/SA pair in each packet.  However, when using a co-ps
forwarding mode like MPLS this is not the case.  Here we have a trail
entity (ie an LSP) that is constructed between addressable (ie network
significant) access points by the concatenation of a sequence of single
link-connection (downstream only) significant identifiers.

So given this is even recognised in the draft now (and as one reads
through the draft it becomes increasingly clear that the MPLS server
layer case is being treated quite differently to the IP server layer
case), then why not go the extra step and come clean by accepting that
we don't have to force XoverMPLS to be the same as XoverIP?  We could
have a nice/simple adaptation for carrying clients over arch compliant
MPLS now and really start to leverage the latent potential of MPLS.

Can someone please explain to us why this can't this be done (and please
don't use mp2p and PHP as excuses....we know these are broken arch
flavours of MPLS, we just have to live with these and move on....we
should not keep making further mistakes on the back of past mistakes)?


5	Can someone please explain to us why Y.1710 (which is largely
about principles/requirements) is at long last recognised in this draft
but Y.1711 is not recognised as a valid OAM solution for MPLS?  This is
especially puzzling for us as Y.1711 is simple and complete (wrt defect
and availability specifications) and was written by an operator.....so
one might get the hint here that it was something that we 'required' ;-)
It seems quite bizarre that this is not included (even for completeness
of reference), especially noting this remark at the end of section
4.2.2:

"Based on these observations, it is clear that a Service Provider has
the disposal of a variety of tools. There are many factors that
influence which combination of tools best meets its needs."=20

Is there some specific technical (or other) reason why Y.1711 cannot be
referenced?


6	In section 4.4 it says:

"Besides reporting PW failures, PW status is used to propagate AC
failures. When and how to use those messages is dependent on the
emulated protocol and will be explained in the subsequent paragraphs 5.3
and 6.3)."

This is generally incorrect.  If one respects the client/server
architectural requirements (in particular client and server layer
independence, and client layer transparency) then a failure of a client
layer network should have no consequential impact on any server layer.
The above statement is violating layer independence and it is therefore
not a good idea.  It's the same as asking a SDH network to carry an ATM
client (or any other client) layer's failure indications.

And what happens if the client and server layers are own by different
operating parties?  This is obviously a wrong behaviour here.

Each layer network must be self-contained and in a client/server
relationship they must be independent.

=20
7	In section 4.7 it says:

"PWs can fail in a single direction or in both directions. PEs SHOULD
keep track of the status of each individual direction. In other words, a
PE SHOULD be able to distinguish between the following states: "PW UP",
"PW Transmit Direction Down", "PW Receive Direction Down", "PW Receive
and Transmit Down".=20
  =20
The next two sections discuss under which conditions a PE enters and
exits these states. To avoid an unnecessarily complicated description,
only the states "PW UP" and "PW DOWN" are discussed without further
analysis whether it applies to one or two directions of the PW."

Be careful here.  Performance metrics apply unidirectionally and only to
the available state.  However, for many applications the failure of one
direction effectively means *both* directions must be considered as
failed.  Thus even if only a single direction fails (though to be
accurate, this actually means if one direction enters the unavailable
state) then the collection of performance metrics of *both* directions
should be suspended....at least wrt to their meaning against any
performance SLAs that are being measured.  Have a read of Y.1711, as
this explains what is required here.


8	In section 4.7.1 it says:

"Note that if the control session between the PEs fails, the PW is torn
down and needs to be re-established. As a consequence, control session
failure leads to disappearance of the PW, not to a PW Down state."=20

This should not be taken as a general requirement.  Failures of
control-plane components should not necessarily remove data-plane trails
that have been set-up.  This is particularly true in the case of
S-PVC-like constructs.


9	Towards the end of section 5.2 FR 'port-mode' is mentioned.
Similarly in section 6.2 wrt ATM 'transparent mapping' it says:

"In case of transparent mapping, where the PE does not keep track of the
status of individual ATM VPCs or VCCs, it is possible that a PE does not
know which VPCs and/or VCCs are active. In such a case there is a need
for another fault indication mechanism on the AC. This is beyond the
scope of this document."

'Port-mode' has no meaning in functional architecture terms.....and for
a good reason as the extract above demonstrates....and really ought not
to be used for any client case.


.....so far.....regards, Neil



=20
=20


