IETF Logo Mail Archive

[v6ops] FW: I-D Action: draft-templin-v6ops-pdhost-06.txt

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 05 September 2017 21:27 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 E373312895E for <v6ops@ietfa.amsl.com>; Tue, 5 Sep 2017 14:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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, URIBL_BLOCKED=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 USUcoF25wuey for <v6ops@ietfa.amsl.com>; Tue, 5 Sep 2017 14:27:11 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 25B6C1243F6 for <v6ops@ietf.org>; Tue, 5 Sep 2017 14:27:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v85LR9oh006786; Tue, 5 Sep 2017 14:27:10 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v85LR9sE006626 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <v6ops@ietf.org>; Tue, 5 Sep 2017 14:27:09 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 5 Sep 2017 14:27:08 -0700
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; Tue, 5 Sep 2017 14:27:08 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: v6ops list <v6ops@ietf.org>
Thread-Topic: I-D Action: draft-templin-v6ops-pdhost-06.txt
Thread-Index: AQHTJoxCYBlQLPEYAUGtsG36832ak6KmzGnw
Date: Tue, 05 Sep 2017 21:27:08 +0000
Message-ID: <f8c656e010834843b41eb40051a7ab60@XCH15-06-08.nw.nos.boeing.com>
References: <150464618134.29784.3337785472849329615@ietfa.amsl.com>
In-Reply-To: <150464618134.29784.3337785472849329615@ietfa.amsl.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/v6ops/Q8O1nInDJ7NqWQVWCnRxtm4udGo>
Subject: [v6ops] FW: I-D Action: draft-templin-v6ops-pdhost-06.txt
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: Tue, 05 Sep 2017 21:27:13 -0000

Hi, here is a draft that is very closely related to RFC7934 and 'unique-ipv6-prefix-per-host'.
It described the options available for a node that receives a unique prefix delegation from
the network in terms of routing and multi-addressing considerations. It is of direct interest
to this community.

I have given my time and energies to contribute to the aforementioned v6ops docs and
would appreciate input from the working group on my document. Please see below for
abstract and URLs.

Thanks - Fred

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Tuesday, September 05, 2017 2:16 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-templin-v6ops-pdhost-06.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : IPv6 Prefix Delegation for Hosts
        Author          : Fred L. Templin
	Filename        : draft-templin-v6ops-pdhost-06.txt
	Pages           : 10
	Date            : 2017-09-05

Abstract:
   IPv6 prefixes are typically delegated to requesting routers which
   then use them to number their downstream-attached links and networks.
   This document considers both this traditional case, and the case when
   the "requesting router" is actually a simple host which receives a
   delegated prefix that it can use for its own internal multi-
   addressing purposes.  This latter method can be employed in a wide
   variety of use cases to allow ample address availability without
   impacting link performance.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-templin-v6ops-pdhost/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-templin-v6ops-pdhost-06
https://datatracker.ietf.org/doc/html/draft-templin-v6ops-pdhost-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-templin-v6ops-pdhost-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

v2.46.0 | Report a Bug | By Email | System Status