Re: [mpls]

Alexander Vainshtein <> Sat, 06 February 2016 17:05 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 5AB391A3B9D; Sat, 6 Feb 2016 09:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z_x-yqglewMd; Sat, 6 Feb 2016 09:05:48 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:fe04::774]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4EF571A21C2; Sat, 6 Feb 2016 09:05:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-ecitele-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MwGkyH/J4/+K4Dd5f4pcSZf8WbLyBTjJUCOVLOlmisc=; b=l+5yFcGQRm4oZ9H8p8C2jL16nPFH/bujwzouYTlKespdLTLj4dEGjDrdjKiQsxsUFO/n3gyLy3nGn6LyJ+/C7jVv/7kISx6zgp9aSix4de5bu8BxsLbHLQOks+CXAfolcvKhBZjKhi1I/Eob/Oj+znYxTf+BGuWRfQk+uLyR8bY=
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.396.15; Sat, 6 Feb 2016 17:05:31 +0000
Received: from ([]) by ([]) with mapi id 15.01.0396.020; Sat, 6 Feb 2016 17:05:31 +0000
From: Alexander Vainshtein <>
To: Huub van Helvoort <>
Thread-Topic: [mpls]
Thread-Index: AQHRYQCVYzI7ELxLYUmgc17D6Ipc8A==
Date: Sat, 06 Feb 2016 17:05:31 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-mailer: Infraware POLARIS Mobile Mailer v2.5
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; DB3PR03MB0777; 5:TQ9XZSq5GifFt2ZRBFAMzjvUDBguetIgPRRks8X3AYwPISGq98KseSmfKXiV/9eg0NUXa5SN9FmEBayZlJdOJN9VUYjTqcYu21Aq/0gZz5ba1AITbpQGotkB0QPmiZcrUqU5CAaM8n3iXm8O/5WIig==; 24:GFGfwGtmA0ekLeJwbOwr4ddmcdYivxuTNj4r7GjqoTZU+gC2K2J8g7BFRXzyxgtdyGe2Ex/II7AtpzH6xHmcgas2CNxfPa0Lhry5cZqkCkA=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR03MB0777;
x-ms-office365-filtering-correlation-id: ef348fdf-ec31-4b99-9844-08d32f17b86d
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DB3PR03MB0777; BCL:0; PCL:0; RULEID:; SRVR:DB3PR03MB0777;
x-forefront-prvs: 08444C7C87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(479174004)(377454003)(377424004)(69234005)(13464003)(24454002)(51914003)(19580395003)(1220700001)(15975445007)(19580405001)(1096002)(50986999)(19617315012)(10400500002)(76576001)(4326007)(106116001)(50226001)(5008740100001)(3900700001)(77096005)(2900100001)(11100500001)(586003)(86362001)(87936001)(6116002)(1411001)(189998001)(40100003)(5001960100002)(110136002)(5002640100001)(5004730100002)(33656002)(74316001)(16236675004)(102836003)(66066001)(2906002)(3280700002)(3846002)(122556002)(5003600100002)(3660700001)(92566002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR03MB0777;; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB3PR03MB07809A3CCB690ACD6F77CE6D9DD30DB3PR03MB0780eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2016 17:05:31.3377 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR03MB0777
Archived-At: <>
Cc: "" <>, "" <>
Subject: Re: [mpls]
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 06 Feb 2016 17:05:55 -0000

Hi Huub,

Lots of thanks for the clarification.

Regards and a nice weekend to you.

Thumb typed on my LG,

------ Original message ------
From: Huub van Helvoort
Date: 06/02/2016 15:24
To: Alexander Vainshtein;
Cc:;Loa Andersson;Scott Mansfield;;
Subject:Re: [mpls]

Hello Sasha,

The amendment is to align G.8131 with the published RFCc. So it is following work in the IETF.

Have a nice weekend, Huub.

sent from Huawei Nexus

On 6 Feb 2016 2:16 p.m., "Alexander Vainshtein" <<>> wrote:


Lots of thanks for a prompt response and for a catched typo.

In any case, does the proposed Amendment imply that IETF has to do something about tgese RFCs as wekl to keep everything in sync?

Regards, and lots of thamks in advance,


Thumb typed on my LG,

------ Original message ------
From: Huub van Helvoort
Date: 05/02/2016 13:55
To: Alexander Vainshtein;Loa Andersson;Scott Mansfield;
Subject:Re: [mpls]

Hello Sasha,

You are probably referring to G.8131.

FYI: G.8131 is based on and in line with the RFCs you mention.
G.8131 was published after these RFC were published, there were
liaisons exchanged to align the progress of this work.

Best regards, Huub.

> Loa. Scott and all,
> One of the documents mentioned in the liaison deals with revision  of an ITU-T G.8113 that deals with linear protection of MPLS-TP LSPs.
> This issue has some history in the MPLS WG:
> 1. IETF has published RFC 6378 as a Proposed Standard
> 2. Some  serious technical issues have been then found with this document, and as a consequence, RFC 7324 has been published (also as P) to fix these issues
> 3.In addition, RFC 7121 has been published to describe an alternative solution to RFC 6378  to make linear protection of LPs to macth expectations of the Telecom operators; this is also a PS document.
> And, in addition, ITU-T has published G.8113 that also deals with linear protection of MPLS-TP LSPs.
> Having so  many documents dealing with the same issue looks problematic tome in any case. And since ITU-T now plans to approve revisions to its own standard pertaining to linear protection of LSPs, it makes sense to ask for some clarifications, mainly if a revision process of, say. 7121 should be initiated to mact the changes in G.8113.
> My 2c,
> Sasha
> ________________________________________
> From: mpls <<>> on behalf of Loa Andersson <<>>
> Sent: Friday, February 5, 2016 5:32 AM
> To: Scott Mansfield;<>;<>
> Subject: Re: [mpls]
> Scott,
> So maybe just a short response.
> "Thanks for your liaison on the final approval of the MPLS-TP
> Recommendations, this marks a step in the joint MPLS-TP project.
> IETF have to date published 45 MPLS-TP RFC from 7 working groups and
> independent document. IETF still have 11 active Internet Drafts.
> We are looking forward to your support completing the MPLS-TP
> project."
> I think you can correct grammar and spelling and send it timely.
> Working Group,
> Please comment on this?
> /Loa
> On 2016-02-04 21:13, Scott Mansfield wrote:
>> I'm willing to help, but I don’t see anything here worth commenting on, unless there is a burning desire to make comments now.  None of the documents liaised have changed dramatically since early 2014.
>> -scott.
>> -----Original Message-----
>> From: Loa Andersson []
>> Sent: Thursday, February 04, 2016 5:58 AM
>> To:<>;<>; Scott Mansfield
>> Subject:
>> Working Group,
>> We have a liaison from SG15 that we need to decide on how to respond to
>> I've asked Scott to help us coordinate this.
>> Any comments are welcome.
>> /Loa
>> mpls wg co-chair