Re: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to MPLS Transport Profile Linear Protection) to Proposed Standard
"Adrian Farrel" <adrian@olddog.co.uk> Mon, 31 March 2014 20:16 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 D02DC1A6FBB; Mon, 31 Mar 2014 13:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.783
X-Spam-Level:
X-Spam-Status: No, score=-99.783 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, USER_IN_WHITELIST=-100] autolearn=no
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 5n0Wb7lmscCq; Mon, 31 Mar 2014 13:16:23 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 77A531A6FB4; Mon, 31 Mar 2014 13:16:23 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s2VKGJBU001708; Mon, 31 Mar 2014 21:16:19 +0100
Received: from 950129200 (13.17.90.92.rev.sfr.net [92.90.17.13]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s2VKGHej001693 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 31 Mar 2014 21:16:18 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Eric Osborne' <eric@notcom.com>
References: <08fb01cf4932$a0b51c50$e21f54f0$@olddog.co.uk> <CA+97oKNeKjAn5DmxTkFQPx6ifYeUaWYgMqUfT7EG=TH6yf48Nw@mail.gmail.com>
In-Reply-To: <CA+97oKNeKjAn5DmxTkFQPx6ifYeUaWYgMqUfT7EG=TH6yf48Nw@mail.gmail.com>
Date: Mon, 31 Mar 2014 21:16:17 +0100
Message-ID: <005101cf4d1e$13c74da0$3b55e8e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEtX0VsC3HbzAHU8DO//v8gDWm6EAIxxmwdnC3uDgA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20602.002
X-TM-AS-Result: No--33.671-10.0-31-10
X-imss-scan-details: No--33.671-10.0-31-10
X-TMASE-MatchedRID: EMyCvCfVN1Ezx9GDMr0HvzYTypjB3iDVuikHZcC6ceATVJPv0YKEKZiF 91oJeq4SC2LSbHrzHY02HZCtTkRx1Pd55AQ+b0rfuZH4LSX2+NW3dp6DuD+6wC62hjZS0WoYwqK BAza4rVvv7KQvOHjFKOQrukFcodKLkRgNtybE2t+jafQQYN4dhHH1PtMiCrmFRJWmeOMHa+Sqs5 KfY652zxgmeC7wGtsQ1DYVF1+wlwdCzHFhiypoVppWgCLYjjT9BdebOqawiLuB7hpizqoTJ/aox E42c1lDlZaHSIhaFDg3ePVDw45PxZj50ewQ/8wVy7TSWcbz49bKIQXG0L1M7Jy1Yc8tPkV9zcwT glIp/qOAl4UGeuDxkbBWFDUa0Cpgg3V8xGMW7vfKl4yJoI+fG5rTnsbMps30DO+DX+rUwfY30Ee Cx5K2K3WVib4qoeH9nzUT9qf9ruhroTn0jEcZf+QoIU4rAATMVNyVbFFiiaAz91mDYZLM5Q+7/Q uPSbIryf/0I/NH8I6WJcbpNaIEAPs6AFvEdeZfHPCema1j/6t9LQinZ4QefL6qvLNjDYTwzz3je hzeneyrusVRy4an8bxAi7jPoeEQftwZ3X11IV0=
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/4lCQKijftiV4rpSrE9GwJQrqg10
Cc: mpls@ietf.org, ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to MPLS Transport Profile Linear Protection) to Proposed Standard
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: <http://www.ietf.org/mail-archive/web/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, 31 Mar 2014 20:16:26 -0000
Thanks Eric, "reject the message" means send some form of error response? Or do you mean "drop the message" and "vigorously report it"? Thanks, Adrian > -----Original Message----- > From: Eric Osborne [mailto:eric@notcom.com] > Sent: 31 March 2014 20:09 > To: Adrian Farrel > Cc: ietf@ietf.org; mpls@ietf.org > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to > MPLS Transport Profile Linear Protection) to Proposed Standard > > Hello Adrian, WG- > > I propose this: > > Malformed TLV: reject the message and vigorously report it > Unknown TLV type: report the TLV, ignore the TLV and process the rest > of the message > > I'm open to other opinions, though. > > > > > eric > > On Wed, Mar 26, 2014 at 4:33 PM, Adrian Farrel <adrian@olddog.co.uk> wrote: > > Hi, > > > > I have one issue I want to bring up as a last call comment. I discussed it > > briefly with Eric and we agreed it is something that needs wider discussion than > > just a late editorial change. > > > > Currently 6378 does not describe the format of PSC TLVs and > > draft-ietf-mpls-tp-itu introduces one without defining the format tightly. > > Therefore, this document contains a simple statement of the fields and > meanings > > in a TLV. > > > > However, 6378 also does not state how to handle: > > - a malformed TLV > > - an unknown TLV type > > > > We need to add some simple text to cover this. > > > > Options for each of the above are: > > - ignore the TLV but process the message > > - report the TLV but ignore the TLV and process the message > > - ignore the message > > - report the message but ignore it > > - reject the message > > > > Thanks, > > Adrian > > > >> -----Original Message----- > >> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG > >> Sent: 26 March 2014 19:57 > >> To: IETF-Announce > >> Cc: mpls@ietf.org > >> Subject: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to > > MPLS > >> Transport Profile Linear Protection) to Proposed Standard > >> > >> > >> The IESG has received a request from the Multiprotocol Label Switching WG > >> (mpls) to consider the following document: > >> - 'Updates to MPLS Transport Profile Linear Protection' > >> <draft-ietf-mpls-psc-updates-03.txt> as Proposed Standard > >> > >> The IESG plans to make a decision in the next few weeks, and solicits > >> final comments on this action. Please send substantive comments to the > >> ietf@ietf.org mailing lists by 2014-04-09. Exceptionally, comments may be > >> sent to iesg@ietf.org instead. In either case, please retain the > >> beginning of the Subject line to allow automated sorting. > >> > >> Abstract > >> > >> This document contains four updates to the Protection State > >> Coordination (PSC) logic defined in RFC6378, "MPLS Transport Profile > >> (MPLS-TP) Linear Protection" . Two of the updates correct existing > >> behavior. The third clarifies a behavior which was not explained in > >> the RFC, and the fourth adds rules around handling capabilities > >> mismatches. > >> > >> > >> The file can be obtained via > >> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/ > >> > >> IESG discussion can be tracked via > >> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/ballot/ > >> > >> No IPR declarations have been submitted directly on this I-D. > >> > >> _______________________________________________ > >> mpls mailing list > >> mpls@ietf.org > >> https://www.ietf.org/mailman/listinfo/mpls > > > > _______________________________________________ > > mpls mailing list > > mpls@ietf.org > > https://www.ietf.org/mailman/listinfo/mpls
- [mpls] Last Call: <draft-ietf-mpls-psc-updates-03… The IESG
- Re: [mpls] Last Call: <draft-ietf-mpls-psc-update… Adrian Farrel
- Re: [mpls] Last Call: <draft-ietf-mpls-psc-update… Yaacov Weingarten
- Re: [mpls] Last Call: <draft-ietf-mpls-psc-update… Eric Osborne
- Re: [mpls] Last Call: <draft-ietf-mpls-psc-update… Eric Osborne
- Re: [mpls] Last Call: <draft-ietf-mpls-psc-update… Adrian Farrel