Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
Joe Touch <touch@isi.edu> Sat, 18 March 2017 16:27 UTC
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05ABA1288B8; Sat, 18 Mar 2017 09:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 mPzjNrrtT4KO; Sat, 18 Mar 2017 09:27:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 B2D2F1277BB; Sat, 18 Mar 2017 09:27:36 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2IGQgkX011175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 18 Mar 2017 09:26:44 -0700 (PDT)
Subject: Re: [Tsv-art] TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
References: <48bfa3a1-e53c-6b31-69b0-2645ddd5937f@isi.edu> <41A44496-F222-40D5-95FE-5CE142C3827F@gmail.com> <46d7ae23-cf3d-570d-3d79-9d915663cf16@isi.edu> <8D6CA1F7-CB01-4FCD-B81C-ECBEFC088EAE@gmail.com> <e55e095b-b5c6-56e8-d4be-0b438c61ae67@isi.edu> <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com>
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, IESG <iesg@ietf.org>, "tsv-art@ietf.org" <tsv-art@ietf.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <01fc4067-6825-9343-7735-86f9bf77bebe@isi.edu>
Date: Sat, 18 Mar 2017 09:26:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-eqbA65wiyP575Kbni4b31Jo37uZ0n=0UGn62A_n30H8Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------6F495733573D7217B70CDADB"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qTOt9LlJRH55ohstYgkSlq-Eb9E>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 16:27:39 -0000
FWIW, I was thinking of an update that focused on the description issue below. Nothing functionally would change. Joe On 3/18/2017 9:03 AM, Spencer Dawkins at IETF wrote: > I may not be answering the question Joe asked, but ... > > On Mar 17, 2017 19:36, "Joe Touch" <touch@isi.edu > <mailto:touch@isi.edu>> wrote: > > > > On 3/17/2017 4:31 PM, Bob Hinden wrote: > > Joe, > > > > I think this will be up to the AD and IESG. > OK - I'll wait for them to respond. > > If you (and others) want to work on a major update, I am happy > to share the XML. I hope we don’t end up with can’t move the > current document forward, and no one wants to do a major update. > I'd certainly prefer to have this doc address these issues. > > One question - if a major update occurred, would that be at the same > standard level? If so, and if these issues are of concern, I'd be glad > to take that on. > > If a major rev is a standards-level setback, that would be less > useful. > > I'd like to hear their views... > > > So, RFC 1981 is a Draft Standard, which is theoretically a bigger deal > than a Proposed Standard. If a replacement to RFC 1981 doesn't work > the same way that RFC 1981 works, I don't see how it would also be a > Draft Standard, based on the standards level of the RFC it would be > replacing. Do others see something I'm missing? > > However. > > Assuming that a replacement for RFC 1981 Path MTU Discovery doesn't > have the issues we've been talking about in these threads, I would > hope that we could publish that replacement at Proposed Standard (not > at Experimental). > > Given that we don't use the Draft Standard level for advancing > standards track RFCs any more (post > https://datatracker.ietf.org/doc/rfc6410/), would publishing a > replacement that works better than RFC 1981 at Proposed Standard be a > bad thing? > > Curiously yours, > > Spencer > > > Joe > > _______________________________________________ > Tsv-art mailing list > Tsv-art@ietf.org <mailto:Tsv-art@ietf.org> > https://www.ietf.org/mailman/listinfo/tsv-art > <https://www.ietf.org/mailman/listinfo/tsv-art> > >
- TSV-ART Telechat review of draft-ietf-6man-rfc198… Joe Touch
- Re: TSV-ART Telechat review of draft-ietf-6man-rf… Joe Touch
- Re: TSV-ART Telechat review of draft-ietf-6man-rf… Bob Hinden
- Re: TSV-ART Telechat review of draft-ietf-6man-rf… Joe Touch
- Re: TSV-ART Telechat review of draft-ietf-6man-rf… Bob Hinden
- Re: TSV-ART Telechat review of draft-ietf-6man-rf… Joe Touch
- Re: [Tsv-art] TSV-ART Telechat review of draft-ie… Spencer Dawkins at IETF
- Re: [Tsv-art] TSV-ART Telechat review of draft-ie… Joe Touch
- Re: [Tsv-art] TSV-ART Telechat review of draft-ie… Spencer Dawkins at IETF