From pwe3-bounces@ietf.org Thu Feb 01 02:07:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCW13-0007th-8x; Thu, 01 Feb 2007 02:05:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCW11-0007tc-GM
	for pwe3@ietf.org; Thu, 01 Feb 2007 02:05:51 -0500
Received: from mx2-012.rad.co.il ([212.199.240.16] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCW10-0001Mp-2G
	for pwe3@ietf.org; Thu, 01 Feb 2007 02:05:51 -0500
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 01 Feb 2007 09:05:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] SAToP RTP frequency default
Date: Thu, 1 Feb 2007 09:05:39 +0200
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D0320887B@exrad3.ad.rad.co.il>
In-Reply-To: <8F242B230AD6474C8E7815DE0B4982D703B80056@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] SAToP RTP frequency default
Thread-Index: Acc/3A8i/u+tBcUtT8iqVoiPX7CozgF8cwmA
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "STUART VENTERS" <stuart.venters@adtran.com>,
	<pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Stuart,=20

I quite agree that 8 kHz is ridiculously low,=20
but disagree with your argument about the quantization noise this adds.

The 1/8 khz quantization noise adds local jitter but should have no
effect on the wander
in any implementation with even rudimentary clock recovery.

However, I am unsure what you mean about using the nominal TDM line
rate.
Of course using the actual TDM source clock is great if it is available=20
at the other end, but then you don't need a timestamp - just lock the
remote clock to it.

So I assume that you suggest using another clock which happens to be the
same
rate. This is also NOT a good idea, as the aliasing of the close rate
can be catastrophic
to clock recovery algorithms - indeed, it is a much better idea to use
an E1 rate to recover
a T1 and vice versa.

In any case, the eral constraint on common clock frequencies is
what common infrastructure is available. That is what determines the
rate.
There is an appendix in Y.1413 with detailed recommendations on this.

Y(J)S


-----Original Message-----
From: STUART VENTERS [mailto:stuart.venters@adtran.com]=20
Sent: Wednesday, January 24, 2007 19:21
To: pwe3@ietf.org
Subject: [PWE3] SAToP RTP frequency default

Greetings,

I'm looking at using SAToP for transporting T1's using differential
timing mode.
I'm wondering about the choice of 8Khz for the default RTP timestamp
frequency in RFC-4553.

Specifically, does the default actually work and does it match what's
preferred in the field?


Section 4.3.2.  Usage of RTP Header   5th paragraph

 The frequency of the clock used for generating timestamps MUST be an
   integer multiple of 8 kHz.  All implementations of SAToP MUST support
   the 8 kHz clock.  Other multiples of 8 kHz MAY be used.

A common wander spec for end to end T1 transport is 18us.  The 8khz RTP
default appears to cause the tdm to packet IWF to add quite a bit of
noise to the information concerning the actual phase of the incoming T1.
Depending on the noise frequency, the packet to tdm iwf may be able to
filter it out, but it seems like the wander spec would be easier to meet
with a lower quantization noise.  (In a similar situation in the Sonet
world, I think the receiving iwf is in fact sometimes unable to filter
it out without help from the transmitting iwf in the form of dithering.)

The 8Khz default results in a quantization noise of +- 62.5us.   =20
Making the differential timing default be the nominal tdm line rate
might be and alternative to the current default.  (IE 1.544Mhz for T1,
2.048 for E1, etc.)

For a sample size of 3 implementations, this appears to be in line with
actual practice.
    (My personal preference would be 8.192M, but I could go with 1.544
making it 4 implementations.)

Perhaps others on the list have an opinion in this regard.

I've looked in the pwe3 mail archives for this.  The closest I've found
was a discussion in Sept 04 about how the 192 bytes payload default
interacted with the 8khz timestamp frequency.  Perhaps someone could
point me someplace else where this has already been discussed.


Cheers,

Stuart Venters



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

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



From pwe3-bounces@ietf.org Thu Feb 01 02:16:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCWBH-0004hp-AF; Thu, 01 Feb 2007 02:16:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCWBF-0004ha-3M
	for pwe3@ietf.org; Thu, 01 Feb 2007 02:16:25 -0500
Received: from mx2-012.rad.co.il ([212.199.240.16] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCWBD-0004zK-3J
	for pwe3@ietf.org; Thu, 01 Feb 2007 02:16:25 -0500
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 01 Feb 2007 09:16:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Date: Thu, 1 Feb 2007 09:16:17 +0200
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D03208898@exrad3.ad.rad.co.il>
In-Reply-To: <1A209B72F475B54FB693B7EA2ED2980E088574@INEXC1U02.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Thread-Index: AccwJCHMtGrRnXvVS6e+1LcMZag+PAQJoYOgAWFszyA=
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Ramalingam, Swaminathan \(Swaminathan\)" <swamir@alcatel-lucent.com>,
	"Ahluwalia, Ajit \(Ajit\)" <ajitahlu@alcatel-lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 23336e92cd9b2f166f17126afcdd84ec
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0634910172=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0634910172==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C745D0.DD99EEB9"

This is a multi-part message in MIME format.

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

Sorry for the delay in processing.
=20
I have not suggested a special-purpose replacement for the TDMoIP OAM
message format,
as I believe that the performance measurement PDUs of Y.1731 fill the
gap.
=20
So, if PWE accepts the use of Y.1731 PDUs as VCCV payloads,
we will automatically get everything needed.
=20
(This means we will need another PWACH type)
=20
However, if we do not get agreement on this issue
I will rebake the old protocol based on ICMP,
add everything needed, and issue an ID.
I hope I won't have to do this.
=20
Y(J)S

________________________________

From: Ramalingam, Swaminathan (Swaminathan)
[mailto:swamir@alcatel-lucent.com]=20
Sent: Thursday, January 25, 2007 08:58
To: Yaakov Stein; Ahluwalia, Ajit (Ajit); pwe3@ietf.org
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs



Y(J)S,

=20

Is that mean VCCV need to signal one of the BFD CV type if an
implementation wants to send TDM OAM inband?. In that case, what is the
payload format (for TDM OAM)?=20

=20

=20

Thanks,

Swami

=20

________________________________

From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Thursday, January 04, 2007 10:42 PM
To: Ahluwalia, Ajit (Ajit); pwe3@ietf.org
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs

=20

Ajit

=20

The inband format relies on VCCV, which is the reason the CW is the
PWACH one

rather than the user traffic CW. VCCV based on BFD could be used for
most of the

functionality, but indeed it would be better to have a full-functioned
OAM here

(for example, a Y.1731 format one).

=20

The out-of-band OAM format is presently limited to the UDP/IP case.

There is no intent to extend it to the MPLS case, unless extending

the VCCV-based approach proves impossible. Incidentally, I admit

that there are advantages to the out-of-band approach for MPLS

where there may be many PWs in a single MPLS tunnel -=20

but that is not the direction the WG wanted us to go.

=20

Y(J)S

=20

=20

________________________________

From: Ahluwalia, Ajit (Ajit) [mailto:ajitahlu@alcatel-lucent.com]
Sent: Thu 04/01/2007 14:38
To: pwe3@ietf.org
Subject: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs

Hi,
1. Could anyone describe the format of inband TDM OAM format for MPLS
PSNs, section D.2 of draft-ietf-pwe3-tdmoip-06 just mentions first
nibble being 0001.
2. draft-ietf-pwe3-tdmoip-06.txt talks about out-of-band OAM format
where forward/reverse PW labels are 16 bit each, appropriate for UDP/IP
PSNs but how would this work for MPLS PSNs where more bits are required.

Thanks
Ajit

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


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>[PWE3] =
Inband/out-of-band TDM OAM format for MPLS PSNs</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR><!--[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]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: SimSun;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>Sorry=20
for the delay in processing.</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>I have=20
not suggested a special-purpose replacement for the TDMoIP OAM message=20
format,</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>as I=20
believe that the performance measurement PDUs of Y.1731 fill the=20
gap.</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>So, if=20
PWE accepts the use of Y.1731 PDUs as&nbsp;VCCV =
payloads,</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>we=20
will automatically get everything needed.</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>(This=20
means we will need another PWACH type)</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =

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

size=3D2>However, if we do not get agreement on this =
issue</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>I will=20
rebake the old protocol based on ICMP,</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>add=20
everything needed, and issue an ID.</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =
size=3D2>I hope=20
I won't have to do this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D717381207-01022007><FONT face=3DArial color=3D#0000ff =

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

size=3D2>Y(J)S</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Ramalingam, Swaminathan =
(Swaminathan)=20
[mailto:swamir@alcatel-lucent.com] <BR><B>Sent:</B> Thursday, January =
25, 2007=20
08:58<BR><B>To:</B> Yaakov Stein; Ahluwalia, Ajit (Ajit);=20
pwe3@ietf.org<BR><B>Subject:</B> RE: [PWE3] Inband/out-of-band TDM OAM =
format=20
for MPLS PSNs<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Y(J)S,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Is that mean =
VCCV need=20
to signal one of the BFD CV type if an implementation wants to send TDM =
OAM=20
inband?. In that case, what is the payload format (for TDM OAM)?=20
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Swami<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Yaakov=20
Stein [mailto:yaakov_s@rad.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, January 04, 2007 =
10:42=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
<st1:PersonName=20
w:st=3D"on">Ahluwalia, Ajit</st1:PersonName> (Ajit); =
pwe3@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [PWE3] =
Inband/out-of-band TDM=20
OAM format for MPLS PSNs</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV id=3DidOWAReplyText42058>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Ajit</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The inband format relies =
on VCCV,=20
which is the reason the CW is the PWACH =
one</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">rather than the user =
traffic=20
CW.&nbsp;VCCV based on BFD could be used for most of=20
the</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">functionality, but indeed =
it would=20
be better to have a full-functioned OAM =
here</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">(for example, a Y.1731 =
format=20
one).</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The out-of-band OAM format =
is=20
presently limited to the UDP/IP case.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">There is no intent to =
extend it to=20
the MPLS case, unless extending</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">the VCCV-based approach =
proves=20
impossible. Incidentally, I admit</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">that there are advantages =
to the=20
out-of-band approach for MPLS</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">where there may be many =
PWs in a=20
single MPLS tunnel - </SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">but that is not the =
direction the WG=20
wanted us to go.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Y(J)S</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
<st1:PersonName w:st=3D"on">Ahluwalia, Ajit</st1:PersonName> (Ajit)=20
[mailto:ajitahlu@alcatel-lucent.com]<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thu 04/01/2007 =
14:38<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> pwe3@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [PWE3] =
Inband/out-of-band TDM OAM=20
format for MPLS PSNs</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">Hi,<BR>1.=20
Could anyone describe the format of inband TDM OAM format for =
MPLS<BR>PSNs,=20
section D.2 of draft-ietf-pwe3-tdmoip-06 just mentions first<BR>nibble =
being=20
0001.<BR>2. draft-ietf-pwe3-tdmoip-06.txt talks about out-of-band OAM=20
format<BR>where forward/reverse PW labels are 16 bit each, appropriate =
for=20
UDP/IP<BR>PSNs but how would this work for MPLS PSNs where more bits are =

required.<BR><BR>Thanks<BR>Ajit<BR><BR>__________________________________=
_____________<BR>pwe3=20
mailing list<BR>pwe3@ietf.org<BR><A=20
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.or=
g/mailman/listinfo/pwe3</A></SPAN></FONT><o:p></o:p></P></DIV></DIV></BOD=
Y></HTML>

------_=_NextPart_001_01C745D0.DD99EEB9--


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

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

--===============0634910172==--




From pwe3-bounces@ietf.org Thu Feb 01 11:19:07 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCecv-0007sT-S1; Thu, 01 Feb 2007 11:17:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCecu-0007sK-E8
	for pwe3@ietf.org; Thu, 01 Feb 2007 11:17:32 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCecs-0000NO-OT
	for pwe3@ietf.org; Thu, 01 Feb 2007 11:17:32 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 01 Feb 2007 11:17:31 -0500
X-IronPort-AV: i="4.13,268,1167627600"; 
	d="scan'208,217"; a="112929040:sNHT103091236"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l11GHUfv012185; 
	Thu, 1 Feb 2007 11:17:30 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l11GHUOA001833; 
	Thu, 1 Feb 2007 11:17:30 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 11:17:30 -0500
Received: from [10.83.15.53] ([10.83.15.53]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Feb 2007 11:17:29 -0500
In-Reply-To: <457D36D9D89B5B47BC06DA869B1C815D03208898@exrad3.ad.rad.co.il>
References: <457D36D9D89B5B47BC06DA869B1C815D03208898@exrad3.ad.rad.co.il>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <3067688A-7C16-45EC-B12B-BBC327C6575C@cisco.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Date: Thu, 1 Feb 2007 11:17:27 -0500
To: "Yaakov Stein" <yaakov_s@rad.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 01 Feb 2007 16:17:29.0314 (UTC)
	FILETIME=[78355C20:01C7461C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=15872; t=1170346650;
	x=1171210650; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=tnadeau@cisco.com;
	z=From:=20=22Thomas=20D.=20Nadeau=22=20<tnadeau@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20Inband/out-of-band=20TDM=20OAM=20format=20fo
	r=20MPLS=20PSNs |Sender:=20
	|To:=20=22Yaakov=20Stein=22=20<yaakov_s@rad.com>;
	bh=pf8mpO1j8NFIf+u+n4Ns1vs3wCoTi9IRDnUi1Z3jRLE=;
	b=pLJ/uV1080SDLwHiBE+XnmDVGejeqFNwtrLjCctWYKObe1/cm/Lg/geg5QOAw14UWmKN5H03
	8j5i1UaLrNbz9OTED088dhQ9vGm6l46W36coF3c7DFJGqX4FCeArfDrr;
Authentication-Results: rtp-dkim-2; header.From=tnadeau@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Cc: "Ahluwalia, Ajit \(Ajit\)" <ajitahlu@alcatel-lucent.com>, pwe3@ietf.org,
	"Ramalingam, Swaminathan \(Swaminathan\)" <swamir@alcatel-lucent.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1762098507=="
Errors-To: pwe3-bounces@ietf.org


--===============1762098507==
Content-Type: multipart/alternative; boundary=Apple-Mail-2-913402762


--Apple-Mail-2-913402762
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On Feb 1, 2007, at 2:16 AM, Yaakov Stein wrote:

> Sorry for the delay in processing.
>
> I have not suggested a special-purpose replacement for the TDMoIP  
> OAM message format,
> as I believe that the performance measurement PDUs of Y.1731 fill  
> the gap.
>
> So, if PWE accepts the use of Y.1731 PDUs as VCCV payloads,
> we will automatically get everything needed.

	I am reluctant to do this, as I was when it was originally proposed.

	--Tom


>  (This means we will need another PWACH type)
>
> However, if we do not get agreement on this issue
> I will rebake the old protocol based on ICMP,
> add everything needed, and issue an ID.
> I hope I won't have to do this.
>
> Y(J)S
>
> From: Ramalingam, Swaminathan (Swaminathan) [mailto:swamir@alcatel- 
> lucent.com]
> Sent: Thursday, January 25, 2007 08:58
> To: Yaakov Stein; Ahluwalia, Ajit (Ajit); pwe3@ietf.org
> Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
>
> Y(J)S,
>
>
>
> Is that mean VCCV need to signal one of the BFD CV type if an  
> implementation wants to send TDM OAM inband?. In that case, what is  
> the payload format (for TDM OAM)?
>
>
>
>
>
> Thanks,
>
> Swami
>
>
>
> From: Yaakov Stein [mailto:yaakov_s@rad.com]
> Sent: Thursday, January 04, 2007 10:42 PM
> To: Ahluwalia, Ajit (Ajit); pwe3@ietf.org
> Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
>
>
>
> Ajit
>
>
>
> The inband format relies on VCCV, which is the reason the CW is the  
> PWACH one
>
> rather than the user traffic CW. VCCV based on BFD could be used  
> for most of the
>
> functionality, but indeed it would be better to have a full- 
> functioned OAM here
>
> (for example, a Y.1731 format one).
>
>
>
> The out-of-band OAM format is presently limited to the UDP/IP case.
>
> There is no intent to extend it to the MPLS case, unless extending
>
> the VCCV-based approach proves impossible. Incidentally, I admit
>
> that there are advantages to the out-of-band approach for MPLS
>
> where there may be many PWs in a single MPLS tunnel -
>
> but that is not the direction the WG wanted us to go.
>
>
>
> Y(J)S
>
>
>
>
>
> From: Ahluwalia, Ajit (Ajit) [mailto:ajitahlu@alcatel-lucent.com]
> Sent: Thu 04/01/2007 14:38
> To: pwe3@ietf.org
> Subject: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
>
> Hi,
> 1. Could anyone describe the format of inband TDM OAM format for MPLS
> PSNs, section D.2 of draft-ietf-pwe3-tdmoip-06 just mentions first
> nibble being 0001.
> 2. draft-ietf-pwe3-tdmoip-06.txt talks about out-of-band OAM format
> where forward/reverse PW labels are 16 bit each, appropriate for  
> UDP/IP
> PSNs but how would this work for MPLS PSNs where more bits are  
> required.
>
> Thanks
> Ajit
>
> _______________________________________________
> 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


--Apple-Mail-2-913402762
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><BR><DIV><DIV>On Feb 1, 2007, at =
2:16 AM, Yaakov Stein wrote:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE =
type=3D"cite"><O:SMARTTAGTYPE name=3D"PersonName" =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></O:SMARTTAGTY=
PE> <DIV><SPAN class=3D"717381207-01022007"><FONT face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Sorry for the delay in =
processing.</FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></FONT></SPAN>=A0</DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">I have not suggested a special-purpose replacement for the =
TDMoIP OAM message format,</FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">as I believe that the performance measurement PDUs of Y.1731 =
fill the gap.</FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></FONT></SPAN>=A0</DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">So, if PWE accepts the use of Y.1731 PDUs as=A0VCCV =
payloads,</FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">we will automatically get everything =
needed.</FONT></SPAN></DIV></BLOCKQUOTE><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><SPAN class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</SPAN>I am reluctant to do this, as I =
was when it was originally proposed.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><SPAN =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</SPAN>--Tom</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV><BR><BLOCKQUOTE =
type=3D"cite"> <DIV><SPAN class=3D"717381207-01022007"><FONT =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></FONT></SPAN>=A0<SPAN =
class=3D"717381207-01022007"><FONT class=3D"Apple-style-span" =
color=3D"#0000FF" face=3D"Arial" size=3D"3"><SPAN =
class=3D"Apple-style-span" style=3D"font-size: 13px;">(This means we =
will need another PWACH type)</SPAN></FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></FONT></SPAN>=A0</DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">However, if we do not get agreement on this =
issue</FONT></SPAN></DIV> <DIV><SPAN class=3D"717381207-01022007"><FONT =
face=3D"Arial" color=3D"#0000ff" size=3D"2">I will rebake the old =
protocol based on ICMP,</FONT></SPAN></DIV> <DIV><SPAN =
class=3D"717381207-01022007"><FONT face=3D"Arial" color=3D"#0000ff" =
size=3D"2">add everything needed, and issue an ID.</FONT></SPAN></DIV> =
<DIV><SPAN class=3D"717381207-01022007"><FONT face=3D"Arial" =
color=3D"#0000ff" size=3D"2">I hope I won't have to do =
this.</FONT></SPAN></DIV> <DIV><SPAN class=3D"717381207-01022007"><FONT =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></FONT></SPAN>=A0</DIV> =
<DIV><SPAN class=3D"717381207-01022007"><FONT face=3D"Arial" =
color=3D"#0000ff" size=3D"2">Y(J)S</FONT></SPAN></DIV><BR> <DIV =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
<HR tabindex=3D"-1"> <FONT face=3D"Tahoma" size=3D"2"><B>From:</B> =
Ramalingam, Swaminathan (Swaminathan) [<A =
href=3D"mailto:swamir@alcatel-lucent.com">mailto:swamir@alcatel-lucent.com=
</A>] <BR><B>Sent:</B> Thursday, January 25, 2007 08:58<BR><B>To:</B> =
Yaakov Stein; Ahluwalia, Ajit (Ajit); <A =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><B>Subject:</B> RE: =
[PWE3] Inband/out-of-band TDM OAM format for MPLS =
PSNs<BR></FONT><BR></DIV> <DIV></DIV> <DIV class=3D"Section1"><P =
class=3D"MsoNormal"><FONT face=3D"Arial" color=3D"navy" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Y(J)S,<O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT =
face=3D"Arial" color=3D"navy" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; =
COLOR: navy; FONT-FAMILY: Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT face=3D"Arial" color=3D"navy" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Is that mean =
VCCV need to signal one of the BFD CV type if an implementation wants to =
send TDM OAM inband?. In that case, what is the payload format (for TDM =
OAM)? <O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT =
face=3D"Arial" color=3D"navy" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; =
COLOR: navy; FONT-FAMILY: Arial"><O:P>=A0</O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT face=3D"Arial" color=3D"navy" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><O:P>=A0</O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT =
face=3D"Arial" color=3D"navy" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; =
COLOR: navy; FONT-FAMILY: Arial">Thanks,<O:P></O:P></SPAN></FONT></P><P =
class=3D"MsoNormal"><FONT face=3D"Arial" color=3D"navy" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Swami<O:P></O:P></SPAN></FONT></P><P class=3D"MsoNormal"><FONT =
face=3D"Arial" color=3D"navy" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; =
COLOR: navy; FONT-FAMILY: Arial"><O:P>=A0</O:P></SPAN></FONT></P> <DIV> =
<DIV class=3D"MsoNormal" style=3D"TEXT-ALIGN: center" =
align=3D"center"><FONT face=3D"Times New Roman" size=3D"3"><SPAN =
style=3D"FONT-SIZE: 12pt"> <HR tabindex=3D"-1" align=3D"center" =
width=3D"100%" size=3D"2"> </SPAN></FONT></DIV><P =
class=3D"MsoNormal"><B><FONT face=3D"Tahoma" size=3D"2"><SPAN =
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT face=3D"Tahoma" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Yaakov Stein [<A =
href=3D"mailto:yaakov_s@rad.com">mailto:yaakov_s@rad.com</A>] =
<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, =
January 04, 2007 10:42 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> <ST1:PERSONNAME w:st=3D"on">Ahluwalia, =
Ajit</ST1:PERSONNAME> (Ajit); <A =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><B><SPAN =
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [PWE3] =
Inband/out-of-band TDM OAM format for MPLS =
PSNs</SPAN></FONT><O:P></O:P></P></DIV><P class=3D"MsoNormal"><FONT =
face=3D"Times New Roman" size=3D"3"><SPAN style=3D"FONT-SIZE: =
12pt"><O:P>=A0</O:P></SPAN></FONT></P> <DIV id=3D"idOWAReplyText42058"> =
<DIV><P class=3D"MsoNormal"><FONT face=3D"Arial" color=3D"black" =
size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Ajit</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Times New Roman" size=3D"3"><SPAN =
style=3D"FONT-SIZE: 12pt">=A0<O:P></O:P></SPAN></FONT></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Arial" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The inband format relies =
on VCCV, which is the reason the CW is the PWACH =
one</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT =
face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">rather than the user traffic CW.=A0VCCV based on BFD could be =
used for most of the</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Arial" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">functionality, but indeed =
it would be better to have a full-functioned OAM =
here</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT =
face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">(for example, a Y.1731 format =
one).</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT=
 face=3D"Times New Roman" size=3D"3"><SPAN style=3D"FONT-SIZE: =
12pt">=A0<O:P></O:P></SPAN></FONT></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Arial" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The out-of-band OAM format =
is presently limited to the UDP/IP =
case.</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT=
 face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">There is no intent to extend it to the MPLS case, unless =
extending</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Arial" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">the VCCV-based approach =
proves impossible. Incidentally, I =
admit</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT=
 face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">that there are advantages to the out-of-band approach for =
MPLS</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT =
face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">where there may be many PWs in a single MPLS tunnel - =
</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT =
face=3D"Arial" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">but that is not the direction the WG wanted us to =
go.</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P class=3D"MsoNormal"><FONT =
face=3D"Times New Roman" size=3D"3"><SPAN style=3D"FONT-SIZE: =
12pt">=A0<O:P></O:P></SPAN></FONT></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Arial" size=3D"2"><SPAN =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Y(J)S</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P =
class=3D"MsoNormal"><FONT face=3D"Times New Roman" size=3D"3"><SPAN =
style=3D"FONT-SIZE: 12pt">=A0<O:P></O:P></SPAN></FONT></P></DIV></DIV> =
<DIV><P class=3D"MsoNormal"><FONT face=3D"Times New Roman" =
size=3D"3"><SPAN style=3D"FONT-SIZE: =
12pt"><O:P>=A0</O:P></SPAN></FONT></P> <DIV class=3D"MsoNormal" =
style=3D"TEXT-ALIGN: center" align=3D"center"><FONT face=3D"Times New =
Roman" size=3D"3"><SPAN style=3D"FONT-SIZE: 12pt"> <HR tabindex=3D"-1" =
align=3D"center" width=3D"100%" size=3D"2"> </SPAN></FONT></DIV><P =
class=3D"MsoNormal" style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3D"Tahoma"=
 size=3D"2"><SPAN style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=3D"Tahoma" =
size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> =
<ST1:PERSONNAME w:st=3D"on">Ahluwalia, Ajit</ST1:PERSONNAME> (Ajit) [<A =
href=3D"mailto:ajitahlu@alcatel-lucent.com">mailto:ajitahlu@alcatel-lucent=
.com</A>]<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thu =
04/01/2007 14:38<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
<A href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><B><SPAN =
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [PWE3] =
Inband/out-of-band TDM OAM format for MPLS =
PSNs</SPAN></FONT><O:P></O:P></P></DIV> <DIV><P><FONT face=3D"Times New =
Roman" size=3D"2"><SPAN style=3D"FONT-SIZE: 10pt">Hi,<BR>1. Could anyone =
describe the format of inband TDM OAM format for MPLS<BR>PSNs, section =
D.2 of draft-ietf-pwe3-tdmoip-06 just mentions first<BR>nibble being =
0001.<BR>2. draft-ietf-pwe3-tdmoip-06.txt talks about out-of-band OAM =
format<BR>where forward/reverse PW labels are 16 bit each, appropriate =
for UDP/IP<BR>PSNs but how would this work for MPLS PSNs where more bits =
are =
required.<BR><BR>Thanks<BR>Ajit<BR><BR>___________________________________=
____________<BR>pwe3 mailing list<BR><A =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.org=
/mailman/listinfo/pwe3</A></SPAN></FONT><O:P></O:P></P></DIV></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">pwe3 mailing list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/pwe3">https://www1.ietf.org=
/mailman/listinfo/pwe3</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-2-913402762--


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

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

--===============1762098507==--




From pwe3-bounces@ietf.org Thu Feb 01 12:54:42 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCg7k-0002Bm-K1; Thu, 01 Feb 2007 12:53:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCg7j-0002Bh-T4
	for pwe3@ietf.org; Thu, 01 Feb 2007 12:53:27 -0500
Received: from mx2-n.rad.co.il ([62.0.23.221] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCg7g-0000DE-GA
	for pwe3@ietf.org; Thu, 01 Feb 2007 12:53:27 -0500
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 01 Feb 2007 19:53:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Date: Thu, 1 Feb 2007 19:53:13 +0200
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D03208BDA@exrad3.ad.rad.co.il>
In-Reply-To: <3067688A-7C16-45EC-B12B-BBC327C6575C@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Thread-Index: AcdGHHvOxyvkWzgoSVue/SkrX5cq5AADTF9w
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: "Ahluwalia, Ajit \(Ajit\)" <ajitahlu@alcatel-lucent.com>, pwe3@ietf.org,
	"Ramalingam, Swaminathan \(Swaminathan\)" <swamir@alcatel-lucent.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0521153652=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0521153652==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C74629.D9EF1878"

This is a multi-part message in MIME format.

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

So, if PWE accepts the use of Y.1731 PDUs as VCCV payloads,   we will
automatically get everything needed.

I am reluctant to do this, as I was when it was originally proposed.

--Tom

[YJS] So what do you suggest ?=20

------_=_NextPart_001_01C74629.D9EF1878
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.2900.3020" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; khtml-nbsp-mode: space; =
khtml-line-break: after-white-space">
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D717381207-01022007>So, if PWE accepts the use of Y.1731 PDUs =
as&nbsp;VCCV=20
payloads,<SPAN class=3D879015217-01022007>&nbsp; =
&nbsp;</SPAN></SPAN><SPAN=20
class=3D717381207-01022007>we will automatically get everything=20
needed.</SPAN></FONT></FONT></FONT></DIV>
<DIV>
<DIV><BR class=3Dkhtml-block-placeholder></DIV><SPAN =
class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN>I am reluctant to do this, as I was =
when it was=20
originally proposed.</DIV>
<DIV><BR class=3Dkhtml-block-placeholder></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: =
pre"></SPAN>--Tom</DIV>
<DIV><BR class=3Dkhtml-block-placeholder><SPAN =
class=3D879015217-01022007><FONT=20
face=3DArial color=3D#0000ff size=3D2>[YJS] So what do you suggest=20
?&nbsp;</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C74629.D9EF1878--


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

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

--===============0521153652==--




From pwe3-bounces@ietf.org Thu Feb 01 20:44:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCnSn-0004tB-VD; Thu, 01 Feb 2007 20:43:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCnSn-0004r0-9Y
	for pwe3@ietf.org; Thu, 01 Feb 2007 20:43:41 -0500
Received: from host-api.adtran.com ([208.251.151.99] helo=EXV1.corp.adtran.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCnSl-0001qk-9b
	for pwe3@ietf.org; Thu, 01 Feb 2007 20:43:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] SAToP RTP frequency default
Date: Thu, 1 Feb 2007 19:43:33 -0600
Message-ID: <8F242B230AD6474C8E7815DE0B4982D703B8006F@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] SAToP RTP frequency default
Thread-Index: Acc/3A8i/u+tBcUtT8iqVoiPX7CozgF8cwmAACSSo4A=
From: "STUART VENTERS" <stuart.venters@adtran.com>
To: "Yaakov Stein" <yaakov_s@rad.com>,
	<pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Yaakov,

Thanks for the pointer to Y.1413, it does bring up a strange idea.
Namely that the RTP frequency should be determined by what's available =
at the pseudowire endpoint.

This seems weird because:
1) Both ends of the pseudowire might have different clocks available.
2) It's not that hard to make a pseudowire engine that doesn't care.
3) It leads to the questionable, lowest common denominator 8khz default.

So when you say 8 kHz is ridiculously low, what do you mean?
  (Perhaps that it makes it difficult to provide reasonable payload =
wander?)

Stuart

(answers to you questions interleaved below)



-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Thursday, February 01, 2007 1:06 AM
To: STUART VENTERS; pwe3@ietf.org
Subject: RE: [PWE3] SAToP RTP frequency default


Stuart,=20

I quite agree that 8 kHz is ridiculously low,=20
but disagree with your argument about the quantization noise this adds.
<<< Ok, but I'm sticking with my story.  >>>
<<< It seems like any given RTP packet is telling you >>>
<<<    the phase of the payload to within +-62.5us.  >>>
<<< The timing recovery may make this a non-issue,  >>>
<<<   but the RTP packet gives it +-62.5ns of noise to start with. >>>

The 1/8 khz quantization noise adds local jitter but should have no
effect on the wander
in any implementation with even rudimentary clock recovery.
<<< I was thinking that if the noise were high frequency, >>>
<<<   the clock recovery would attenuate the jitter.   >>>
<<< If it were low frequency, you get wander. >>>

However, I am unsure what you mean about using the nominal TDM line
rate.
Of course using the actual TDM source clock is great if it is available=20
at the other end, but then you don't need a timestamp - just lock the
remote clock to it.

So I assume that you suggest using another clock which happens to be the
same rate.
<<< Yes, you assume correctly >>>

This is also NOT a good idea, as the aliasing of the close rate
can be catastrophic to clock recovery algorithms - indeed, it is a much
better idea to use an E1 rate to recover a T1 and vice versa.
<<< Agreed, the E1 rate would be better for the reason you state. >>>
<<<  (Life is better if the payload rate divided by the packet size >>>
<<<   is not related to the RTP frequency.) >>>
<<< However, even with the T1 rate at a near zero frequency offset, >>>
<<< you still know the payload phase to within 647 ns. >>>
<<< Assuming a jitter attenuator, 647ns of residual wander seems good =
enough. >>>
<<<  (And a lot better than with the 8Khz default.) >>>

In any case, the eral constraint on common clock frequencies is
what common infrastructure is available. That is what determines the
rate.
There is an appendix in Y.1413 with detailed recommendations on this.

Y(J)S


-----Original Message-----
From: STUART VENTERS [mailto:stuart.venters@adtran.com]=20
Sent: Wednesday, January 24, 2007 19:21
To: pwe3@ietf.org
Subject: [PWE3] SAToP RTP frequency default

Greetings,

I'm looking at using SAToP for transporting T1's using differential
timing mode.
I'm wondering about the choice of 8Khz for the default RTP timestamp
frequency in RFC-4553.

Specifically, does the default actually work and does it match what's
preferred in the field?


Section 4.3.2.  Usage of RTP Header   5th paragraph

 The frequency of the clock used for generating timestamps MUST be an
   integer multiple of 8 kHz.  All implementations of SAToP MUST support
   the 8 kHz clock.  Other multiples of 8 kHz MAY be used.

A common wander spec for end to end T1 transport is 18us.  The 8khz RTP
default appears to cause the tdm to packet IWF to add quite a bit of
noise to the information concerning the actual phase of the incoming T1.
Depending on the noise frequency, the packet to tdm iwf may be able to
filter it out, but it seems like the wander spec would be easier to meet
with a lower quantization noise.  (In a similar situation in the Sonet
world, I think the receiving iwf is in fact sometimes unable to filter
it out without help from the transmitting iwf in the form of dithering.)

The 8Khz default results in a quantization noise of +- 62.5us.   =20
Making the differential timing default be the nominal tdm line rate
might be and alternative to the current default.  (IE 1.544Mhz for T1,
2.048 for E1, etc.)

For a sample size of 3 implementations, this appears to be in line with
actual practice.
    (My personal preference would be 8.192M, but I could go with 1.544
making it 4 implementations.)

Perhaps others on the list have an opinion in this regard.

I've looked in the pwe3 mail archives for this.  The closest I've found
was a discussion in Sept 04 about how the 192 bytes payload default
interacted with the 8khz timestamp frequency.  Perhaps someone could
point me someplace else where this has already been discussed.


Cheers,

Stuart Venters



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

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



From pwe3-bounces@ietf.org Fri Feb 02 09:30:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HCzPG-00026A-La; Fri, 02 Feb 2007 09:28:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HCzPF-000263-01
	for pwe3@ietf.org; Fri, 02 Feb 2007 09:28:49 -0500
Received: from cat.tcb.net ([64.78.150.134] helo=dog.tcb.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCzPD-0004IV-Ld
	for pwe3@ietf.org; Fri, 02 Feb 2007 09:28:48 -0500
Received: from rover.local (VDSL-151-118-3-142.DNVR.QWEST.NET [151.118.3.142])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id 83CFE64504
	for <pwe3@ietf.org>; Fri,  2 Feb 2007 07:28:45 -0700 (MST)
Received: from [127.0.0.1] by rover.local (PGP Universal service);
	Fri, 02 Feb 2007 07:28:51 -0700
X-PGP-Universal: processed; by rover.local on Fri, 02 Feb 2007 07:28:51 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <E1HCqWn-0000FI-Lq@stiedprstage1.ietf.org>
Message-Id: <B10577AB-D898-4FA4-B708-23CBAA979AD3@tcb.net>
From: Danny McPherson <danny@tcb.net>
Date: Fri, 2 Feb 2007 07:28:46 -0700
To: "pwe3 ((((((((E-mail)))))))) WG" <pwe3@ietf.org>
X-Mailer: Apple Mail (2.752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Subject: [PWE3] Fwd: Internet-Drafts Submission Cutoff Dates for the 68th
	IETF Meeting in Prague, Czech Republic 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


FYI...

-danny

Begin forwarded message:

> From: ietf-secretariat@ietf.org
> Date: February 1, 2007 10:00:01 PM MST
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 68th IETF   
> Meeting in Prague, Czech Republic
>
>
> There are two (2) Internet-Draft cutoff dates for the 68th
> IETF Meeting in Prague, Czech Republic:
>
> February 26th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> February 26th at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> February 19th at 9:00 AM ET.
>
> March 5th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, March 5th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, March 19th at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 68th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_68.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce


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



From pwe3-bounces@ietf.org Fri Feb 02 15:51:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD5MP-0002YM-Er; Fri, 02 Feb 2007 15:50:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HD5MC-0002WI-V5; Fri, 02 Feb 2007 15:50:04 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HD5MC-00029u-Lw; Fri, 02 Feb 2007 15:50:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id F0AC726ECC;
	Fri,  2 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HD5MA-0002OB-H4; Fri, 02 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HD5MA-0002OB-H4@stiedprstage1.ietf.org>
Date: Fri, 02 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-congestion-frmwk-00.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Pseudowire Congestion Control Framework
	Author(s)	: S. Bryant, et al.
	Filename	: draft-ietf-pwe3-congestion-frmwk-00.txt
	Pages		: 22
	Date		: 2007-2-2
	
   Given that pseudowires may be used to carry non-TCP data flows, it is
   necessary to provide pseudowire-specific congestion control
   procedures.  These procedures should ensure that pseudowire traffic
   is "TCP-compatible", as defined in RFC 2914.  This document attempts
   to lay out the issues which must be considered when defining such
   procedures.


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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-congestion-frmwk-00.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-congestion-frmwk-00.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: <2007-2-2145221.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-congestion-frmwk-00.txt

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

Content-Type: text/plain
Content-ID: <2007-2-2145221.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Sat Feb 03 11:29:21 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDNkA-0008DQ-V8; Sat, 03 Feb 2007 11:28:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDNk9-0008DK-LD
	for pwe3@ietf.org; Sat, 03 Feb 2007 11:28:01 -0500
Received: from [212.25.127.226] (helo=gfi-gw.seabridge.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDNk6-0005KI-HP
	for pwe3@ietf.org; Sat, 03 Feb 2007 11:28:01 -0500
Received: from dove.seabridge.co.il ([172.30.10.115]) by
	gfi-gw.seabridge.co.il with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 3 Feb 2007 18:27:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 3 Feb 2007 18:24:46 +0200
Message-ID: <D3C85156A12AAB4DB23F598007E9826D0174596E@dove.seabridge.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-allan-pw-o-pbt-02.txt 
Thread-Index: AcdHr9GajnDl8IJ0Ttm7vIrkpr2iUQ==
From: "Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
To: <dallan@nortel.com>
X-OriginalArrivalTime: 03 Feb 2007 16:27:51.0923 (UTC)
	FILETIME=[40237430:01C747B0]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9724479da43a8325ad975c1a9b841870
Cc: pwe3@ietf.org, Nurit Sprecher <nurit.sprecher@SeabridgeNetworks.com>
Subject: [PWE3] draft-allan-pw-o-pbt-02.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0275473028=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0275473028==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C747B0.3ED8F218"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C747B0.3ED8F218
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Dave,

Thanks for the updated draft. I believe it is useful.

I wonder what is the difference between PBT and (static) Ethernet as
PSNs as appear in your draft? As I see it, PBT is more a control concept
and not a dataplane or PSN.

Reading the draft it even seems to me that the draft defines PW over
Ethernet PSN (which is set up using PBT mode) and for that sake there is
even no difference between 802.1ad dataplane and 802.1ah. Is that true?=20

Can we modify this draft to be a generic one (as it actually is) and
make it PW over Ethernet PSN?

Best regards,

Nurit.

=20

=20

=20

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Friday, February 02, 2007 22:50
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt=20

=20

A New Internet-Draft is available from the on-line Internet-Drafts=20

directories.

=20

=20

      Title       : Pseudo Wires over Provider Backbone Transport

      Author(s)   : D. Allan

      Filename    : draft-allan-pw-o-pbt-02.txt

      Pages       : 7

      Date        : 2007-2-2

     =20

This memo describes architecture and procedures for the operation of=20

   pseudo wires over provider backbone transport (PBT).

=20

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-allan-pw-o-pbt-02.txt

=20

To remove yourself from the I-D Announcement list, send a message to=20

i-d-announce-request@ietf.org with the word unsubscribe in the body of=20

the message.=20

You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20

to change your subscription settings.

=20

Internet-Drafts are also available by anonymous FTP. Login with the=20

username "anonymous" and a password of your e-mail address. After=20

logging in, type "cd internet-drafts" and then=20

"get draft-allan-pw-o-pbt-02.txt".

=20

A list of Internet-Drafts directories can be found in

http://www.ietf.org/shadow.html=20

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=20

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

=20

Send a message to:

      mailserv@ietf.org.

In the body type:

      "FILE /internet-drafts/draft-allan-pw-o-pbt-02.txt".

     =20

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.

=20

Below is the data which will enable a MIME compliant mail reader

implementation to automatically retrieve the ASCII version of the

Internet-Draft.


------_=_NextPart_001_01C747B0.3ED8F218
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)">
<style>
<!--
 /* 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:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 69.6pt 1.0in 69.6pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1 dir=3DRTL>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Hi Dave,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Thanks for the updated draft. I believe it is =
useful.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>I wonder what is the difference between PBT =
and
(static) Ethernet as PSNs <b><span style=3D'font-weight:bold'>as appear =
in your
draft</span></b>? As I see it, <b><span style=3D'font-weight:bold'>PBT =
is more a
control concept</span></b> and not a dataplane or =
PSN.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Reading the draft it even seems to me that =
the draft
defines PW over Ethernet PSN (which is set up using PBT mode) and for =
that sake
there is even no difference between 802.1ad dataplane and 802.1ah. Is =
that
true? <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Can we modify this draft to be a generic one =
(as it
actually is) and make it PW over Ethernet =
PSN?<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Best regards,<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Nurit.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>-----Original Message-----<br>
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] <br>
Sent: Friday, February 02, 2007 22:50<br>
To: i-d-announce@ietf.org<br>
Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt </span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>A New Internet-Draft is available from the =
on-line
Internet-Drafts <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>directories.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
Pseudo Wires over Provider Backbone =
Transport<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Author(s)&nbsp;&nbsp; :
D. Allan<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Filename&nbsp;&nbsp;&nbsp; :
draft-allan-pw-o-pbt-02.txt<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
7<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
2007-2-2<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>This memo describes architecture and =
procedures for
the operation of <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp; pseudo wires over provider =
backbone
transport (PBT).<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>A URL for this Internet-Draft =
is:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>http://www.ietf.org/internet-drafts/draft-alla=
n-pw-o-pbt-02.txt<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>To remove yourself from the I-D Announcement =
list,
send a message to <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>i-d-announce-request@ietf.org with the word
unsubscribe in the body of <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>the message. <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>You can also visit
https://www1.ietf.org/mailman/listinfo/I-D-announce =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>to change your subscription =
settings.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Internet-Drafts are also available by =
anonymous FTP.
Login with the <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>username &quot;anonymous&quot; and a password =
of your
e-mail address. After <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>logging in, type &quot;cd =
internet-drafts&quot; and
then <o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&quot;get =
draft-allan-pw-o-pbt-02.txt&quot;.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>A list of Internet-Drafts directories can be =
found in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>http://www.ietf.org/shadow.html =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>or =
ftp://ftp.ietf.org/ietf/1shadow-sites.txt<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Internet-Drafts can also be obtained by =
e-mail.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Send a message =
to:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
mailserv@ietf.org.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>In the body =
type:<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;FILE
/internet-drafts/draft-allan-pw-o-pbt-02.txt&quot;.<o:p></o:p></span></fo=
nt></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>NOTE: The mail server at ietf.org can return =
the
document in<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MIME-encoded =
form by
using the &quot;mpack&quot; utility.&nbsp; To use =
this<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature, =
insert the
command &quot;ENCODING mime&quot; before the =
&quot;FILE&quot;<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command.&nbsp; =
To
decode the response(s), you will need &quot;munpack&quot; =
or<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
MIME-compliant mail
reader.&nbsp; Different MIME-compliant mail =
readers<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exhibit =
different
behavior, especially when dealing with<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&quot;multipart&quot;
MIME messages (i.e. documents which have been =
split<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; up into =
multiple
messages), so check your local documentation =
on<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to =
manipulate these
messages.<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Below is the data which will enable a MIME =
compliant
mail reader<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>implementation to automatically retrieve the =
ASCII
version of the<o:p></o:p></span></font></p>

<p class=3DMsoPlainText dir=3DLTR><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'>Internet-Draft.<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C747B0.3ED8F218--


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

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

--===============0275473028==--




From pwe3-bounces@ietf.org Sat Feb 03 22:50:04 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HDYMq-00051V-Q9; Sat, 03 Feb 2007 22:48:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDYMo-000508-U7
	for pwe3@ietf.org; Sat, 03 Feb 2007 22:48:38 -0500
Received: from mx2-q.rad.co.il ([80.74.100.144] helo=antivir2.rad.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDYMY-0007zS-5B
	for pwe3@ietf.org; Sat, 03 Feb 2007 22:48:38 -0500
Received: from exrad3.rad.co.il (HELO exrad3.ad.rad.co.il) ([192.114.24.112])
	by antivir2.rad.co.il with ESMTP; 04 Feb 2007 05:48:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] SAToP RTP frequency default
Date: Sun, 4 Feb 2007 05:48:01 +0200
Message-ID: <457D36D9D89B5B47BC06DA869B1C815D03208CE6@exrad3.ad.rad.co.il>
In-Reply-To: <8F242B230AD6474C8E7815DE0B4982D703B8006F@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] SAToP RTP frequency default
Thread-Index: Acc/3A8i/u+tBcUtT8iqVoiPX7CozgF8cwmAACSSo4AAa3RfoA==
From: "Yaakov Stein" <yaakov_s@rad.com>
To: "STUART VENTERS" <stuart.venters@adtran.com>,
	<pwe3@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

=20

Thanks for the pointer to Y.1413, it does bring up a strange idea.
Namely that the RTP frequency should be determined by what's available
at the pseudowire endpoint.

This seems weird because:
1) Both ends of the pseudowire might have different clocks available.

[YJS] In which case "common clock" is not an option.
That's why I dislike the term "differential method" and prefer "common
clock".
The former makes it sound like the using of a timestamp works magic - it
doesn't.
It is only the existence of a common clock that enables the recovery of
clock even when the network is severely degraded.

2) It's not that hard to make a pseudowire engine that doesn't care.

[YJS] about what ?

3) It leads to the questionable, lowest common denominator 8khz default.

[YJS] 8 kHz is a clock that is universally available at TDM sites.

So when you say 8 kHz is ridiculously low, what do you mean?
  (Perhaps that it makes it difficult to provide reasonable payload
wander?)

[YJS] No - no problem with the wander - just that it strains the
implementation.
Using a clock closer (but not too close!) to the rate being recovered=20
eases the implementation.


Stuart

(answers to you questions interleaved below)



-----Original Message-----
From: Yaakov Stein [mailto:yaakov_s@rad.com]
Sent: Thursday, February 01, 2007 1:06 AM
To: STUART VENTERS; pwe3@ietf.org
Subject: RE: [PWE3] SAToP RTP frequency default


Stuart,=20

I quite agree that 8 kHz is ridiculously low, but disagree with your
argument about the quantization noise this adds.
<<< Ok, but I'm sticking with my story.  >>> <<< It seems like any given
RTP packet is telling you >>>
<<<    the phase of the payload to within +-62.5us.  >>>
<<< The timing recovery may make this a non-issue,  >>>
<<<   but the RTP packet gives it +-62.5ns of noise to start with. >>>

[YJS] As I said, it adds jitter. Jitter is easy to filter out.


The 1/8 khz quantization noise adds local jitter but should have no
effect on the wander in any implementation with even rudimentary clock
recovery.
<<< I was thinking that if the noise were high frequency, >>>
<<<   the clock recovery would attenuate the jitter.   >>>
<<< If it were low frequency, you get wander. >>>

[YJS] The noise you are talking about is quantization noise.
Its rate is once per packet. According to the conventional
classification,
this would add wander if you have less than 10 packets per second
(which is unusually low for TDM PWs). And there is no good reason for
the 10 Hz boundary here - the wander gets harder to eliminate when =20
its timescale is that of the network dynamics - on the order of seconds
!


However, I am unsure what you mean about using the nominal TDM line
rate.
Of course using the actual TDM source clock is great if it is available
at the other end, but then you don't need a timestamp - just lock the
remote clock to it.

So I assume that you suggest using another clock which happens to be the
same rate.
<<< Yes, you assume correctly >>>

This is also NOT a good idea, as the aliasing of the close rate can be
catastrophic to clock recovery algorithms - indeed, it is a much better
idea to use an E1 rate to recover a T1 and vice versa.
<<< Agreed, the E1 rate would be better for the reason you state. >>>
<<<  (Life is better if the payload rate divided by the packet size >>>
<<<   is not related to the RTP frequency.) >>>
<<< However, even with the T1 rate at a near zero frequency offset, >>>
<<< you still know the payload phase to within 647 ns. >>> <<< Assuming
a jitter attenuator, 647ns of residual wander seems good enough. >>> <<<
(And a lot better than with the 8Khz default.) >>>

In any case, the eral constraint on common clock frequencies is what
common infrastructure is available. That is what determines the rate.
There is an appendix in Y.1413 with detailed recommendations on this.

Y(J)S


-----Original Message-----
From: STUART VENTERS [mailto:stuart.venters@adtran.com]
Sent: Wednesday, January 24, 2007 19:21
To: pwe3@ietf.org
Subject: [PWE3] SAToP RTP frequency default

Greetings,

I'm looking at using SAToP for transporting T1's using differential
timing mode.
I'm wondering about the choice of 8Khz for the default RTP timestamp
frequency in RFC-4553.

Specifically, does the default actually work and does it match what's
preferred in the field?


Section 4.3.2.  Usage of RTP Header   5th paragraph

 The frequency of the clock used for generating timestamps MUST be an
   integer multiple of 8 kHz.  All implementations of SAToP MUST support
   the 8 kHz clock.  Other multiples of 8 kHz MAY be used.

A common wander spec for end to end T1 transport is 18us.  The 8khz RTP
default appears to cause the tdm to packet IWF to add quite a bit of
noise to the information concerning the actual phase of the incoming T1.
Depending on the noise frequency, the packet to tdm iwf may be able to
filter it out, but it seems like the wander spec would be easier to meet
with a lower quantization noise.  (In a similar situation in the Sonet
world, I think the receiving iwf is in fact sometimes unable to filter
it out without help from the transmitting iwf in the form of dithering.)

The 8Khz default results in a quantization noise of +- 62.5us.   =20
Making the differential timing default be the nominal tdm line rate
might be and alternative to the current default.  (IE 1.544Mhz for T1,
2.048 for E1, etc.)

For a sample size of 3 implementations, this appears to be in line with
actual practice.
    (My personal preference would be 8.192M, but I could go with 1.544
making it 4 implementations.)

Perhaps others on the list have an opinion in this regard.

I've looked in the pwe3 mail archives for this.  The closest I've found
was a discussion in Sept 04 about how the 192 bytes payload default
interacted with the 8khz timestamp frequency.  Perhaps someone could
point me someplace else where this has already been discussed.


Cheers,

Stuart Venters



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

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



From pwe3-bounces@ietf.org Mon Feb 05 06:13:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE1lQ-00007s-QH; Mon, 05 Feb 2007 06:12:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HDxBB-0004u7-UP
	for pwe3@ietf.org; Mon, 05 Feb 2007 01:18:17 -0500
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDxBA-0001DQ-9E
	for pwe3@ietf.org; Mon, 05 Feb 2007 01:18:17 -0500
Received: by ug-out-1314.google.com with SMTP id 72so1121448ugd
	for <pwe3@ietf.org>; Sun, 04 Feb 2007 22:18:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=i5nJKHPT8pa6I4rdzqGCJ+kIekLftmxnTRkZo2BTICugUi9nd+ShxPjBUZoD2QNnJyszXkjK+H1EqAuEIbA+qO5CgwJ9IDlsu3Na5Y5gSpnOv6W+FRsFp32Jsop9ucDhjNB0OINvevt/225J3aTjBdF+HHESE81ZHWktm7X+knI=
Received: by 10.82.120.14 with SMTP id s14mr1896469buc.1170656294731;
	Sun, 04 Feb 2007 22:18:14 -0800 (PST)
Received: by 10.82.139.3 with HTTP; Sun, 4 Feb 2007 22:18:14 -0800 (PST)
Message-ID: <ec62d6460702042218u4589dce0qfef373c9430ae577@mail.gmail.com>
Date: Mon, 5 Feb 2007 11:48:14 +0530
From: "anupam sadhukhan" <sadhukhan.anupam@gmail.com>
To: pwe3@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Mon, 05 Feb 2007 06:11:59 -0500
Subject: [PWE3] Query regarding the Control word in RFC 4619.
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0909335136=="
Errors-To: pwe3-bounces@ietf.org

--===============0909335136==
Content-Type: multipart/alternative; 
	boundary="----=_Part_45695_9476083.1170656294695"

------=_Part_45695_9476083.1170656294695
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

This is regarding the RFC 4619 (Encapsulation Methods for Transport of Frame
Relay over Multiprotocol Label Switching (MPLS) Networks)
section,7.3 and 7.4.

I couldn't figure out the exact reason for changing the sequence of the two
Bits B|F in the control word to F|B.
It will be very helpful if you can let me know the practical implications of
swapping the position of these two bits.

Regards,
Anupam.

------=_Part_45695_9476083.1170656294695
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi,</div>
<div>&nbsp;</div>
<div>This is regarding the RFC 4619 (Encapsulation Methods for Transport of Frame Relay over&nbsp;Multiprotocol Label Switching (MPLS) Networks) </div>
<div>section,7.3 and 7.4.</div>
<div>&nbsp;</div>
<div>I couldn&#39;t figure out the exact reason for changing the sequence of the two Bits B|F in the control word to F|B.</div>
<div>It will be very helpful if you can let me know the practical&nbsp;implications of swapping the position of these two bits.</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>Anupam.</div>
<div>&nbsp;</div>

------=_Part_45695_9476083.1170656294695--


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

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

--===============0909335136==--




From pwe3-bounces@ietf.org Mon Feb 05 06:25:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE1xh-0000ly-Kd; Mon, 05 Feb 2007 06:24:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE1xf-0000ja-Vy
	for pwe3@ietf.org; Mon, 05 Feb 2007 06:24:39 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE1xR-0007XG-Rs
	for pwe3@ietf.org; Mon, 05 Feb 2007 06:24:39 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 05 Feb 2007 12:24:25 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l15BOP4t003343; 
	Mon, 5 Feb 2007 12:24:25 +0100
Received: from [10.61.65.151] (ams3-vpn-dhcp407.cisco.com [10.61.65.151])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l15BONC8029360; 
	Mon, 5 Feb 2007 12:24:24 +0100 (MET)
Message-ID: <45C713E0.5040805@cisco.com>
Date: Mon, 05 Feb 2007 11:24:16 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: anupam sadhukhan <sadhukhan.anupam@gmail.com>
Subject: Re: [PWE3] Query regarding the Control word in RFC 4619.
References: <ec62d6460702042218u4589dce0qfef373c9430ae577@mail.gmail.com>
In-Reply-To: <ec62d6460702042218u4589dce0qfef373c9430ae577@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=576; t=1170674665;
	x=1171538665; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20Query=20regarding=20the=20Control=20word=20i
	n=20RFC=204619. |Sender:=20;
	bh=OgH95FCxv4ikcFK1Ny6lfbQYSL4KIQp+Ekbhk2CODIk=;
	b=I4quaV4oS8KiAu0ha7u1/kxJlpCw9iuKZ14/LMc8Uj1rrMEc0+RtWD9ojxTBDZzOf8NHUm/J
	mRUXhLgRjHCiDcuBS+R/aWG8/k6ADJYJZNRtPiGdB2d4agmeXVhoTWpR;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

anupam sadhukhan wrote:

> Hi,
>  
> This is regarding the RFC 4619 (Encapsulation Methods for Transport of 
> Frame Relay over Multiprotocol Label Switching (MPLS) Networks)
> section,7.3 and 7.4.
>  
> I couldn't figure out the exact reason for changing the sequence of the 
> two Bits B|F in the control word to F|B.
> It will be very helpful if you can let me know the 
> practical implications of swapping the position of these two bits.
>  
> Regards,
> Anupam.

The new mapping aligns the bit position with those in a frame-relay
header.

- Stewart




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



From pwe3-bounces@ietf.org Mon Feb 05 06:51:23 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HE2Md-0005gD-2m; Mon, 05 Feb 2007 06:50:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HE2Mb-0005eb-5T
	for pwe3@ietf.org; Mon, 05 Feb 2007 06:50:25 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE2MZ-0005gZ-SC
	for pwe3@ietf.org; Mon, 05 Feb 2007 06:50:25 -0500
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 05 Feb 2007 12:50:24 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l15BoN7G032150; 
	Mon, 5 Feb 2007 12:50:23 +0100
Received: from [10.61.65.151] (ams3-vpn-dhcp407.cisco.com [10.61.65.151])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l15BoJC8007072; 
	Mon, 5 Feb 2007 12:50:20 +0100 (MET)
Message-ID: <45C719F5.6030807@cisco.com>
Date: Mon, 05 Feb 2007 11:50:13 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <E1HCisc-00084h-2r@stiedprstage1.ietf.org>
In-Reply-To: <E1HCisc-00084h-2r@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=477; t=1170676223;
	x=1171540223; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20draft-ietf-mpls-icmp-08.txt |Sender:=20;
	bh=xQ6WLox3byGXN8vP3/QCY3EFUJWYc0Gy3uEw/Jjz7oI=;
	b=lv/XO42ixloiFdXDU9oE3WPkiD/xiB7uGw6WAIsT8NdbXWMt7O/8T2u0XeaFNhnoBQ0M0aNt
	mNjVnjJdk9eK9Ei1ocg/bWFDHalfxoXVngLkxn7/ISYLpNqVjwaXRg8Y;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: mpls@lists.ietf.org, pwe3 <pwe3@ietf.org>
Subject: [PWE3] draft-ietf-mpls-icmp-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

This draft explains what to do if you have
IP over MPLS, but not what to do if you
are carrying something other than IP - for
example a pseudowire.

It occurs to me that in some cases it would
be useful to resolve the MPLS destination
label to the destination IP address, and
send the diagnostic packet forward.

Clearly that does not work if you have
an unknown label or an unknown next hop,
but there may be other circumstances where it
is useful.

- Stewart





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



From pwe3-bounces@ietf.org Tue Feb 06 03:25:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HELdD-0004Xt-V2; Tue, 06 Feb 2007 03:24:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HELdC-0004X3-1I
	for pwe3@ietf.org; Tue, 06 Feb 2007 03:24:50 -0500
Received: from nf-out-0910.google.com ([64.233.182.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HELdA-0008O2-Pk
	for pwe3@ietf.org; Tue, 06 Feb 2007 03:24:50 -0500
Received: by nf-out-0910.google.com with SMTP id l36so109223nfa
	for <pwe3@ietf.org>; Tue, 06 Feb 2007 00:24:48 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=fg913xRkVvF33GYDcu/gnomEoThm009gmi2tCqxAKonOw+OWCsnYnmAxlmGW+IRE8edZSlyPj470r3r+tDP0m2AR6yOqJNXhRUgv0BsdxBjBCISqju47MCKXzp491dG8jSL8YDuNgjrdjhJ9eCqsFE1d7DgfxxO/I2hr2FokJhA=
Received: by 10.48.240.10 with SMTP id n10mr197882nfh.1170750288272;
	Tue, 06 Feb 2007 00:24:48 -0800 (PST)
Received: by 10.49.42.14 with HTTP; Tue, 6 Feb 2007 00:24:48 -0800 (PST)
Message-ID: <b33c82d0702060024s21cfa1c2x4e246d356d3b4df4@mail.gmail.com>
Date: Tue, 6 Feb 2007 13:54:48 +0530
From: "sujay gupta" <sujay.ietf@gmail.com>
To: pwe3@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [PWE3] test
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0283402070=="
Errors-To: pwe3-bounces@ietf.org

--===============0283402070==
Content-Type: multipart/alternative; 
	boundary="----=_Part_2417_5498796.1170750288239"

------=_Part_2417_5498796.1170750288239
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



------=_Part_2417_5498796.1170750288239
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br>

------=_Part_2417_5498796.1170750288239--


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

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

--===============0283402070==--




From pwe3-bounces@ietf.org Wed Feb 07 15:51:14 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtkC-0003VG-0m; Wed, 07 Feb 2007 15:50:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtjv-0003RJ-AY; Wed, 07 Feb 2007 15:50:03 -0500
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HEtju-0003Sa-RS; Wed, 07 Feb 2007 15:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id C104532993;
	Wed,  7 Feb 2007 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HEtju-0001ar-Jh; Wed, 07 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HEtju-0001ar-Jh@stiedprstage1.ietf.org>
Date: Wed, 07 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-aii-aggregate-02.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: AII Types for Aggregation
	Author(s)	: C. Metz, et al.
	Filename	: draft-ietf-pwe3-aii-aggregate-02.txt
	Pages		: 8
	Date		: 2007-2-7
	
The signaling protocols used to establish point-to-point pseudowires
   include type-length-value (TLV) fields that identify pseudowire
   endpoints called attachment individual identifiers (AII). This
   document defines AII structures in the form of new AII type-length-
   value fields that support AII aggregation for improved scalability
   and VPN autodiscovery. It is envisioned that this would be useful in
   large inter-domain virtual private wire service networks where
   pseudowires are established between selected local and remote PE
   nodes based on customer need.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-aii-aggregate-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-aii-aggregate-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: <2007-2-7110609.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-aii-aggregate-02.txt

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

Content-Type: text/plain
Content-ID: <2007-2-7110609.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Wed Feb 07 15:51:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtlG-0005Z1-VN; Wed, 07 Feb 2007 15:51:26 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtkx-00056M-B7; Wed, 07 Feb 2007 15:51:07 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HEtku-0002cz-Re; Wed, 07 Feb 2007 15:51:07 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 177A32ACAA;
	Wed,  7 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HEtju-0001bJ-Q7; Wed, 07 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HEtju-0001bJ-Q7@stiedprstage1.ietf.org>
Date: Wed, 07 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-09.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Definitions for Textual Conventions and for Managing Pseudo-Wires over PSN
	Author(s)	: T. Nadeau, et al.
	Filename	: draft-ietf-pwe3-pw-tc-mib-09.txt
	Pages		: 11
	Date		: 2007-2-7
	
This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions (TCs) to represent commonly-used Pseudo
   Wire (PW) management information.  The intent is that these TCs will
   be imported and used in PW-related MIB modules that would otherwise
   define their own representations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-pw-tc-mib-09.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-pw-tc-mib-09.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: <2007-2-7112455.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-tc-mib-09.txt

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

Content-Type: text/plain
Content-ID: <2007-2-7112455.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Wed Feb 07 17:04:06 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtnL-0000EC-4P; Wed, 07 Feb 2007 15:53:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HEtkx-00056O-Fq; Wed, 07 Feb 2007 15:51:07 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HEtku-0002d0-Sh; Wed, 07 Feb 2007 15:51:07 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 1AD222ACAB;
	Wed,  7 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HEtju-0001bM-Rd; Wed, 07 Feb 2007 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HEtju-0001bM-Rd@stiedprstage1.ietf.org>
Date: Wed, 07 Feb 2007 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-mib-10.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Pseudo Wire (PW) Management Information Base
	Author(s)	: D. Zelig, et al.
	Filename	: draft-ietf-pwe3-pw-mib-10.txt
	Pages		: 63
	Date		: 2007-2-7
	
This memo defines an experimental portion of the Management
   Information Base for use with network management protocols in the
   Internet community.  In particular, it describes managed objects for
   modeling of Pseudo Wire Edge-to-Edge services carried over a general
   Packet Switched Network.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-pw-mib-10.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-pw-mib-10.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: <2007-2-7112648.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-mib-10.txt

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

Content-Type: text/plain
Content-ID: <2007-2-7112648.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Thu Feb 08 03:05:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HF4Gf-0002yo-Dw; Thu, 08 Feb 2007 03:04:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HF4Gd-0002yT-EJ
	for pwe3@ietf.org; Thu, 08 Feb 2007 03:04:31 -0500
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HF4GX-0007UI-UR
	for pwe3@ietf.org; Thu, 08 Feb 2007 03:04:31 -0500
Received: from I2KF03BV-UKBR.domain1.systemhost.net ([193.113.197.43]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 Feb 2007 08:04:25 +0000
Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by
	I2KF03BV-UKBR.domain1.systemhost.net with Microsoft
	SMTPSVC(6.0.3790.211); Thu, 8 Feb 2007 08:04:24 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Feb 2007 08:04:24 -0000
Message-ID: <0536FC9B908BEC4597EE721BE6A353891B31CC53@i2km07-ukbr.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mpls] draft-ietf-mpls-icmp-08.txt
Thread-Index: AcdK+Gf4jHpmyZNATDC5yefihHu/RgAXFSWg
From: <neil.2.harrison@bt.com>
To: <rbonica@juniper.net>,
	<stbryant@cisco.com>
X-OriginalArrivalTime: 08 Feb 2007 08:04:24.0714 (UTC)
	FILETIME=[BF4DE6A0:01C74B57]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: mpls@lists.ietf.org, pwe3@ietf.org
Subject: [PWE3] RE: [mpls] draft-ietf-mpls-icmp-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Ron/Stewart,

The real problem here is that we are not always clear about which layer
network are are talking about.  ICMP is part of the IP layer network's
(and ONLY the IP layer network's) management-plane.  When layer networks
get functionally coupled then folks are tempted to devise clever ways to
use the protocols that belong to one layer network in/by another layer
network....but this is really not a good general idea (this is
especially true if the layer networks involved belong to different
network modes).

The consequence of functionally coupling different layer networks is
almost always practically manifested as increased complexity and
increased marginal cost, ie one ends up with diseconomies of
scale....though it usually takes significant deployment to see this to
really figure-out what the real cause is (though it is my experience
most folks don't even see this anyway).

regards, Neil

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net]=20
> Sent: 07 February 2007 20:37
> To: Stewart Bryant
> Cc: mpls@lists.ietf.org; pwe3
> Subject: Re: [mpls] draft-ietf-mpls-icmp-08.txt
>=20
>=20
> Hi Stewart,
>=20
> As currently defined, the ICMP message is a response to the=20
> unroutable IP datagram. In an application like pseudowires,=20
> you wouldn't send an ICMP packet.
>=20
> However, now that ICMP messages are extensible, people might=20
> find new applications form them. But let's say that this is=20
> beyond the scope of this draft and fair game for future drafts.
>=20
>                                      Ron
>=20
> Stewart Bryant wrote:
> > This draft explains what to do if you have
> > IP over MPLS, but not what to do if you
> > are carrying something other than IP - for
> > example a pseudowire.
> >=20
> > It occurs to me that in some cases it would
> > be useful to resolve the MPLS destination
> > label to the destination IP address, and
> > send the diagnostic packet forward.
> >=20
> > Clearly that does not work if you have
> > an unknown label or an unknown next hop,
> > but there may be other circumstances where it
> > is useful.
> >=20
> > - Stewart
> >=20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > mpls mailing list
> > mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls
> >=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
>=20

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



From pwe3-bounces@ietf.org Thu Feb 08 03:31:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HF4fm-0006wZ-L5; Thu, 08 Feb 2007 03:30:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HF4fl-0006wU-0m
	for pwe3@ietf.org; Thu, 08 Feb 2007 03:30:29 -0500
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HF4fj-0006si-N4
	for pwe3@ietf.org; Thu, 08 Feb 2007 03:30:28 -0500
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l188UEb17812; Thu, 8 Feb 2007 03:30:15 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Feb 2007 03:30:14 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE0C3AE8CA@zcarhxm2.corp.nortel.com>
In-Reply-To: <D3C85156A12AAB4DB23F598007E9826D0174596E@dove.seabridge.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-allan-pw-o-pbt-02.txt
Thread-Index: AcdHr9GajnDl8IJ0Ttm7vIrkpr2iUQDqyOzA
From: "David Allan" <dallan@nortel.com>
To: "Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: pwe3@ietf.org
Subject: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Nurit:

You're correct in nothing the PSN is more .1Q than anything. It is
simply a provider MAC space.

It would be possible to genericize the draft, given there is an
interested community....

Rgds
Dave
=20
=20

________________________________

From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]=20
Sent: Saturday, February 03, 2007 11:25 AM
To: Allan, David (CAR:NS00)
Cc: pwe3@ietf.org; Nurit Sprecher
Subject: draft-allan-pw-o-pbt-02.txt



Hi Dave,

Thanks for the updated draft. I believe it is useful.

I wonder what is the difference between PBT and (static) Ethernet as
PSNs as appear in your draft? As I see it, PBT is more a control concept
and not a dataplane or PSN.

Reading the draft it even seems to me that the draft defines PW over
Ethernet PSN (which is set up using PBT mode) and for that sake there is
even no difference between 802.1ad dataplane and 802.1ah. Is that true?=20

Can we modify this draft to be a generic one (as it actually is) and
make it PW over Ethernet PSN?

Best regards,

Nurit.

=20

=20

=20

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Friday, February 02, 2007 22:50
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt=20

=20

A New Internet-Draft is available from the on-line Internet-Drafts=20

directories.

=20

=20

      Title       : Pseudo Wires over Provider Backbone Transport

      Author(s)   : D. Allan

      Filename    : draft-allan-pw-o-pbt-02.txt

      Pages       : 7

      Date        : 2007-2-2

     =20

This memo describes architecture and procedures for the operation of=20

   pseudo wires over provider backbone transport (PBT).

=20

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-allan-pw-o-pbt-02.txt

=20

To remove yourself from the I-D Announcement list, send a message to=20

i-d-announce-request@ietf.org with the word unsubscribe in the body of=20

the message.=20

You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20

to change your subscription settings.

=20

Internet-Drafts are also available by anonymous FTP. Login with the=20

username "anonymous" and a password of your e-mail address. After=20

logging in, type "cd internet-drafts" and then=20

"get draft-allan-pw-o-pbt-02.txt".

=20

A list of Internet-Drafts directories can be found in

http://www.ietf.org/shadow.html=20

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=20

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

=20

Send a message to:

      mailserv@ietf.org.

In the body type:

      "FILE /internet-drafts/draft-allan-pw-o-pbt-02.txt".

     =20

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.

=20

Below is the data which will enable a MIME compliant mail reader

implementation to automatically retrieve the ASCII version of the

Internet-Draft.


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



From pwe3-bounces@ietf.org Thu Feb 08 09:03:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HF9rE-000269-Cn; Thu, 08 Feb 2007 09:02:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HF9rC-000260-B6
	for pwe3@ietf.org; Thu, 08 Feb 2007 09:02:38 -0500
Received: from ripley.ciena.com ([63.118.34.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HF9rB-00020a-1C
	for pwe3@ietf.org; Thu, 08 Feb 2007 09:02:38 -0500
Received: from lin1-118-39-27.ciena.com (HELO mdmxm02.ciena.com)
	([63.118.39.27])
	by ripley.ciena.com with ESMTP; 08 Feb 2007 09:02:35 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
Date: Thu, 8 Feb 2007 09:01:03 -0500
Message-ID: <3C13767EA2F93441AFB13A630204F1B233A822@mamxm02.ciena.com>
In-Reply-To: <87AC5F88F03E6249AEA68D40BD3E00BE0C3AE8CA@zcarhxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-allan-pw-o-pbt-02.txt
Thread-Index: AcdHr9GajnDl8IJ0Ttm7vIrkpr2iUQDqyOzAAAuD9cA=
From: "Shah, Himanshu" <hshah@ciena.com>
To: "David Allan" <dallan@nortel.com>,
	"Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
X-OriginalArrivalTime: 08 Feb 2007 14:01:05.0982 (UTC)
	FILETIME=[93743DE0:01C74B89]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Dave, Nurit,

Isn't this what is now widely known as 'dry-martini'?

/himanshu

> -----Original Message-----
> From: David Allan [mailto:dallan@nortel.com]
> Sent: Thursday, February 08, 2007 3:30 AM
> To: Nurit Sprecher
> Cc: pwe3@ietf.org
> Subject: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
>=20
>=20
> Hi Nurit:
>=20
> You're correct in nothing the PSN is more .1Q than anything. It is
> simply a provider MAC space.
>=20
> It would be possible to genericize the draft, given there is an
> interested community....
>=20
> Rgds
> Dave
> =20
> =20
>=20
> ________________________________
>=20
> From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]=20
> Sent: Saturday, February 03, 2007 11:25 AM
> To: Allan, David (CAR:NS00)
> Cc: pwe3@ietf.org; Nurit Sprecher
> Subject: draft-allan-pw-o-pbt-02.txt
>=20
>=20
>=20
> Hi Dave,
>=20
> Thanks for the updated draft. I believe it is useful.
>=20
> I wonder what is the difference between PBT and (static) Ethernet as
> PSNs as appear in your draft? As I see it, PBT is more a=20
> control concept
> and not a dataplane or PSN.
>=20
> Reading the draft it even seems to me that the draft defines PW over
> Ethernet PSN (which is set up using PBT mode) and for that=20
> sake there is
> even no difference between 802.1ad dataplane and 802.1ah. Is=20
> that true?=20
>=20
> Can we modify this draft to be a generic one (as it actually is) and
> make it PW over Ethernet PSN?
>=20
> Best regards,
>=20
> Nurit.
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
> Sent: Friday, February 02, 2007 22:50
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt=20
>=20
> =20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts=20
>=20
> directories.
>=20
> =20
>=20
> =20
>=20
>       Title       : Pseudo Wires over Provider Backbone Transport
>=20
>       Author(s)   : D. Allan
>=20
>       Filename    : draft-allan-pw-o-pbt-02.txt
>=20
>       Pages       : 7
>=20
>       Date        : 2007-2-2
>=20
>      =20
>=20
> This memo describes architecture and procedures for the operation of=20
>=20
>    pseudo wires over provider backbone transport (PBT).
>=20
> =20
>=20
> A URL for this Internet-Draft is:
>=20
> http://www.ietf.org/internet-drafts/draft-allan-pw-o-pbt-02.txt
>=20
> =20
>=20
> To remove yourself from the I-D Announcement list, send a message to=20
>=20
> i-d-announce-request@ietf.org with the word unsubscribe in=20
> the body of=20
>=20
> the message.=20
>=20
> You can also visit=20
> https://www1.ietf.org/mailman/listinfo/I-D-announce=20
>=20
> to change your subscription settings.
>=20
> =20
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the=20
>=20
> username "anonymous" and a password of your e-mail address. After=20
>=20
> logging in, type "cd internet-drafts" and then=20
>=20
> "get draft-allan-pw-o-pbt-02.txt".
>=20
> =20
>=20
> A list of Internet-Drafts directories can be found in
>=20
> http://www.ietf.org/shadow.html=20
>=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> =20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> =20
>=20
> Send a message to:
>=20
>       mailserv@ietf.org.
>=20
> In the body type:
>=20
>       "FILE /internet-drafts/draft-allan-pw-o-pbt-02.txt".
>=20
>      =20
>=20
> NOTE: The mail server at ietf.org can return the document in
>=20
>       MIME-encoded form by using the "mpack" utility.  To use this
>=20
>       feature, insert the command "ENCODING mime" before the "FILE"
>=20
>       command.  To decode the response(s), you will need "munpack" or
>=20
>       a MIME-compliant mail reader.  Different MIME-compliant mail
> readers
>=20
>       exhibit different behavior, especially when dealing with
>=20
>       "multipart" MIME messages (i.e. documents which have been split
>=20
>       up into multiple messages), so check your local documentation on
>=20
>       how to manipulate these messages.
>=20
> =20
>=20
> Below is the data which will enable a MIME compliant mail reader
>=20
> implementation to automatically retrieve the ASCII version of the
>=20
> Internet-Draft.
>=20
>=20
> _______________________________________________
> 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



From pwe3-bounces@ietf.org Thu Feb 08 09:19:33 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFA7F-0001o4-Br; Thu, 08 Feb 2007 09:19:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HEtXG-0005rn-89
	for pwe3@ietf.org; Wed, 07 Feb 2007 15:36:58 -0500
Received: from kremlin.juniper.net ([207.17.137.120])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEtXE-0001Of-V3
	for pwe3@ietf.org; Wed, 07 Feb 2007 15:36:58 -0500
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by kremlin.juniper.net with ESMTP; 07 Feb 2007 12:36:56 -0800
X-IronPort-AV: i="4.13,296,1167638400"; 
	d="scan'208"; a="652634934:sNHT31430660"
Received: from [172.25.51.58] ([172.25.51.58] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 Feb 2007 15:36:55 -0500
Message-ID: <45CA3862.6000404@juniper.net>
Date: Wed, 07 Feb 2007 15:36:50 -0500
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stewart Bryant <stbryant@cisco.com>
References: <E1HCisc-00084h-2r@stiedprstage1.ietf.org>
	<45C719F5.6030807@cisco.com>
In-Reply-To: <45C719F5.6030807@cisco.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Feb 2007 20:36:55.0587 (UTC)
	FILETIME=[B4E89F30:01C74AF7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
X-Mailman-Approved-At: Thu, 08 Feb 2007 09:19:12 -0500
Cc: mpls@lists.ietf.org, pwe3 <pwe3@ietf.org>
Subject: [PWE3] Re: [mpls] draft-ietf-mpls-icmp-08.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Stewart,

As currently defined, the ICMP message is a response to the unroutable
IP datagram. In an application like pseudowires, you wouldn't send an
ICMP packet.

However, now that ICMP messages are extensible, people might find new
applications form them. But let's say that this is beyond the scope of
this draft and fair game for future drafts.

                                     Ron

Stewart Bryant wrote:
> This draft explains what to do if you have
> IP over MPLS, but not what to do if you
> are carrying something other than IP - for
> example a pseudowire.
> 
> It occurs to me that in some cases it would
> be useful to resolve the MPLS destination
> label to the destination IP address, and
> send the diagnostic packet forward.
> 
> Clearly that does not work if you have
> an unknown label or an unknown next hop,
> but there may be other circumstances where it
> is useful.
> 
> - Stewart
> 
> 
> 
> 
> 
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
> 

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



From pwe3-bounces@ietf.org Thu Feb 08 09:26:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFAEP-00062d-Mu; Thu, 08 Feb 2007 09:26:37 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFAEO-00062Y-MQ
	for pwe3@ietf.org; Thu, 08 Feb 2007 09:26:36 -0500
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFAEM-0007ND-7y
	for pwe3@ietf.org; Thu, 08 Feb 2007 09:26:36 -0500
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
	[47.129.230.99])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l18EQUm02760; Thu, 8 Feb 2007 09:26:30 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
Date: Thu, 8 Feb 2007 09:26:14 -0500
Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE0C3AE8DA@zcarhxm2.corp.nortel.com>
In-Reply-To: <3C13767EA2F93441AFB13A630204F1B233A822@mamxm02.ciena.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
Thread-Index: AcdHr9GajnDl8IJ0Ttm7vIrkpr2iUQDqyOzAAAuD9cAAAPxx4A==
From: "David Allan" <dallan@nortel.com>
To: "Shah, Himanshu" <hshah@ciena.com>,
	"Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Cc: pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

IMO a strict subset, "dry-martini" postulated anything could take the
role of label... ;-)

Dave=20

-----Original Message-----
From: Shah, Himanshu [mailto:hshah@ciena.com]=20
Sent: Thursday, February 08, 2007 9:01 AM
To: Allan, David (CAR:NS00); Nurit Sprecher
Cc: pwe3@ietf.org
Subject: RE: [PWE3] RE: draft-allan-pw-o-pbt-02.txt

Dave, Nurit,

Isn't this what is now widely known as 'dry-martini'?

/himanshu

> -----Original Message-----
> From: David Allan [mailto:dallan@nortel.com]
> Sent: Thursday, February 08, 2007 3:30 AM
> To: Nurit Sprecher
> Cc: pwe3@ietf.org
> Subject: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
>=20
>=20
> Hi Nurit:
>=20
> You're correct in nothing the PSN is more .1Q than anything. It is=20
> simply a provider MAC space.
>=20
> It would be possible to genericize the draft, given there is an=20
> interested community....
>=20
> Rgds
> Dave
> =20
> =20
>=20
> ________________________________
>=20
> From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]
> Sent: Saturday, February 03, 2007 11:25 AM
> To: Allan, David (CAR:NS00)
> Cc: pwe3@ietf.org; Nurit Sprecher
> Subject: draft-allan-pw-o-pbt-02.txt
>=20
>=20
>=20
> Hi Dave,
>=20
> Thanks for the updated draft. I believe it is useful.
>=20
> I wonder what is the difference between PBT and (static) Ethernet as=20
> PSNs as appear in your draft? As I see it, PBT is more a control=20
> concept and not a dataplane or PSN.
>=20
> Reading the draft it even seems to me that the draft defines PW over=20
> Ethernet PSN (which is set up using PBT mode) and for that sake there=20
> is even no difference between 802.1ad dataplane and 802.1ah. Is that=20
> true?
>=20
> Can we modify this draft to be a generic one (as it actually is) and=20
> make it PW over Ethernet PSN?
>=20
> Best regards,
>=20
> Nurit.
>=20
> =20
>=20
> =20
>=20
> =20
>=20
> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Friday, February 02, 2007 22:50
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt
>=20
> =20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
>=20
> directories.
>=20
> =20
>=20
> =20
>=20
>       Title       : Pseudo Wires over Provider Backbone Transport
>=20
>       Author(s)   : D. Allan
>=20
>       Filename    : draft-allan-pw-o-pbt-02.txt
>=20
>       Pages       : 7
>=20
>       Date        : 2007-2-2
>=20
>      =20
>=20
> This memo describes architecture and procedures for the operation of
>=20
>    pseudo wires over provider backbone transport (PBT).
>=20
> =20
>=20
> A URL for this Internet-Draft is:
>=20
> http://www.ietf.org/internet-drafts/draft-allan-pw-o-pbt-02.txt
>=20
> =20
>=20
> To remove yourself from the I-D Announcement list, send a message to
>=20
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
>=20
> the message.=20
>=20
> You can also visit
> https://www1.ietf.org/mailman/listinfo/I-D-announce
>=20
> to change your subscription settings.
>=20
> =20
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the
>=20
> username "anonymous" and a password of your e-mail address. After
>=20
> logging in, type "cd internet-drafts" and then
>=20
> "get draft-allan-pw-o-pbt-02.txt".
>=20
> =20
>=20
> A list of Internet-Drafts directories can be found in
>=20
> http://www.ietf.org/shadow.html
>=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> =20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> =20
>=20
> Send a message to:
>=20
>       mailserv@ietf.org.
>=20
> In the body type:
>=20
>       "FILE /internet-drafts/draft-allan-pw-o-pbt-02.txt".
>=20
>      =20
>=20
> NOTE: The mail server at ietf.org can return the document in
>=20
>       MIME-encoded form by using the "mpack" utility.  To use this
>=20
>       feature, insert the command "ENCODING mime" before the "FILE"
>=20
>       command.  To decode the response(s), you will need "munpack" or
>=20
>       a MIME-compliant mail reader.  Different MIME-compliant mail=20
> readers
>=20
>       exhibit different behavior, especially when dealing with
>=20
>       "multipart" MIME messages (i.e. documents which have been split
>=20
>       up into multiple messages), so check your local documentation on
>=20
>       how to manipulate these messages.
>=20
> =20
>=20
> Below is the data which will enable a MIME compliant mail reader
>=20
> implementation to automatically retrieve the ASCII version of the
>=20
> Internet-Draft.
>=20
>=20
> _______________________________________________
> 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



From pwe3-bounces@ietf.org Thu Feb 08 18:51:43 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFJ2l-0002fL-U9; Thu, 08 Feb 2007 18:51:11 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFJ2d-0002FT-9M; Thu, 08 Feb 2007 18:51:03 -0500
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HFJ2c-0003ZG-Uq; Thu, 08 Feb 2007 18:51:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id DBDE02ACD7;
	Thu,  8 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HFJ1e-0006vT-Kv; Thu, 08 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HFJ1e-0006vT-Kv@stiedprstage1.ietf.org>
Date: Thu, 08 Feb 2007 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-tc-mib-10.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Definitions for Textual Conventions and for Managing Pseudo-Wires over PSN
	Author(s)	: T. Nadeau, et al.
	Filename	: draft-ietf-pwe3-pw-tc-mib-10.txt
	Pages		: 11
	Date		: 2007-2-8
	
This memo defines a Management Information Base (MIB) module which
   contains Textual Conventions (TCs) to represent commonly-used Pseudo
   Wire (PW) management information.  The intent is that these TCs will
   be imported and used in PW-related MIB modules that would otherwise
   define their own representations.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-pw-tc-mib-10.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-pw-tc-mib-10.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: <2007-2-8161613.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-tc-mib-10.txt

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

Content-Type: text/plain
Content-ID: <2007-2-8161613.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Fri Feb 09 04:22:44 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFRwf-0002BX-Um; Fri, 09 Feb 2007 04:21:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFRwd-00029W-Cq
	for pwe3@ietf.org; Fri, 09 Feb 2007 04:21:28 -0500
Received: from [212.25.127.226] (helo=gfi-gw.seabridge.co.il)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFRwa-0006k0-UU
	for pwe3@ietf.org; Fri, 09 Feb 2007 04:21:27 -0500
Received: from dove.seabridge.co.il ([172.30.10.115]) by
	gfi-gw.seabridge.co.il with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 9 Feb 2007 11:21:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 9 Feb 2007 11:21:18 +0200
Message-ID: <D3C85156A12AAB4DB23F598007E9826D0183269A@dove.seabridge.co.il>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-allan-pw-o-pbt-02.txt
Thread-Index: AcdHr9GajnDl8IJ0Ttm7vIrkpr2iUQDqyOzAADNkdkA=
From: "Nurit Sprecher" <nurit.sprecher@SeabridgeNetworks.com>
To: "David Allan" <dallan@nortel.com>
X-OriginalArrivalTime: 09 Feb 2007 09:21:19.0771 (UTC)
	FILETIME=[A88176B0:01C74C2B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: pwe3@ietf.org
Subject: [PWE3] RE: draft-allan-pw-o-pbt-02.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi Dave,
I would be interest in joining a generalized document.
Regards,
Nurit


-----Original Message-----
From: David Allan [mailto:dallan@nortel.com]=20
Sent: Thursday, February 08, 2007 10:30
To: Nurit Sprecher
Cc: pwe3@ietf.org
Subject: RE: draft-allan-pw-o-pbt-02.txt

Hi Nurit:

You're correct in nothing the PSN is more .1Q than anything. It is
simply a provider MAC space.

It would be possible to genericize the draft, given there is an
interested community....

Rgds
Dave
=20
=20

________________________________

From: Nurit Sprecher [mailto:nurit.sprecher@SeabridgeNetworks.com]=20
Sent: Saturday, February 03, 2007 11:25 AM
To: Allan, David (CAR:NS00)
Cc: pwe3@ietf.org; Nurit Sprecher
Subject: draft-allan-pw-o-pbt-02.txt



Hi Dave,

Thanks for the updated draft. I believe it is useful.

I wonder what is the difference between PBT and (static) Ethernet as
PSNs as appear in your draft? As I see it, PBT is more a control concept
and not a dataplane or PSN.

Reading the draft it even seems to me that the draft defines PW over
Ethernet PSN (which is set up using PBT mode) and for that sake there is
even no difference between 802.1ad dataplane and 802.1ah. Is that true?=20

Can we modify this draft to be a generic one (as it actually is) and
make it PW over Ethernet PSN?

Best regards,

Nurit.

=20

=20

=20

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Friday, February 02, 2007 22:50
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-allan-pw-o-pbt-02.txt=20

=20

A New Internet-Draft is available from the on-line Internet-Drafts=20

directories.

=20

=20

      Title       : Pseudo Wires over Provider Backbone Transport

      Author(s)   : D. Allan

      Filename    : draft-allan-pw-o-pbt-02.txt

      Pages       : 7

      Date        : 2007-2-2

     =20

This memo describes architecture and procedures for the operation of=20

   pseudo wires over provider backbone transport (PBT).

=20

A URL for this Internet-Draft is:

http://www.ietf.org/internet-drafts/draft-allan-pw-o-pbt-02.txt

=20

To remove yourself from the I-D Announcement list, send a message to=20

i-d-announce-request@ietf.org with the word unsubscribe in the body of=20

the message.=20

You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20

to change your subscription settings.

=20

Internet-Drafts are also available by anonymous FTP. Login with the=20

username "anonymous" and a password of your e-mail address. After=20

logging in, type "cd internet-drafts" and then=20

"get draft-allan-pw-o-pbt-02.txt".

=20

A list of Internet-Drafts directories can be found in

http://www.ietf.org/shadow.html=20

or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=20

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

=20

Send a message to:

      mailserv@ietf.org.

In the body type:

      "FILE /internet-drafts/draft-allan-pw-o-pbt-02.txt".

     =20

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.

=20

Below is the data which will enable a MIME compliant mail reader

implementation to automatically retrieve the ASCII version of the

Internet-Draft.


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



From pwe3-bounces@ietf.org Mon Feb 12 06:08:59 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGZ2S-0004cJ-N1; Mon, 12 Feb 2007 06:08:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGZ2R-0004bn-3j
	for pwe3@ietf.org; Mon, 12 Feb 2007 06:08:03 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGZ2K-00010M-ME
	for pwe3@ietf.org; Mon, 12 Feb 2007 06:08:03 -0500
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	EB1E420672 for <pwe3@ietf.org>; Mon, 12 Feb 2007 12:07:45 +0100 (CET)
X-AuditID: c1b4fb3c-aefc6bb0000007de-13-45d04a81d420 
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	DC330205A4 for <pwe3@ietf.org>; Mon, 12 Feb 2007 12:07:45 +0100 (CET)
Received: from esealmw110.eemea.ericsson.se ([153.88.200.78]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 12:07:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Feb 2007 12:07:46 +0100
Message-ID: <271DCF0DD53DB34EB20C50A3FBF26E632E252E@esealmw110.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CESoPSN
Thread-Index: AcdOlgYxy6fmjxEiRSCAdKsgMnruvg==
From: "Orazio Toscano \(GA/ERI\)" <orazio.toscano@ericsson.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 12 Feb 2007 11:07:45.0627 (UTC)
	FILETIME=[060302B0:01C74E96]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [PWE3] CESoPSN
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

One doubt regarding the Ietf-draft-pwe3-cesopsn.
According to the latest versions ( 04/05/06/07 from March 2006) the PSN, =
Multiplexing and CESoPSN Layers foresee the CESoPSN control word just =
before the RTP fields and the Payload area with the exception of IPv4/v6 =
and UDP (Figures 1a, 1b and 1c). In this case the CESoPSN cotrol word is =
after the RTP fields and just before the Payload Area.
Seeing the Signaling Packets PSN, Multiplexing and CESoPSN layers =
instead the control word is just before the RTP fields and the payload =
area only for the MPLS case; in the IPv4/v6 and L2TPv3 and in the =
IPv4/v6 and UDP cases the Control word is after the RTP field and just =
before the Encoded Ce application state (Figures 4a and 4b).
So regarding the new definitions and the IPv4/v6 and L2TPv3 case we have =
a different relative position of the RTP and CESoPSN control words in =
Signaling Packets compared to payload Packets.
=20
Thank you for comments.
=20
Best Regards=20
Orazio Toscano=20

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



From pwe3-bounces@ietf.org Mon Feb 12 06:44:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGZbI-0006p4-16; Mon, 12 Feb 2007 06:44:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGZbG-0006oT-5r; Mon, 12 Feb 2007 06:44:02 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HGZbE-0006sc-L0; Mon, 12 Feb 2007 06:44:02 -0500
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 12 Feb 2007 12:44:01 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1CBhxlu011769; 
	Mon, 12 Feb 2007 12:43:59 +0100
Received: from [10.61.64.81] (ams3-vpn-dhcp81.cisco.com [10.61.64.81])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l1CBhuC8004840; 
	Mon, 12 Feb 2007 12:43:56 +0100 (MET)
Message-ID: <45D052F7.5000209@cisco.com>
Date: Mon, 12 Feb 2007 11:43:51 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tictoc@ietf.org, pwe3 <pwe3@ietf.org>, ntpwg@ntp.isc.org,
	IEEE1588 <stds-1588@IEEE.ORG>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=667; t=1171280639;
	x=1172144639; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20TICTOC=20scheduled=20for=20IETF68=20(Prague)
	|Sender:=20; bh=fM40ZevJVzX9fI3AdPBswaZJTRUlpITDEy/0oeUT0Y4=;
	b=DUdIw/0Xpxt/hfScs3mjA4kmFMAbu9VAtdpkp6f74NY0w7fzMvgtCAf0adoP2cW2dAx3zmpZ
	3oDrcY8qhTSYrjFmw/L8ayGAtn7kAFfIFSdmRBCaBAuJag0Ru9TY9hSx;
Authentication-Results: ams-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
Subject: [PWE3] TICTOC scheduled for IETF68 (Prague)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


The TICTOC BOF has been scheduled for Tuesday 20th March
0900 to 1130.

More information on TICTOC can be obtained from:

http://www1.tools.ietf.org/bof/trac/wiki#TimeframeIETF68Prague

It's not yet determined who will be chairing the BOF and
the detailed agenda is still being worked on. In the
meantime I suggest that those that wish to present on
this topic send requests to the TICTOC list.

Stewart


PS: for those not familiar with IETF procedures, the
IETF agenda will not be final until much closer to the
meeting, so please keep an eye on the IETF agenda page

https://datatracker.ietf.org/public/meeting_agenda_html.cgi?meeting_num=68

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



From pwe3-bounces@ietf.org Tue Feb 13 15:52:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4dR-0002sv-GS; Tue, 13 Feb 2007 15:52:21 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4cB-0000up-RP; Tue, 13 Feb 2007 15:51:04 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HH4cB-0003IC-Dm; Tue, 13 Feb 2007 15:51:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 68C5717665;
	Tue, 13 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HH4bD-0002yE-4J; Tue, 13 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HH4bD-0002yE-4J@stiedprstage1.ietf.org>
Date: Tue, 13 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-pw-atm-mib-02.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Managed Objects for ATM over Packet Switched Network (PSN)
	Author(s)	: T. Nadeau, et al.
	Filename	: draft-ietf-pwe3-pw-atm-mib-02.txt
	Pages		: 37
	Date		: 2007-2-13
	
This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   the Internet community.  In particular, it describes managed objects
   for modeling ATM Pseudowire (PW) carrying ATM cells over Packet
   Switch Network (PSN) as defined in the PWE3 [ATMENCAP]and [ATMTRANS].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-atm-mib-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-pw-atm-mib-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-pw-atm-mib-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: <2007-2-13142629.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-pw-atm-mib-02.txt

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

Content-Type: text/plain
Content-ID: <2007-2-13142629.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Tue Feb 13 15:52:51 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4dN-0002lY-UY; Tue, 13 Feb 2007 15:52:18 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HH4cB-0000us-Uq; Tue, 13 Feb 2007 15:51:04 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HH4cB-0003ID-Fe; Tue, 13 Feb 2007 15:51:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 7A97D17677;
	Tue, 13 Feb 2007 20:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HH4bD-0002yR-7b; Tue, 13 Feb 2007 15:50:03 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HH4bD-0002yR-7b@stiedprstage1.ietf.org>
Date: Tue, 13 Feb 2007 15:50:03 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-tdm-mib-07.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Managed Objects for TDM over Packet Switched Network (PSN)
	Author(s)	: O. Nicklass.
	Filename	: draft-ietf-pwe3-tdm-mib-07.txt
	Pages		: 42
	Date		: 2007-2-13
	
This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects for pseudo wire
   encapsulation for structured or unstructured TDM (T1, E1, T3, E3)
   circuits over a Packet Switch Network (PSN).

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-tdm-mib-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-tdm-mib-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: <2007-2-13143238.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2007-2-13143238.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




From pwe3-bounces@ietf.org Thu Feb 15 07:09:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHfP7-000480-SB; Thu, 15 Feb 2007 07:08:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HHfP5-00047s-Uc
	for pwe3@ietf.org; Thu, 15 Feb 2007 07:07:59 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHfOr-0003U7-NB
	for pwe3@ietf.org; Thu, 15 Feb 2007 07:07:59 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l1FC7WZn019137;
	Thu, 15 Feb 2007 06:07:42 -0600 (CST)
Received: from inexp02.in.lucent.com ([135.254.223.66]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Feb 2007 06:07:39 -0600
Received: from INEXC1U02.in.lucent.com ([135.254.223.25]) by
	inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 15 Feb 2007 17:37:35 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Date: Thu, 15 Feb 2007 17:37:34 +0530
Message-ID: <1A209B72F475B54FB693B7EA2ED2980E13F10B@INEXC1U02.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs
Thread-Index: AcdGHHvOxyvkWzgoSVue/SkrX5cq5AADTF9wArPEadAAAEXwMA==
References: <3067688A-7C16-45EC-B12B-BBC327C6575C@cisco.com>
	<457D36D9D89B5B47BC06DA869B1C815D03208BDA@exrad3.ad.rad.co.il> 
From: "Ramalingam, Swaminathan \(Swaminathan\)" <swamir@alcatel-lucent.com>
To: "Ramalingam, Swaminathan \(Swaminathan\)" <swamir@alcatel-lucent.com>,
	"Yaakov Stein" <yaakov_s@rad.com>, "Thomas D. Nadeau" <tnadeau@cisco.com>
X-OriginalArrivalTime: 15 Feb 2007 12:07:35.0181 (UTC)
	FILETIME=[E0CABBD0:01C750F9]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: "Ahluwalia, Ajit \(Ajit\)" <ajitahlu@alcatel-lucent.com>, pwe3@ietf.org
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1654198352=="
Errors-To: pwe3-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1654198352==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C750F9.E09513F9"

This is a multi-part message in MIME format.

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

Tom,

=20

Do you have some other idea?

=20

As Yaakov specified, how about going ICMP way?

=20

Thanks,

Swami

=20

________________________________

From: Yaakov Stein [mailto:yaakov_s@rad.com]=20
Sent: Thursday, February 01, 2007 11:23 PM
To: Thomas D. Nadeau
Cc: Ramalingam, Swaminathan (Swaminathan); Ahluwalia, Ajit (Ajit);
pwe3@ietf.org
Subject: RE: [PWE3] Inband/out-of-band TDM OAM format for MPLS PSNs

=20

So, if PWE accepts the use of Y.1731 PDUs as VCCV payloads,   we will
automatically get everything needed.

=20

I am reluctant to do this, as I was when it was originally proposed.

=20

--Tom


[YJS] So what do you suggest ?=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3020" name=3DGENERATOR><!--[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]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: SimSun;
}
@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: @SimSun;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US=20
style=3D"WORD-WRAP: break-word; khtml-nbsp-mode: space; =
khtml-line-break: after-white-space"=20
vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Tom,<o:p></o:p></SPAN></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Do you have =
some other=20
idea?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">As Yaakov =
specified,=20
how about going ICMP way?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Thanks,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Swami<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Yaakov=20
Stein [mailto:yaakov_s@rad.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, February 01, 2007 =
11:23=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Thomas D.=20
Nadeau<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
<st1:PersonName=20
w:st=3D"on">Ramalingam, Swaminathan</st1:PersonName> (Swaminathan);=20
<st1:PersonName w:st=3D"on">Ahluwalia, Ajit</st1:PersonName> (Ajit);=20
pwe3@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> RE:=20
[PWE3] Inband/out-of-band TDM OAM format for MPLS=20
PSNs</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">So, if PWE =
accepts the=20
use of Y.1731 PDUs as&nbsp;VCCV payloads,&nbsp; &nbsp;we will =
automatically get=20
everything needed.</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">I am reluctant to do this, as I was when it =
was=20
originally proposed.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">--Tom<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><BR></SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">[YJS] So=20
what do you suggest=20
?&nbsp;</SPAN></FONT><o:p></o:p></P></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C750F9.E09513F9--


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

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

--===============1654198352==--




From pwe3-bounces@ietf.org Fri Feb 16 12:45:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI784-0003TI-Mm; Fri, 16 Feb 2007 12:44:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI781-0003SM-Ad; Fri, 16 Feb 2007 12:44:14 -0500
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI77z-0000th-VE; Fri, 16 Feb 2007 12:44:13 -0500
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id l1GHiBnD006178; 
	Fri, 16 Feb 2007 09:44:11 -0800
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id l1GHiBre006177;
	Fri, 16 Feb 2007 09:44:11 -0800
Date: Fri, 16 Feb 2007 09:44:11 -0800
Message-Id: <200702161744.l1GHiBre006177@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org
Subject: [PWE3] RFC 4816 on Pseudowire Emulation Edge-to-Edge (PWE3)
	Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4816

        Title:      Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous 
                    Transfer Mode (ATM) Transparent Cell Transport 
                    Service 
        Author:     A. Malis, L. Martini,
                    J. Brayley, T. Walsh
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    andrew.g.malis@verizon.com, 
                    lmartini@cisco.com, 
                    jeremy.brayley@ecitele.com, twalsh@juniper.net
        Pages:      5
        Characters: 10269
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pwe3-cell-transport-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4816.txt

The document describes a transparent cell transport service that
makes use of the "N-to-one" cell relay mode for Pseudowire Emulation
Edge-to-Edge (PWE3) Asynchronous Transfer-Mode (ATM) cell
encapsulation.  [STANDARDS TRACK]

This document is a product of the Pseudo Wire Emulation Edge to Edge
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



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



From pwe3-bounces@ietf.org Mon Feb 19 07:18:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJ7Ro-0001Hm-SR; Mon, 19 Feb 2007 07:16:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HIOT5-00035V-19
	for pwe3@ietf.org; Sat, 17 Feb 2007 07:15:07 -0500
Received: from ihemail4.lucent.com ([135.245.0.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HIOT0-0004pM-Jv
	for pwe3@ietf.org; Sat, 17 Feb 2007 07:15:07 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id l1HCEt8U017645
	for <pwe3@ietf.org>; Sat, 17 Feb 2007 06:15:00 -0600 (CST)
Received: from inexp02.in.lucent.com ([135.254.223.66]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 17 Feb 2007 06:14:55 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.20]) by
	inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 17 Feb 2007 17:43:21 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 17 Feb 2007 17:43:19 +0530
Message-ID: <CD7C9E0C08D4F84F86F17FC054A027E33E6474@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Regarding PW header's SeqNum field.
thread-index: AcdSjQLTYUzlSvB/SAiuFj8f6cN2kw==
From: "D, Ganesh \(Ganesh\)" <ganeshd@alcatel-lucent.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 17 Feb 2007 12:13:21.0557 (UTC)
	FILETIME=[04130450:01C7528D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
X-Mailman-Approved-At: Mon, 19 Feb 2007 07:16:47 -0500
Subject: [PWE3] Regarding PW header's SeqNum field.
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

 =20
Hello All,
=20
- The PW header's seq num is suppose to have sequence num of PW pkt's.On
the Egress side each pkt will have 16 bit seq num is incremented for
every pkt (  0 to 2^16 ).
- And on the Ingress side these pkts will be held in a buffer and the
seq num will help in reordering the pkt's if they got out of order while
traversing the PSN. And seq num will also help in abroving the PSN
jitter.
=20
Here is a situation observing am dealing with,
=20
- If the PWE solution should use the existing jitter buffer mechanism
already existing, then the pkt seq num should be converted to cell seq
num.
- The pkts contain cells. Lets say a PW is configured for
'CellConcatDepeth'. And let 'CellOffset' be the offset of the cell with
in this PW pkt ( first cell will have 'CellOffset' =3D 0, second cell =
will
have 'CellOffset' =3D 1, and so on till 'CellOffset' =3D
(CellConcatDepeth-1) ). =20
- Then the cell seq num can be easily calculated as 'cell seq num' =3D
(CellConcatDepth*PktSeqNum) + (CellOffset).
- But the problem is PW Pkt may contain number of cells less than
CellConcatDepth. In that case above formula will have holes in the
cellSeqNum.
- The above problem can be solved if, PW header contains cellSeqNum of
cell at CellOffset =3D ZERO ( let me call it cell0_seqNum ). Then 'cell
seq num' =3D  cell0_seqNum + CellOffset    .
=20
Can any body please tell me how can i carry this extra information? or
shall pkt seq num be replaced with cell0_seqNum ( but that's against the
draft ).
Can any body through some light at other way of solving this problem.
=20
Thanks in advance
Ganesh.D=20
=20

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



From pwe3-bounces@ietf.org Mon Feb 19 09:36:49 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJ9cv-0004CX-9B; Mon, 19 Feb 2007 09:36:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJ9ct-0004CN-8m
	for pwe3@ietf.org; Mon, 19 Feb 2007 09:36:23 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJ9cn-0004eu-4x
	for pwe3@ietf.org; Mon, 19 Feb 2007 09:36:23 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com
	[169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id
	l1JEQE9X004570; Mon, 19 Feb 2007 09:26:14 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com
	(uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA16542; 
	Mon, 19 Feb 2007 09:26:14 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service
	(5.5.2657.72) id <F1Z6CYN8>; Mon, 19 Feb 2007 09:26:13 -0500
Message-ID: <0BF76B30C100624BA997C9CED19D8125ECA32F@uspitsmsgusr08.pit.comms.marconi.com>
From: "Aanand, Siddharth" <Siddharth.Aanand@marconi.com>
To: "'D, Ganesh (Ganesh)'" <ganeshd@alcatel-lucent.com>, pwe3@ietf.org
Subject: RE: [PWE3] Regarding PW header's SeqNum field.
Date: Mon, 19 Feb 2007 09:26:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Ganesh,

I am not exactly sure why you need the cell sequence number but in any case
let us assume that you do, we know that a packet is either completely
delivered at the Egress PE or not. In that case can the egress PE not keep a
running count (on a per-flow basis) as it is extracting cells from the
concatenated packet?

Sidd

-----Original Message-----
From: D, Ganesh (Ganesh) [mailto:ganeshd@alcatel-lucent.com] 
Sent: Saturday, February 17, 2007 7:13 AM
To: pwe3@ietf.org
Subject: [PWE3] Regarding PW header's SeqNum field.

  
Hello All,
 
- The PW header's seq num is suppose to have sequence num of PW pkt's.On
the Egress side each pkt will have 16 bit seq num is incremented for
every pkt (  0 to 2^16 ).
- And on the Ingress side these pkts will be held in a buffer and the
seq num will help in reordering the pkt's if they got out of order while
traversing the PSN. And seq num will also help in abroving the PSN
jitter.
 
Here is a situation observing am dealing with,
 
- If the PWE solution should use the existing jitter buffer mechanism
already existing, then the pkt seq num should be converted to cell seq
num.
- The pkts contain cells. Lets say a PW is configured for
'CellConcatDepeth'. And let 'CellOffset' be the offset of the cell with
in this PW pkt ( first cell will have 'CellOffset' = 0, second cell will
have 'CellOffset' = 1, and so on till 'CellOffset' =
(CellConcatDepeth-1) ).  
- Then the cell seq num can be easily calculated as 'cell seq num' =
(CellConcatDepth*PktSeqNum) + (CellOffset).
- But the problem is PW Pkt may contain number of cells less than
CellConcatDepth. In that case above formula will have holes in the
cellSeqNum.
- The above problem can be solved if, PW header contains cellSeqNum of
cell at CellOffset = ZERO ( let me call it cell0_seqNum ). Then 'cell
seq num' =  cell0_seqNum + CellOffset    .
 
Can any body please tell me how can i carry this extra information? or
shall pkt seq num be replaced with cell0_seqNum ( but that's against the
draft ).
Can any body through some light at other way of solving this problem.
 
Thanks in advance
Ganesh.D 
 

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

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



From pwe3-bounces@ietf.org Mon Feb 19 10:25:00 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJANA-0002NE-En; Mon, 19 Feb 2007 10:24:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJAN8-0002N7-D7
	for pwe3@ietf.org; Mon, 19 Feb 2007 10:24:10 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJAN7-0005Iw-1v
	for pwe3@ietf.org; Mon, 19 Feb 2007 10:24:10 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-5.cisco.com with ESMTP; 19 Feb 2007 07:24:05 -0800
X-IronPort-AV: i="4.14,191,1170662400"; 
	d="scan'208"; a="390684782:sNHT2063187138"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l1JFO4WY017331; 
	Mon, 19 Feb 2007 07:24:04 -0800
Received: from [10.61.80.52] (ams3-vpn-dhcp4149.cisco.com [10.61.80.52])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l1JFO1Dk027924;
	Mon, 19 Feb 2007 07:24:02 -0800 (PST)
Message-ID: <45D9C10C.3060505@cisco.com>
Date: Mon, 19 Feb 2007 15:23:56 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Aanand, Siddharth" <Siddharth.Aanand@marconi.com>
Subject: Re: [PWE3] Regarding PW header's SeqNum field.
References: <0BF76B30C100624BA997C9CED19D8125ECA32F@uspitsmsgusr08.pit.comms.marconi.com>
In-Reply-To: <0BF76B30C100624BA997C9CED19D8125ECA32F@uspitsmsgusr08.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2704; t=1171898644;
	x=1172762644; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=stbryant@cisco.com;
	z=From:=20Stewart=20Bryant=20<stbryant@cisco.com>
	|Subject:=20Re=3A=20[PWE3]=20Regarding=20PW=20header's=20SeqNum=20field.
	|Sender:=20; bh=H1AjsgBAr2srf51FHYhQOCx+oCwDAJli1ClF1EuJC78=;
	b=2YlRow2fklmm/NjDi0uvFv+qvtATDHQ4POVv+Mzz/Z+MxMpinjYq+br6uVKgB6YH22hz7kJA
	HB++SmdLoZ0So7pzKYazuB9+ZPTJlqRL9VDOOIpjuF0vbPfIg6U4sbiW;
Authentication-Results: sj-dkim-2; header.From=stbryant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: pwe3@ietf.org, "'D, Ganesh \(Ganesh\)'" <ganeshd@alcatel-lucent.com>
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

This looks rather like a proprietry buffer management
design issue rather than a PWE3 protocol issue.

- Stewart

Aanand, Siddharth wrote:
> Ganesh,
> 
> I am not exactly sure why you need the cell sequence number but in any case
> let us assume that you do, we know that a packet is either completely
> delivered at the Egress PE or not. In that case can the egress PE not keep a
> running count (on a per-flow basis) as it is extracting cells from the
> concatenated packet?
> 
> Sidd
> 
> -----Original Message-----
> From: D, Ganesh (Ganesh) [mailto:ganeshd@alcatel-lucent.com] 
> Sent: Saturday, February 17, 2007 7:13 AM
> To: pwe3@ietf.org
> Subject: [PWE3] Regarding PW header's SeqNum field.
> 
>   
> Hello All,
>  
> - The PW header's seq num is suppose to have sequence num of PW pkt's.On
> the Egress side each pkt will have 16 bit seq num is incremented for
> every pkt (  0 to 2^16 ).
> - And on the Ingress side these pkts will be held in a buffer and the
> seq num will help in reordering the pkt's if they got out of order while
> traversing the PSN. And seq num will also help in abroving the PSN
> jitter.
>  
> Here is a situation observing am dealing with,
>  
> - If the PWE solution should use the existing jitter buffer mechanism
> already existing, then the pkt seq num should be converted to cell seq
> num.
> - The pkts contain cells. Lets say a PW is configured for
> 'CellConcatDepeth'. And let 'CellOffset' be the offset of the cell with
> in this PW pkt ( first cell will have 'CellOffset' = 0, second cell will
> have 'CellOffset' = 1, and so on till 'CellOffset' =
> (CellConcatDepeth-1) ).  
> - Then the cell seq num can be easily calculated as 'cell seq num' =
> (CellConcatDepth*PktSeqNum) + (CellOffset).
> - But the problem is PW Pkt may contain number of cells less than
> CellConcatDepth. In that case above formula will have holes in the
> cellSeqNum.
> - The above problem can be solved if, PW header contains cellSeqNum of
> cell at CellOffset = ZERO ( let me call it cell0_seqNum ). Then 'cell
> seq num' =  cell0_seqNum + CellOffset    .
>  
> Can any body please tell me how can i carry this extra information? or
> shall pkt seq num be replaced with cell0_seqNum ( but that's against the
> draft ).
> Can any body through some light at other way of solving this problem.
>  
> Thanks in advance
> Ganesh.D 
>  
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
> 

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



From pwe3-bounces@ietf.org Wed Feb 21 01:07:12 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJkc9-0004HV-42; Wed, 21 Feb 2007 01:06:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJkc7-0004HQ-1A
	for pwe3@ietf.org; Wed, 21 Feb 2007 01:06:03 -0500
Received: from ihemail1.lucent.com ([135.245.0.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJkc5-0002U5-ND
	for pwe3@ietf.org; Wed, 21 Feb 2007 01:06:02 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l1L661Fi010881
	for <pwe3@ietf.org>; Wed, 21 Feb 2007 00:06:01 -0600 (CST)
Received: from inexp02.in.lucent.com ([135.254.223.66]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 00:06:00 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.20]) by
	inexp02.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 11:35:57 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Feb 2007 11:35:56 +0530
Message-ID: <CD7C9E0C08D4F84F86F17FC054A027E33E6979@INEXC1U01.in.lucent.com>
In-Reply-To: <CD7C9E0C08D4F84F86F17FC054A027E3038EF4@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PWE3 Liberal Label Retention
thread-index: AcdVfH/Z0e3V9VzTQLKNswk9uZ3FyAAAc0eg
References: <CD7C9E0C08D4F84F86F17FC054A027E3038EF4@INEXC1U01.in.lucent.com>
From: "Adukuri, Pavan Kumar \(Pavan\)" <pavanka@alcatel-lucent.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 21 Feb 2007 06:05:57.0175 (UTC)
	FILETIME=[5A404470:01C7557E]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [PWE3] PWE3 Liberal Label Retention
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

=20
I am trying to understand the label retention Mode relevance in PWE3 FEC
signaling. RFC 4447 talks about liberal label retention. Can anybody
explain how it is used for PWE3s?

Thanks
Pavan

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



From pwe3-bounces@ietf.org Thu Feb 22 10:42:40 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKG4d-0000Eu-LP; Thu, 22 Feb 2007 10:41:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJkPN-0005Tx-Ns
	for pwe3@ietf.org; Wed, 21 Feb 2007 00:52:53 -0500
Received: from ihemail4.lucent.com ([135.245.0.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJkPK-0000Rd-Dd
	for pwe3@ietf.org; Wed, 21 Feb 2007 00:52:53 -0500
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id l1L5qj4D013650
	for <pwe3@ietf.org>; Tue, 20 Feb 2007 23:52:45 -0600 (CST)
Received: from inexp01.in.lucent.com ([135.254.223.65]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Feb 2007 23:52:45 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.20]) by
	inexp01.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 21 Feb 2007 11:22:41 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Feb 2007 11:22:41 +0530
Message-ID: <CD7C9E0C08D4F84F86F17FC054A027E33E6962@INEXC1U01.in.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PWE3 Liberal Label Retention
thread-index: AcdVfH/Z0e3V9VzTQLKNswk9uZ3FyA==
From: "Adukuri, Pavan Kumar \(Pavan\)" <pavanka@alcatel-lucent.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 21 Feb 2007 05:52:42.0087 (UTC)
	FILETIME=[80577770:01C7557C]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
X-Mailman-Approved-At: Thu, 22 Feb 2007 10:41:33 -0500
Subject: [PWE3] PWE3 Liberal Label Retention
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

I am trying to understand the label retention Mode relevance in PWE3 FEC
signaling. RFC 4447 talks about liberal label retention. Can anybody
explain how it is used for PWE3s?

Thanks
Pavan

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



From pwe3-bounces@ietf.org Fri Feb 23 01:41:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKU6c-00053Z-4d; Fri, 23 Feb 2007 01:40:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKU6a-00053L-1y
	for pwe3@ietf.org; Fri, 23 Feb 2007 01:40:32 -0500
Received: from mail.tataelxsi.co.in ([203.200.1.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKU6Y-0007Wq-Hw
	for pwe3@ietf.org; Fri, 23 Feb 2007 01:40:32 -0500
Received: from shailender (59.160.207.5.ill-bgl.static.vsnl.net.in
	[59.160.207.5] (may be forged))
	by mail.tataelxsi.co.in (MOS 3.8.3-GA)
	with ESMTP id CGK40337 (AUTH shailender);
	Fri, 23 Feb 2007 12:04:40 +0530 (IST)
From: Shailender Potharaju <shailender@tataelxsi.co.in>
To: "'Adukuri, Pavan Kumar \(Pavan\)'" <pavanka@alcatel-lucent.com>,
	<pwe3@ietf.org>
Subject: RE: [PWE3] PWE3 Liberal Label Retention
Date: Fri, 23 Feb 2007 12:02:47 +0530
Message-ID: <06fc01c75714$6fc59290$341a320a@telxsi.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
Importance: Normal
In-Reply-To: <CD7C9E0C08D4F84F86F17FC054A027E33E6962@INEXC1U01.in.lucent.com>
X-Junkmail-Status: score=10/50, host=mail.tataelxsi.co.in
X-Junkmail-SD-Raw: score=unknown,
	refid=str=0001.0A090206.45DE8B00.008C,ss=1,fgs=0,
	ip=59.160.207.5, so=2006-12-09 10:45:40,
	dmn=5.2.125/2007-01-26
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Hi,
According to RFC 4447, DU is must and liberal label retention should be used
for PWE3 signaling. As soon as a PW is configured on one end of PW, the
endpoint sends label mapping message to the peer. If the peer (PW is yet to
be configured on it) supports liberal retention mode, stores the received
label and binds it to the PW once it is configured.

Regards
Shailender

-----Original Message-----
From: Adukuri, Pavan Kumar (Pavan) [mailto:pavanka@alcatel-lucent.com]
Sent: Wednesday, February 21, 2007 11:23 AM
To: pwe3@ietf.org
Subject: [PWE3] PWE3 Liberal Label Retention


I am trying to understand the label retention Mode relevance in PWE3 FEC
signaling. RFC 4447 talks about liberal label retention. Can anybody
explain how it is used for PWE3s?

Thanks
Pavan

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


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



From pwe3-bounces@ietf.org Fri Feb 23 03:36:32 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HKVu3-0001qi-5w; Fri, 23 Feb 2007 03:35:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HKVu1-0001qO-N2
	for pwe3@ietf.org; Fri, 23 Feb 2007 03:35:41 -0500
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HKVtx-0002WT-8D
	for pwe3@ietf.org; Fri, 23 Feb 2007 03:35:41 -0500
Received: from gbmail02.netfr.alcatel.fr (gbmail02.netfr.alcatel.fr
	[155.132.251.26])
	by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id l1N8ZabG021215;
	Fri, 23 Feb 2007 09:35:36 +0100
To: pwe3@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OF95FFB75A.2A8EB56C-ON8025728B.002E5C71-8025728B.002F15B0@netfr.alcatel.fr>
From: Matthew.Bocci@alcatel-lucent.co.uk
Date: Fri, 23 Feb 2007 08:34:17 +0000
X-MIMETrack: Serialize by Router on GBMAIL02/GB/ALCATEL(Release 5.0.13aHF163 |
	June 23, 2005) at 02/23/2007 08:35:29
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: stbryant@cisco.com, danny@tcb.net
Subject: [PWE3] Prague meeting slots
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

Folks,

We have a 2 hour session for PWE3, tentatively scheduled for 15:20 on
Tuesday 20th March.

Please can you let me know if you would like a slot to present during the
meeting, by 6th March.

As usual, please include a brief summary of what you want to talk about, a
pointer to the draft (if any), and the time.

Best regards,

Matthew




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



From pwe3-bounces@ietf.org Mon Feb 26 18:39:57 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLpQk-00041h-4X; Mon, 26 Feb 2007 18:38:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HLpPv-0002n0-P1; Mon, 26 Feb 2007 18:38:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HLpPv-0005FX-5G; Mon, 26 Feb 2007 18:38:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 8D81D26E7A;
	Mon, 26 Feb 2007 23:38:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HLpPu-0008KL-FJ; Mon, 26 Feb 2007 18:38:02 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HLpPu-0008KL-FJ@stiedprstage1.ietf.org>
Date: Mon, 26 Feb 2007 18:38:02 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Internet Architecture Board <iab@iab.org>,
	pwe3 mailing list <pwe3@ietf.org>, pwe3 chair <pwe3-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [PWE3] Protocol Action: 'Wildcard Pseudowire Type' to Proposed 
 Standard 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

The IESG has approved the following document:

- 'Wildcard Pseudowire Type '
   <draft-ietf-pwe3-wildcard-pw-type-02.txt> as a Proposed Standard

This document is the product of the Pseudowire Emulation Edge to Edge 
Working Group. 

The IESG contact persons are Mark Townsley and Jari Arkko.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-wildcard-pw-type-02.txt

Technical Summary

Pseudowire signaling requires that the Pseudowire Type (PW Type) be
identical in both directions. For certain applications the
configuration of the PW Type is most easily accomplished by
configuring this information at just one PW endpoint. In any form of
LDP-based signaling, each PW endpoint must initiate the creation of a
unidirectional LSP. In order to allow the initiation of these two
LSPs to remain independent, a means of allowing the PW endpoint
lacking a priori knowledge of the PW Type to initiate the creation of
an LSP is needed. This document defines a Wildcard PW Type to
satisfy this need.

Working Group Summary

This document has been reviewed by the experts in the PWE3 WG. It
has been explicitly requested by the MFA that we expedite completion
as they need to reference it in their work.

Protocol Quality

This document was reviewed for the IESG by Mark Townsley.

Note to RFC Editor
 
Please make the reference to RFC3985 informative rather than normative.


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



From pwe3-bounces@ietf.org Tue Feb 27 08:24:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HM2J7-00068T-Le; Tue, 27 Feb 2007 08:23:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HM2J5-00064j-Um
	for pwe3@ietf.org; Tue, 27 Feb 2007 08:23:51 -0500
Received: from smtp.dataconnection.com ([192.91.191.4]
	helo=enfismtp1.datcon.co.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HM2J4-0005cL-KE
	for pwe3@ietf.org; Tue, 27 Feb 2007 08:23:51 -0500
Received: from enfimail2.datcon.co.uk ([172.19.14.250]) by
	enfismtp1.datcon.co.uk with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 27 Feb 2007 13:23:49 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Feb 2007 13:23:49 -0000
Message-ID: <8AC1AD08D396174DBC4E6D44EFACCFB101488CFA@enfimail2.datcon.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: pwID and pwe3-pw-mib-10 reverse mapping tables
Thread-Index: AcdacoREg2pi4rC9TaegOz7cpwYZ3Q==
From: "Ben Wright" <BenTWright@dataconnection.com>
To: <pwe3@ietf.org>
X-OriginalArrivalTime: 27 Feb 2007 13:23:49.0665 (UTC)
	FILETIME=[845A9910:01C75A72]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: Cisco - Thomas Nadeau <tnadeau@cisco.com>,
	Corrigent - David Zelig <Davidz@corrigent.com>,
	Gridpoint - Ken Young <KenY@gridpointsystems.com>
Subject: [PWE3] pwID and pwe3-pw-mib-10 reverse mapping tables
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

All,=20

I'd like to propose a minor modification to the pwID field in the =
pwTable. =20

For the reverse mappings provided by pwIndexMappingTable and =
pwPeerMappingTable, a unique pwID is required.  However, the description =
of pwID does not require uniqueness, and fixes pwID to zero for static =
PWs (where no pwID is signaled).  In practice this is restrictive for =
'manual' PWs, where these reverse mappings (particularly that provided =
by the pwPeerMappingTable) are still useful.

For the pwID change, I'd suggested the following text.  Does anyone have =
any comments on this new definition?  =20

Change from:
DESCRIPTION
  "Used in the outgoing PW ID field within the 'Virtual
  Circuit FEC Element'.
  Applicable if pwOwner equal 'pwIdFecSignaling' or
  'l2tpControlProtocol', otherwise it SHOULD be set to zero."
=20
Change to:
  "Pseudo Wire identifier.
=20
  If the pwOwner object is 'pwIdFecSignaling' or
  'l2tpControlProtocol', then this object is signaled in the
  outgoing PW ID field within the 'Virtual Circuit FEC
  Element'. For other values of pwOwner, this object is not
  signaled and it MAY be set to zero.
=20
  For implementations that support the pwIndexMappingTable,=20
  a non-zero value is RECOMMENDED, even if this
  identifier is not signaled.  This is so that reverse
  mappings can be provided by pwIndexMappingTable and
  pwPeerMappingTable.  It is therefore RECOMMENDED that the
  value of this pwID be unique (or if pwPeerAddrType is not
  'unknown', at least <pwType,pwID,pwPeerAddrType,pwPeerAddr>
  is unique.)"=20

Note that a similar issue exists for PWs that correspond to FEC 129, but =
the reverse mapping tables (as they stand) do not handle these FECs.  =20

Ben Wright


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



From pwe3-bounces@ietf.org Wed Feb 28 18:51:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMYYy-00019R-CE; Wed, 28 Feb 2007 18:50:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMYYe-000151-AO; Wed, 28 Feb 2007 18:50:04 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMYYd-0002iT-KR; Wed, 28 Feb 2007 18:50:04 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E91E726E5B;
	Wed, 28 Feb 2007 23:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HMYYc-000441-K4; Wed, 28 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HMYYc-000441-K4@stiedprstage1.ietf.org>
Date: Wed, 28 Feb 2007 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: pwe3@ietf.org
Subject: [PWE3] I-D ACTION:draft-ietf-pwe3-enet-mib-10.txt 
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pwe3>,
	<mailto:pwe3-request@ietf.org?subject=subscribe>
Errors-To: pwe3-bounces@ietf.org

--NextPart

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

	Title		: Ethernet Pseudo-Wire (PW) Management Information Base
	Author(s)	: D. Zelig, T. Nadeau
	Filename	: draft-ietf-pwe3-enet-mib-10.txt
	Pages		: 24
	Date		: 2007-2-28
	
This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   the Internet community.  In particular, it describes managed objects
   for modeling of Ethernet Pseudo-Wire (PW) services.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pwe3-enet-mib-10.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-enet-mib-10.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: <2007-2-28153900.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pwe3-enet-mib-10.txt

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

Content-Type: text/plain
Content-ID: <2007-2-28153900.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





