Re: [mpls] https://datatracker.ietf.org/liaison/1435/

Huub van Helvoort <huubatwork@gmail.com> Fri, 05 February 2016 11:55 UTC

Return-Path: <huubatwork@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6045D1B3752; Fri, 5 Feb 2016 03:55:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gss3or-aFjaG; Fri, 5 Feb 2016 03:55:42 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E6801B3751; Fri, 5 Feb 2016 03:55:42 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id g62so44834382wme.0; Fri, 05 Feb 2016 03:55:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=xh4Xe28GB7oN55bhV/qdGpyr+zU5/qLZt6bNAljOt5Q=; b=hEupiOhxolmS8bQH3NnmpOJpgFSLurXCMohU5AjnjI/LgjXPIJjzyAEwSCZVHTAYrZ K7c5OXFo/Y9bWK3wvWZCatg5rFEfbHDGOWFWJfpcPw4UieuBYrNxx0pcSiHNE/q0EaOY rFhBx+SX5R5hxULZjzWXncFgtOXXgtt1/HVNLmK3/Sr2L5czDKjQHYGJO4uk81d/529B 8RIT/QFZLk2PQJBMkMQNayxJBOGX4OTSHzLljtXTDdnw0of66NZvBZvz+1nzDH1HOTQs P3ggdbv8E3cxAZ8Nkoqf0WEPMhm4Ven7jHFY+N8iu0UVHcU+DccC2sJQoNXFOd6LoRiv nHmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=xh4Xe28GB7oN55bhV/qdGpyr+zU5/qLZt6bNAljOt5Q=; b=AOybdjcby4CP5u5v291L9p2QKjHHGsFzCsSFLmnyzCPger90024zGjugYfEOLw6pKn MH27LUl3EOe1I5B/J7hijU+jD6+4TA4SLgNV0T/BGtZOv4b3i54CGPpvqaskkvYBBwIk 4fbzs7byKtqkF9maAiXXWXmHgnKRb7NZlAIUuZE9GQy/gpmGLriqh+oYYSKuhFz7h+rM V46w77az/NoodnOVEi7V1A9p0U02R8TkDpYUjMATL40VrsWDO1wVw9Y1x9O938i+g091 2B66BuKDkiuE7P/C53LMqAHfTLP8cNzaPuAICczbssPqzN4+H0WMX+LNzbUs9wV0LFlk MZDw==
X-Gm-Message-State: AG10YOTwvI6FFr9pLgAV4lZo1iEAPXhNPWjFLs96hRq/j5AxrnYb/lRY/vz30DiQftB+Iw==
X-Received: by 10.194.133.10 with SMTP id oy10mr12980482wjb.93.1454673341039; Fri, 05 Feb 2016 03:55:41 -0800 (PST)
Received: from McAsterix.local ([92.109.37.136]) by smtp.gmail.com with ESMTPSA id k130sm17099028wmg.6.2016.02.05.03.55.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Feb 2016 03:55:40 -0800 (PST)
Message-ID: <56B48DBB.8050008@gmail.com>
Date: Fri, 05 Feb 2016 12:55:39 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, Loa Andersson <loa@pi.nu>, Scott Mansfield <scott.mansfield@ericsson.com>
References: <56B32ED2.7020103@pi.nu> <EF35EE4B92789843B1DECBC0E24558644BE3D966@eusaamb105.ericsson.se>, <56B417DB.10905@pi.nu> <DB3PR03MB0780F11C5FD4F28D9978E7C19DD20@DB3PR03MB0780.eurprd03.prod.outlook.com>
In-Reply-To: <DB3PR03MB0780F11C5FD4F28D9978E7C19DD20@DB3PR03MB0780.eurprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/fm7et01QeQdFt8tjHdEVMIr-G7Y>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Subject: Re: [mpls] https://datatracker.ietf.org/liaison/1435/
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 11:55:46 -0000

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 <mpls-bounces@ietf.org> on behalf of Loa Andersson <loa@pi.nu>
> Sent: Friday, February 5, 2016 5:32 AM
> To: Scott Mansfield; mpls@ietf.org; mpls-chairs@ietf.org
> Subject: Re: [mpls] https://datatracker.ietf.org/liaison/1435/
>
> 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 [mailto:loa@pi.nu]
>> Sent: Thursday, February 04, 2016 5:58 AM
>> To: mpls@ietf.org; mpls-chairs@ietf.org; Scott Mansfield
>> Subject: https://datatracker.ietf.org/liaison/1435/
>>
>> Working Group,
>>
>> We have a liaison from SG15 that we need to decide on how to respond to https://datatracker.ietf.org/liaison/1435/
>> I've asked Scott to help us coordinate this.
>> Any comments are welcome.
>>
>> /Loa
>> mpls wg co-chair
>>