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

Huub van Helvoort <huubatwork@gmail.com> Sat, 06 February 2016 13:24 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 A568D1B2CF5; Sat, 6 Feb 2016 05:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 r_lE4_ciMbOn; Sat, 6 Feb 2016 05:24:39 -0800 (PST)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 5F9A91ACD57; Sat, 6 Feb 2016 05:24:39 -0800 (PST)
Received: by mail-ig0-x231.google.com with SMTP id 5so31732448igt.0; Sat, 06 Feb 2016 05:24:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=h9U0GdVgfFrKK74XttYi1CTXEaGDmxq+VkUEQnwHSlA=; b=V/dm5Kd9CfqVCR0/0m7hHcGimHu8OU5VAdwEvFuN7vgkmbd8p3NoHHzEDbmyu1ED2Q VZcvAG/CBsD9raZIOO70WbMF0DTowW4tj8lDvF1RpY0VGuQe7M2DeC66kk81sk+rTMK/ EyRMuF/2sOKinx5cuskRgNNVhivJTCaoJ3a4JujTV69dUGmMdx110RY7JNoCiEKa/cDj MUyenbIhG3yVX4NaZLGDscNnK6TZMaSEpQ5cY6fWS3W3cNY6ZCHs4vcbU4Y3fnk2YNIk 2W5a1uy90FJgewkqqtoJW+yJb4L1V4so47Efc6wxUVjyoWbNC9yqxyFCYEe4i34loUMQ V+/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=h9U0GdVgfFrKK74XttYi1CTXEaGDmxq+VkUEQnwHSlA=; b=hWRXgVzyWOyOb4RYx9hKL0tVYtEp6+J1fVAtBK0XsnUZGCpy+VEVZZ7ZU7otJPwr1J 2tXZ6dgsSwxcOk7G1CUx6vOLdVOrYB+Us7CBvTGEGBJ/0UZMzgI788SrNtd+kK11+8h5 6hT+jKp6MnLurqgSSxPamMLJwKoTVc0y+ORq4hddjXo3tHQhb2KcTO0mEfVl1f2biayF MWyyre6wiuNkypLFERpN+Z3uDPdbb52jP7pl69UisUiJg5rJy03G3B+szbIjLZnuj/6W 89AusOoAv+MqocGxdDzQdGF76HH+uWgA08xuWE9WNhMwTLgp/R8oMnDcZJIQdocbq7gU z1bA==
X-Gm-Message-State: AG10YOT0jHS8OaXy+YhKUlCpcyjUzh2S0SZWBaer+TlG13CJFpj9CO4FUl3qczr+ncgZbM7GUPe8xOYBJh+3LQ==
MIME-Version: 1.0
X-Received: by 10.50.79.136 with SMTP id j8mr3241387igx.54.1454765078865; Sat, 06 Feb 2016 05:24:38 -0800 (PST)
Received: by 10.107.57.5 with HTTP; Sat, 6 Feb 2016 05:24:38 -0800 (PST)
Received: by 10.107.57.5 with HTTP; Sat, 6 Feb 2016 05:24:38 -0800 (PST)
In-Reply-To: <DB3PR03MB0780C3EE9C1EEA7E0ECC829A9DD30@DB3PR03MB0780.eurprd03.prod.outlook.com>
References: <DB3PR03MB0780C3EE9C1EEA7E0ECC829A9DD30@DB3PR03MB0780.eurprd03.prod.outlook.com>
Date: Sat, 6 Feb 2016 14:24:38 +0100
Message-ID: <CAHOc_FTrF_hNbjMmWyQ-XBfPK1mo7wLfYQHDz1ag0tkyneeYFw@mail.gmail.com>
From: Huub van Helvoort <huubatwork@gmail.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Content-Type: multipart/alternative; boundary=089e013a110ac1ec0c052b19e375
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/n8FE1RxQr5y2vN0tT_QNOYgoWGM>
Cc: 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
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: Sat, 06 Feb 2016 13:24:41 -0000

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" <
Alexander.Vainshtein@ecitele.com> wrote:

> Huub,
>
> 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,
>
> Sasha
>
>
>
>
> Thumb typed on my LG,
> Sasha
>
> ------ Original message ------
> *From: *Huub van Helvoort
> *Date: *05/02/2016 13:55
> *To: *Alexander Vainshtein;Loa Andersson;Scott Mansfield;
> *Cc: *mpls@ietf.org;mpls-chairs@ietf.org;
> *Subject:*Re: [mpls] https://datatracker.ietf.org/liaison/1435/
>
> 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 <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
> >>
>
>