headers
BOCCI Matthew | 2 Nov 2007 17:28
Picon

FW: Vancouver meeting slots


All,

Please can you send requests for a slot at the next PWE3 meeting to me by Monday 19th November.

Please also include a summary of what you want to talk about, and a pointer to the draft, if any.

Best regards,

Matthew 

_______________________________________________
pwe3 mailing list
pwe3 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
Permalink | Reply | 0 comments |
headers
Loa Andersson | 4 Nov 2007 21:08
Picon

The IETF t-mpls design team

The IAB has decided to appoint the following design team:

- Loa Andersson
- Matthew Bocci
- Deborah Brungard
- Stewart Bryant
- Ross Callon
- Dinesh Mohan
- Tom Nadeau
- Tom Walsh

to address issues in preparation of the potential cooperation
between IETF and ITU-T on protocols for t-mpls.

The design team will further discuss its charter and coordinate
it with IAB as necessary; a tentative design team is:

 o Identifying an action list for the IETF
 o Identifying incompatibles and inconsistencies between IETF
   and ITU-T documents
 o IETF decisions to be revisited
 o organization to take care of ITU-T mpls/pwe3 requirements

On behalf of the IAB

/Loa

--

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson <at> acreo.se
                                           loa <at> pi.se

This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com
Permalink | Reply | 0 comments |
headers
Sasha Vainshtein | 7 Nov 2007 06:47
Favicon

draft-ietf-pwe3-tdm-control-protocol-extensi-04: Summary issues raised during the WG LC

Hi all,
In the wake of the WG LC, Stewart and Carlos have sent their comments on the -04 version of the draft in question to the list.
No other comments have been received.
 
We've hold an off-the-list discussion of the issues raised that has helped to clarify the issues and  agree on their resolution
in the -05 version of the draft. A (rather long) summary of this discussion can be found below.
ISSUE: 
Mention MPLS in the title and abstract to match exclusion of L2TPv3.
PROPOSED RESOLUTION:
Accepted.
New title:
Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks
New abstract:
This document defines extension to the PWE3 control protocol [RFC4447]
 and PWE3 IANA allocations [RFC4446] required for setup of 
 TDM pseudo wires in MPLS networks.
ISSUE:
Usage of the PW Status messages for carrying the status of Attachment Circuits of TDM PWs is NOT RECOMMENDED. This may end in conflict with known proposals to use these messages for PW protection.
PROPOSED RESOLUTION:
Leave the text "as is".
AUTHORS' REASONING:
The status of the ACs is adequately carried across the PSN by the flags in the TDM PW Control Word. Having two different mechanisms to carry this across can only result in racing.
At the same time, the PW protection mechanisms proposed in draft-muley-dutta-pwe3-redundancy-bit-01.txt and/ or draft-muley-pwe3-redundancy-01.txt require some dual-homing protocol on Attachment Circuits. There is no such protocol for TDM ACs.
ISSUE:
TDM PW type values are explicitly listed in the text in spite of being already listed in the appropriate IANA registry. Looks like an opportunity for errors.
PROPOSED RESOLUTION:
Leave the text "as is".
AUTHORS' REASONING:
Simplifies reading of the document by the implementers. And the check vs. the registry must be only done once.
ISSUE:
CEP/TDM Payload Bytes parameter is described as being used with all SAToP and CESoPSN PWs. Suggestion to say "for all except TDMoIP".
 
PROPOSED RESOLUTION:
Leave the text "as is".
AUTHORS' REASONING:
There are two different TDMoIP PW types; and positive thinking looks preferable to the authors.
ISSUE:
Presence of some interface parameters is defined as OPTIONAL, and default values of these parameters (as defined in the appropriate encapsulation documents) must be assumed if they are omitted. While this definitely would work, it looks like more complicated code vs. less bytes sent during setup...
PROPOSED RESOLUTION:
Leave the text "as is".
AUTHORS' REASONING:
  1. This is compatible with the existing implementations and with the approved MFA 8.0.0 IA.
  2. The PE that sends the PW label mapping message is not prevented from including all the interface parameters, so there is no additional complexity here. The PE that receives this message can initialize all the interface parameters to defaults and then update them from the actual values found in the received message (that you do not find there, you do not update). This looks as a healthy approach in any case and at least as simple as checking for presence of all the parameters. 
ISSUE:
A clearer way to say that "a TDM PW encapsulation MUST either use or not use RTP in both directions" is required.
PROPOSED RESOLUTION:
Accepted.
 
Alternative text:

Use or non-use of RTP MUST match in the two directions.

ISSUE:
Add a reference to RFC 4446 in the Security Considerations section to say that it is the same
 
PROPOSED RESOLUTION:
Accepted. But it probably should 4447.
Modified text:
This draft does not have any additional impact on security of PWs above
 that of basic LDP setup of PWs as defined in [RFC4447].
ISSUE:
Add (and use) an Informative Reference to draft-ietf-l2tpext-tdm-xx
PROPOSED RESOLUTION:
Leave the references "as is" in this draft, but include a reference to this draft in draft-ietf-l2tpext-tdm-xx
ISSUE:
If possible, explain the reasons for skipping some values in the enumerations for such parameters as  TDMoIP AAL1 mode and TDMoIP AAL2 Option.  
PROPOSED RESOLUTION:
Leave "as is" (no special reasons, this is how it has been implemented).
ISSUE:
Is it the need to specify AAL2 encoding types and, in the case of G.711 encoding, A-law or mu-law?
PROPOSED RESOLUTION:
No need to specify A-law or mu-law, and specific encoding are out of scope; the two sides MUST  agree on them.
Modified text:
Encoding specifies native signal processing performed on the payload. When no native signal processing is performed (i.e. G.711 encoding) this field MUST be zero. Other specific values that can be used in this field are beyond the scope of this specification, but the two directions MUST match for the PW setup to succeed.
ISSUE:
Different names for different unused/reserved bit fields in the TDM Options structure (F and X). One name would suffice.
PROPOSED RESOLUTION:
Leave the text "as is".  It is convenient for some implementations to treat these fields differently.
ISSUE:
The suggested Interface Parameter ID value for AAL1 options overlaps with a value already assigned in the IANA registry.
PROPOSED RESOLUTION:
Shift the suggested Interface Parameter ID values for AAL1 and AAL2 options to avoid the overlap.
ISSUE:
Length of some of the new Interface Parameters has not been defined.
PROPOSED RESOLUTION:
Add a new sub-section at the beginning of Section 3 listing all the relevant Interface Parameters with their IDs (assigned or suggested) and length. Remove the IDs from the sections describing the syntax and semantics of these parameters.
 
The -05 version of the draft that resolves all these issues and fixes a couple of typos will be submitted to the IETF later today.
Meanwhile it can be found at:
 
 
Regards,
              Yaakov and Sasha
 
_______________________________________________
pwe3 mailing list
pwe3 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
Permalink | Reply | 0 comments |
headers
IETF I-D Submission Tool | 7 Nov 2007 11:56
Picon
Favicon

New Version Notification for draft-ietf-pwe3-tdm-control-protocol-extensi-05


A new version of I-D, draft-ietf-pwe3-tdm-control-protocol-extensi-05.txt has been successfuly
submitted by Sasha Vainshtein and posted to the IETF repository.

Filename:	 draft-ietf-pwe3-tdm-control-protocol-extensi
Revision:	 05
Title:		 Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks
Creation_date:	 2007-11-07
WG ID:		 pwe3
Number_of_pages: 13

Abstract:
This document defines extension to the PWE3 control protocol [RFC4447] 
 and PWE3 IANA allocations [RFC4446] required for setup of TDM 
 pseudowires in MPLS networks. 

  Vainshtein and Stein
 Standards Track

[page 1]

 Control Protocol Extensions for TDM Pseudo wires November 2007

The IETF Secretariat.
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 7 Nov 2007 12:00
Picon
Favicon

I-D Action:draft-ietf-pwe3-tdm-control-protocol-extensi-05.txt

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           : Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks
	Author(s)       : S. Vainshtein, Y. Stein
	Filename        : draft-ietf-pwe3-tdm-control-protocol-extensi-05.txt
	Pages           : 13
	Date            : 2007-11-07

This document defines extension to the PWE3 control protocol [RFC4447] 
 and PWE3 IANA allocations [RFC4446] required for setup of TDM 
 pseudowires in MPLS networks. 

  Vainshtein and Stein
 Standards Track

[page 1]

 Control Protocol Extensions for TDM Pseudo wires November 2007

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> 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-control-protocol-extensi-05.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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-tdm-control-protocol-extensi-05.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.
Attachment: message/external-body, 158 bytes
Attachment (draft-ietf-pwe3-tdm-control-protocol-extensi-05.txt): message/external-body, 71 bytes
_______________________________________________
pwe3 mailing list
pwe3 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
Permalink | Reply | 0 comments |
headers
Loa Andersson | 9 Nov 2007 10:02
Picon

Re: The IETF t-mpls design team

All,

I made one mistake in listing the dt-members,

- Mark Townsley is also on the team.

Apologies for this.

/Loa

Loa Andersson wrote:
> The IAB has decided to appoint the following design team:
> 
> - Loa Andersson
> - Matthew Bocci
> - Deborah Brungard
> - Stewart Bryant
> - Ross Callon
> - Dinesh Mohan
> - Tom Nadeau
> - Tom Walsh
> 
> to address issues in preparation of the potential cooperation
> between IETF and ITU-T on protocols for t-mpls.
> 
> The design team will further discuss its charter and coordinate
> it with IAB as necessary; a tentative design team is:
> 
>  o Identifying an action list for the IETF
>  o Identifying incompatibles and inconsistencies between IETF
>    and ITU-T documents
>  o IETF decisions to be revisited
>  o organization to take care of ITU-T mpls/pwe3 requirements
> 
> 
> On behalf of the IAB
> 
> /Loa
> 
> 

--

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson <at> acreo.se
                                           loa <at> pi.se

This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com
Permalink | Reply | 0 comments |
headers
IETF I-D Submission Tool | 9 Nov 2007 20:26
Picon
Favicon

New Version Notification for draft-ietf-pwe3-vccv-bfd-00


A new version of I-D, draft-ietf-pwe3-vccv-bfd-00.txt has been successfuly submitted by Carlos
Pignataro and posted to the IETF repository.

Filename:	 draft-ietf-pwe3-vccv-bfd
Revision:	 00
Title:		 Bi-directional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity
Verification (VCCV)
Creation_date:	 2007-11-09
WG ID:		 pwe3
Number_of_pages: 12

Abstract:
This document describes new Connectivity Verification (CV) types for
using Bi-directional Forwarding Detection (BFD) with Virtual Circuit
Connectivity Verification (VCCV).  VCCV provides a control channel
that is associated with a Pseudowire (PW), as well as the
corresponding operations and management functions such as
connectivity verification to be used over that control channel.

The IETF Secretariat.
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 9 Nov 2007 20:30
Picon
Favicon

I-D Action:draft-ietf-pwe3-vccv-bfd-00.txt

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           : Bi-directional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity
Verification (VCCV)
	Author(s)       : T. Nadeau, C. Pignataro
	Filename        : draft-ietf-pwe3-vccv-bfd-00.txt
	Pages           : 12
	Date            : 2007-11-09

This document describes new Connectivity Verification (CV) types for
using Bi-directional Forwarding Detection (BFD) with Virtual Circuit
Connectivity Verification (VCCV).  VCCV provides a control channel
that is associated with a Pseudowire (PW), as well as the
corresponding operations and management functions such as
connectivity verification to be used over that control channel.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> 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-vccv-bfd-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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-vccv-bfd-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.
Attachment: message/external-body, 138 bytes
Attachment (draft-ietf-pwe3-vccv-bfd-00.txt): message/external-body, 71 bytes
_______________________________________________
pwe3 mailing list
pwe3 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
Permalink | Reply | 0 comments |
headers
IETF I-D Submission Tool | 14 Nov 2007 06:16
Picon
Favicon

New Version Notification for draft-ietf-pwe3-tdm-control-protocol-extensi-06


A new version of I-D, draft-ietf-pwe3-tdm-control-protocol-extensi-06.txt has been successfuly
submitted by Sasha Vainshtein and posted to the IETF repository.

Filename:	 draft-ietf-pwe3-tdm-control-protocol-extensi
Revision:	 06
Title:		 Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks
Creation_date:	 2007-11-13
WG ID:		 pwe3
Number_of_pages: 13

Abstract:
This document defines extension to the PWE3 control protocol [RFC4447] 
 and PWE3 IANA allocations [RFC4446] required for setup of TDM 
 pseudowires in MPLS networks. 

  Vainshtein and Stein
 Standards Track

[page 1]

 Control Protocol Extensions for TDM Pseudo wires November 2007

The IETF Secretariat.
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 14 Nov 2007 06:20
Picon
Favicon

I-D Action:draft-ietf-pwe3-tdm-control-protocol-extensi-06.txt

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           : Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks
	Author(s)       : S. Vainshtein, Y. Stein
	Filename        : draft-ietf-pwe3-tdm-control-protocol-extensi-06.txt
	Pages           : 13
	Date            : 2007-11-14

This document defines extension to the PWE3 control protocol [RFC4447] 
 and PWE3 IANA allocations [RFC4446] required for setup of TDM 
 pseudowires in MPLS networks. 

  Vainshtein and Stein
 Standards Track

[page 1]

 Control Protocol Extensions for TDM Pseudo wires November 2007

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> 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-control-protocol-extensi-06.txt".

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

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

Send a message to:
	mailserv <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pwe3-tdm-control-protocol-extensi-06.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment: message/external-body, 158 bytes
Attachment (draft-ietf-pwe3-tdm-control-protocol-extensi-06.txt): message/external-body, 71 bytes
_______________________________________________
pwe3 mailing list
pwe3 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3
Permalink | Reply | 0 comments |

Gmane