Re: [mpls] Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS and COMMENT)
"Adrian Farrel" <adrian@olddog.co.uk> Sun, 23 November 2014 07:07 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 310D91A1AEE; Sat, 22 Nov 2014 23:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 4yafjjiuYc_m; Sat, 22 Nov 2014 23:07:42 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EE3A1A1AEA; Sat, 22 Nov 2014 23:07:42 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAN77dQg015680; Sun, 23 Nov 2014 07:07:39 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id sAN77cK4015666 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 23 Nov 2014 07:07:38 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Barry Leiba' <barryleiba@computer.org>
References: <20141123064914.2745.26911.idtracker@ietfa.amsl.com>
In-Reply-To: <20141123064914.2745.26911.idtracker@ietfa.amsl.com>
Date: Sun, 23 Nov 2014 07:07:37 -0000
Message-ID: <058901d006ec$2add7770$80986650$@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: AQJTbQVFvXpqMxRLlvUwCRwsl33h0ptm+pjw
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21122.005
X-TM-AS-Result: No--12.882-10.0-31-10
X-imss-scan-details: No--12.882-10.0-31-10
X-TMASE-MatchedRID: WMT2WRIkHPO31G6CKdUG1WOho7buv7d9GSqdEmeD/nVF+YXPIqAdvvbU hPv66jYYCFf9mAstC7MqUWENz2/knnfP3OQRnpC38jbzfqNu/QQrHkgIan9a0TdeVVUZfQ6RGJp b/R8vyp5NYvDaO9t+nFxBgG7mg/DlfPmUQQG69pwWGNJh59eVbGlOPrrbBmagDO+DX+rUwfYsdh 2ZEFy7YUNoVDYC2mKV9jjbGUN5dRScYwc8xKphVe9VsdrlGzy3QZXZg2I8Jab530JsOyx4RRjbR /XCsHXWdjapK/nxWKEDz12htF/DmEIFCJ5KkAbPVoDlQpf4TdUfXzVgO0hVqgBIK0IFAmzh3B2M KHXU15AgDYbsUFsqSXe6UyvCqwsh2krzNcCKFT5c/msUC5wFQRNzcbBs7azLfj4DHOYjBjiZ5zf GdH8k30zA3FGTDk+Xt60beBAogxAM8jMXjBF+sIMbH85DUZXyseWplitmp0j6C0ePs7A07R/88i /oAaos2nAZuKjSYWyq5xmK8A5BIWX0pLUwXE6XFK/XDSvv6PM=
Archived-At: http://mailarchive.ietf.org/arch/msg/mpls/dRWayEFKDhGANaCgVn2V4aSQ_a4
Cc: mpls@ietf.org, mpls-chairs@tools.ietf.org, draft-ietf-mpls-ipv6-only-gap@tools.ietf.org, 'The IESG' <iesg@ietf.org>
Subject: Re: [mpls] Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS and COMMENT)
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: Sun, 23 Nov 2014 07:07:45 -0000
[Adding the MPLS WG] That's a pretty fine question, Barry. I'd say that, despite the care and work of the working group, it is possible that another gap will be identified. However, I think that might be a lowish possibility and that any new gaps might form a small percentage of the total gaps analysed. So, my judgement is that this is a bridge to cross when we get there, but others might comment. And, yes, we can take a pass on the references. A > -----Original Message----- > From: iesg [mailto:iesg-bounces@ietf.org] On Behalf Of Barry Leiba > Sent: 23 November 2014 06:49 > To: The IESG > Cc: mpls-chairs@tools.ietf.org; draft-ietf-mpls-ipv6-only-gap@tools.ietf.org > Subject: Barry Leiba's Discuss on draft-ietf-mpls-ipv6-only-gap-03: (with DISCUSS > and COMMENT) > > Barry Leiba has entered the following ballot position for > draft-ietf-mpls-ipv6-only-gap-03: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > http://datatracker.ietf.org/doc/draft-ietf-mpls-ipv6-only-gap/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > This is a DISCUSS in the truest sense: I'd like to discuss a question > with the shepherd and/or AD, and I fully expect to resolve the question > satisfactorily from that. > > The first thing I wondered was why this shouldn't be something maintained > in a place other than an RFC, and I found that covered well in the > shepherd writeup. Thanks for that! > > What I continue to wonder is whether, in having that discussion, the > working group considered what the likelihood is of discovering more gaps > as they (and other working groups) work on dealing with these. If so, I > wonder what the working group's plan is for documenting those. > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > I submit that a good number of the references really are normative, in > that understanding them is necessary in order to understand this > document. I'd like to see the authors sort that out, and make an > appropriate split in the references, so readers can know which ones truly > do just add extra detail (informative), and which provide necessary > background (normative). That said, I don't consider that important > enough to this document to block on it, so this is a non-blocking > comment. Please consider doing this, but there is no need to respond to > me about it. Thanks.
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Adrian Farrel
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Stewart Bryant (stbryant)
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Loa Andersson
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Mark Tinka
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Barry Leiba
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Barry Leiba
- Re: [mpls] Barry Leiba's Discuss on draft-ietf-mp… Carlos Pignataro (cpignata)