IETF Logo Mail Archive

Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 29 November 2017 15:49 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2996128799 for <v6ops@ietfa.amsl.com>; Wed, 29 Nov 2017 07:49:20 -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 cq_C6A4_MCiE for <v6ops@ietfa.amsl.com>; Wed, 29 Nov 2017 07:49:11 -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 157A81275C5 for <v6ops@ietf.org>; Wed, 29 Nov 2017 07:49:11 -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 vATFn9TJ023387; Wed, 29 Nov 2017 08:49:10 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vATFn0PJ023279 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 29 Nov 2017 08:49:00 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 29 Nov 2017 07:48:59 -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.1320.000; Wed, 29 Nov 2017 07:48:59 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Paul Marks <pmarks@google.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-templin-v6ops-pdhost a working group draft?
Thread-Index: AdNoiEQoZAX3ZeaJTjOHwVsWAIjDPwAbKBoAAAyErnA=
Date: Wed, 29 Nov 2017 15:48:59 +0000
Message-ID: <f8f12bc3f534470db63f5172fc69e862@XCH15-06-08.nw.nos.boeing.com>
References: <34cf035352254aadb3146dffb3baebb0@XCH15-06-08.nw.nos.boeing.com> <CAHaKRvJCabgnc3U-ouZ1ghmwYzOQ+H1fDHwKrac6ghxaH=+Zdw@mail.gmail.com>
In-Reply-To: <CAHaKRvJCabgnc3U-ouZ1ghmwYzOQ+H1fDHwKrac6ghxaH=+Zdw@mail.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DZQlCep7r0fBYmPMlwvuGOhpCC4>
Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2017 15:49:21 -0000

Hi Paul,

Thanks for the reminder about this interesting question. See below:

> -----Original Message-----
> From: Paul Marks [mailto:pmarks@google.com]
> Sent: Tuesday, November 28, 2017 5:32 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] draft-templin-v6ops-pdhost a working group draft?
> 
> On Tue, Nov 28, 2017 at 12:37 PM, Templin, Fred L
> <Fred.L.Templin@boeing.com> wrote:
> > See below for an updated version of this draft. This version addresses comments
> > received on the list regarding more clearly identifying classes of devices that can
> > be considered as ordinary routers.
> 
> Have you considered clarifying whether addresses at the top and bottom
> of the delegated prefix (RFC 2373, RFC 2526) should be reserved under
> this model?

I think in the router model, subnetting the delegated prefix would be
exactly the same as for any router. So, subnet router anycast for
example would have the same significance as in any routing hierarchy.

> When delegating to a host, I often wonder whether it's technically
> incorrect to use prefix::0 as a normal address.  Does anyone know for
> sure?

In the host model, I would like to say that address autoconfiguration is per
standard IPv6 procedures and leave that as out of scope for this document.
But, perhaps I could also add a reference to RFC4291(bis) and say that address
autoconfiguration must be consistent with the IPv6 addressing architecture.

About prefix::0, I think we would have to determine whether local
applications, middleboxes and/or correspondents would view that as a
special address and do something different with it than for an ordinary
GUA. But, I think that is out of scope for this document.
 
What do you think?

Thanks - Fred

v2.23.0 | Report a Bug | By Email