IETF Logo Mail Archive

RE: 6man w.g. last call for <draft-ietf-6man-rfc6434-bis-03.txt> [Second try]

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 07 February 2018 15:47 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 0686012D7EB for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 07:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 RE5ekVROK-Er for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 07:47:23 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3C2F126E3A for <ipv6@ietf.org>; Wed, 7 Feb 2018 07:47:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id w17FlMh1017357; Wed, 7 Feb 2018 08:47:22 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w17FlINi017318 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 7 Feb 2018 08:47:19 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 7 Feb 2018 07:47:18 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1347.000; Wed, 7 Feb 2018 07:47:18 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-rfc6434-bis-03.txt> [Second try]
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-rfc6434-bis-03.txt> [Second try]
Thread-Index: AQHTn6GnqJA3u+zVGkK+5I1M3sdCkqOYpFqAgABxKtA=
Date: Wed, 07 Feb 2018 15:47:18 +0000
Message-ID: <01e0a51ed886470eb9f45a403e9b3660@XCH15-06-08.nw.nos.boeing.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <DFBAB1B6-7F1A-4E10-9239-955DCD184A1F@gmail.com> <2f60e27d-f669-16dc-c1a5-de1b389b41fe@gmail.com>
In-Reply-To: <2f60e27d-f669-16dc-c1a5-de1b389b41fe@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8stb44Q8fUj9FFQBC3NQKyMdZys>
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: Wed, 07 Feb 2018 15:47:26 -0000

Hi,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Tuesday, February 06, 2018 4:58 PM
> To: ipv6@ietf.org
> Subject: Re: 6man w.g. last call for <draft-ietf-6man-rfc6434-bis-03.txt> [Second try]
> 
> I think this is ready. It can only be a snapshot, and today is as good
> as any day to take the snapshot.

I agree that this is a snapshot based on what we know today. I think what we
really need is a "living document", but I don't think IETF process is oriented
toward supporting that concept. Should we expect to see a successive string
of (bis)es going forward into the future after this gets published?

Thanks - Fred

>     Brian
> 
> On 07/02/2018 12:24, Bob Hinden wrote:
> >
> > This message starts a two week 6MAN Working Group Last Call on advancing:
> >
> >       Title           : IPv6 Node Requirements
> >       Authors         : Tim Chown
> >                         John Loughney
> >                         Timothy Winters
> >       Filename        : draft-ietf-6man-rfc6434-bis-03.txt
> >       Pages           : 40
> >       Date            : 2018-02-06
> >
> >       https://tools.ietf.org/html/draft-ietf-6man-rfc6434-bis-03
> >
> > as a Best Current Practice (BCP).  Substantive comments and statements of support
> > for publishing this document should be directed to the mailing list.
> > Editorial suggestions can be sent to the author.  This last call will
> > end on 20 February 2018.
> >
> > Thanks,
> > Bob & Ole
> >
> >
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email