Subject: [PWE3] FW: New Version Notification for draft-jc-pwe3-static-config-check-00.txt

From: Lizhong Jin<[email-masked]>
Date: Tue, 24 Jul 2012 11:25:11 +0800

Hi all,
Draft-jc-pwe3-static-config-check-00 is the updated version of 
draft-jc-pwe3-mpls-tp-static-checking-00 
(http://tools.ietf.org/html/draft-jc-pwe3-mpls-tp-static-checking-00) 
which had been presented at IETF83 Paris meeting.
After receiving the comments from the meeting and mailing list, we change 
the draft name, and the updates include:
1. Extending static PW checking for both MPLS-TP and Non-TP;
2. New Static PW FEC Element TLV is defined, instead of using Generalized 
ID FEC;
3. TX/RX Sequence number is used to ensure message delivery, instead of 
using local and remote PW element.
4. Control word configuration checking update;

Any more comments are appreciated. Thank you.

Regards
Lizhong

----- Forwarded by Lizhong Jin on 2012/07/24 11:16 -----

[email-masked] wrote 2012/07/06 11:55:41:

> 
> A new version of I-D, draft-jc-pwe3-static-config-check-00.txt
> has been successfully submitted by Lizhong Jin and posted to the
> IETF repository.
> 
> Filename:    draft-jc-pwe3-static-config-check
> Revision:    00
> Title:       Static pseudowire configuration checking using Generic 
> Associated Channel (G-ACh) Advertisement Protocol
> Creation date:    2012-07-06
> WG ID:       Individual Submission
> Number of pages: 10
> URL:             http://www.ietf.org/internet-drafts/draft-jc-pwe3-
> static-config-check-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-jc-pwe3-
> static-config-check
> Htmlized:        http://tools.ietf.org/html/draft-jc-pwe3-static-
> config-check-00
> 
> 
> Abstract:
>    This draft defines a method to verify the configuration parameters of
>    static pseudowires (PW).  Since a static PW can be independently
>    provisioned at each end of the PW there is a potential for a
>    configuration parameter mismatch and this can result in the PW not
>    being operational.  The procedures in this draft intend to solve this
>    problem and simplify the provisioning.
> 
>  
> 
> 
> The IETF Secretariat
>