[mpls] FW: New Version Notification for draft-vainshtein-mpls-gal-tc-ttl-handling-02.txt

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 21 September 2015 11:40 UTC

Return-Path: <adrian@olddog.co.uk>
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 709401A0461 for <mpls@ietfa.amsl.com>; Mon, 21 Sep 2015 04:40:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, USER_IN_WHITELIST=-100] 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 ny3XXDGQHW1B for <mpls@ietfa.amsl.com>; Mon, 21 Sep 2015 04:40:43 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BE111A039A for <mpls@ietf.org>; Mon, 21 Sep 2015 04:40:42 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t8LBeepC026488 for <mpls@ietf.org>; Mon, 21 Sep 2015 12:40:40 +0100
Received: from 950129200 ([149.254.180.20]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id t8LBebGA026458 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <mpls@ietf.org>; Mon, 21 Sep 2015 12:40:39 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: mpls@ietf.org
References: <20150921112517.18785.11208.idtracker@ietfa.amsl.com>
In-Reply-To: <20150921112517.18785.11208.idtracker@ietfa.amsl.com>
Date: Mon, 21 Sep 2015 12:40:41 +0100
Message-ID: <00fe01d0f462$58ff67d0$0afe3770$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIxY4drm5Xcu1qR4OKpPeMFdhIIr52F/Fzg
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-8.0.0.1202-21828.007
X-TM-AS-Result: No--19.528-10.0-31-10
X-imss-scan-details: No--19.528-10.0-31-10
X-TMASE-MatchedRID: im+fhl6xvt3Of6FUr/HJkUg5Iem1vm3HnbR1KGab5Xkn+p552csI1Rch drJv3xSnBA19C356nKqA5llRhvVm5Rv4EaDquet2cFEiuPxHjsVMkOX0UoduuZfVFZyvCiMcFkm shPAJ67S3Og1E0dYhyywS3doODapmC61sZDZ0mT7YxkZC4pzxSFaOJcCxVHYrLLoMUXmFqmZJQ0 OQUGYtfTFxJ+DPhnFr8U8MeFCSDHKgH7Fpy5MrLZVRzPxemJL0h8Ytn75ClDP0NSuQztbtQ2KPA PFWHMoI4EXw14zmtrIj26BuB2jszUj7ejO32BAynVTWWiNp+v9BldmDYjwlpqMLUT/MIQivi5UV hdBCczIlGtUuqObGlzk2sxk9/brkMHsCEB6xhyMtMfCdg6KRDX0tCKdnhB581B0Hk1Q1KyKh5DO WGPdqWY2j49Ftap9EkGUtrowrXLg=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/AaJw1nChdWUFHNy00firwTrLNM4>
Subject: [mpls] FW: New Version Notification for draft-vainshtein-mpls-gal-tc-ttl-handling-02.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Mon, 21 Sep 2015 11:40:45 -0000

Hello working group,

Rather belatedly we have updated this draft.

We got a number of questions and comments on and off list coming from the MPLS-RT and concerned individuals.

We hope that this revision captures most of this, but we are aware that there are still some open issues and concerns that need to be discussed. Some of the worries are around whether:
- this makes deployed implementations non-conformant
  (it does not)
- this requires deployed implementations to be changed
  (it does not)
- this requires new implementations to be different from
  existing implementations
  (it does not)

What the document does is summarised at the end of section 1...

   In summary, the objective of this document is not to change the
   conformance requirements of existing implementations, but to enhance
   the likelihood of new implementations interoperating with each other
   and with implementations already in the field.  In particular, to
   improve the interoperability results where a new implementation
   interacts with a legacy implementation that may be sender or receiver
   of an LSE that contains the GAL and that may be any of:

   o  built with poor design considerations

   o  implemented with a misunderstanding of RFC 5586

   o  over-zealous in its policing of RFC 5586 behavior.

This leads to a debate over whether the I-D should target the Standards Track, or should be Informational and serve as guidelines. 

Thanks,
Adrian

> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: 21 September 2015 12:25
> To: Loa Andersson; Alexander Vainshtein; Adrian Farrel; Adrian Farrel; Sasha
> Vainshtein; Loa Andersson
> Subject: New Version Notification for draft-vainshtein-mpls-gal-tc-ttl-handling-
> 02.txt
> 
> 
> A new version of I-D, draft-vainshtein-mpls-gal-tc-ttl-handling-02.txt
> has been successfully submitted by Adrian Farrel and posted to the
> IETF repository.
> 
> Name:		draft-vainshtein-mpls-gal-tc-ttl-handling
> Revision:	02
> Title:		Handling the TC and TTL fields in a Label Stack Entry that Contains
> the Generic Associated Channel Label
> Document date:	2015-09-21
> Group:		mpls
> Pages:		7
> URL:            https://www.ietf.org/internet-drafts/draft-vainshtein-mpls-gal-tc-ttl-
> handling-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-vainshtein-mpls-gal-tc-ttl-
> handling/
> Htmlized:       https://tools.ietf.org/html/draft-vainshtein-mpls-gal-tc-ttl-handling-
> 02
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-vainshtein-mpls-gal-tc-ttl-
> handling-02
> 
> Abstract:
>    This document clarifies handling of the Traffic Class (TC) and Time-
>    to-Live (TTL) fields of a Label Stack Entry that contains the Generic
>    Associated Channel (G-ACh) Label (GAL).  These clarifications are
>    intended to aid interoperability of implementations.
> 
>    Original handling was defined in RFC 5586, and this document updates
>    that RFC.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat