Re: [v6ops] updated draft-shytyi-v6ops-danir

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 20 September 2019 14:42 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 57FAE1201E4 for <v6ops@ietfa.amsl.com>; Fri, 20 Sep 2019 07:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 pwen8Y50zz-i for <v6ops@ietfa.amsl.com>; Fri, 20 Sep 2019 07:42:00 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 66C00120089 for <v6ops@ietf.org>; Fri, 20 Sep 2019 07:42:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id x8KEfwkM017319; Fri, 20 Sep 2019 10:41:58 -0400
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id x8KEfqZB017268 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 20 Sep 2019 10:41:52 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Fri, 20 Sep 2019 07:41:51 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.1713.004; Fri, 20 Sep 2019 07:41:51 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] updated draft-shytyi-v6ops-danir
Thread-Index: AQHVb8GKiTW02BXllUWQcvDOjXA2GA==
Date: Fri, 20 Sep 2019 14:41:51 +0000
Message-ID: <283ff17a1a044db1a75235578358fc3b@boeing.com>
References: <867ca1bc-e2a6-8d1b-8cd0-c4a51c8f83ea@gmail.com> <039e65dbdb8b41feb76971ff89e5ab9d@boeing.com> <b8129cd2-b1d4-99c3-c6f1-549ccdafa6c0@gmail.com> <ff00aa92743d446fa6a4857df1d717d4@boeing.com> <24a8ec13-b32c-a060-41e3-c4ade3c0f4d5@gmail.com>
In-Reply-To: <24a8ec13-b32c-a060-41e3-c4ade3c0f4d5@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 80B7A60328B5EB9F4557537B240D137C166A4777A18F18770B19E0E591536ED72000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9E2Ot7lN2Dx4_AzobqEL1xAsToY>
Subject: Re: [v6ops] updated draft-shytyi-v6ops-danir
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 20 Sep 2019 14:42:02 -0000

Hi Alex,

> > Here is another active document with an approach to Prefix
> > Registration (as opposed to
> >
> > Prefix Delegation) that is being considered for civil aviation:
> >
> > https://datatracker.ietf.org/doc/draft-templin-atn-aero-interface/
> 
> It's an interesting draft.  Maybe we can advantageously refer bilaterally.
> 
> Alex

The draft has not quite crossed over from the aviation domain into the IETF yet,
but a reference could be added to the next version. I am contemplating adding
a short section on "Prefix Delegation vs Prefix Registration", where Delegation
is when the requesting node does not know beforehand what prefix the network
will give it, and Registration is when the requesting node already knows its prefix
and is just wanting for the network to inject it into the routing system. We deal
with both in the aviation domain, but expect that commercial aircraft will have
pre-placed prefixes that never change and need only be registered with the
routing system upon network join. (In fact, maybe I will just cut-and-paste
this text into  the draft.)

Thanks - Fred