Re: [v6ops] GRASP

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 20 December 2017 17:29 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 6C3461270A3 for <v6ops@ietfa.amsl.com>; Wed, 20 Dec 2017 09:29:47 -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 IPzmMuEu1bWI for <v6ops@ietfa.amsl.com>; Wed, 20 Dec 2017 09:29:45 -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 C82FF1241F3 for <v6ops@ietf.org>; Wed, 20 Dec 2017 09:29:45 -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 vBKHTjOt056692; Wed, 20 Dec 2017 10:29:45 -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 vBKHTh3O056589 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 20 Dec 2017 10:29:43 -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.1347.2; Wed, 20 Dec 2017 09:29:42 -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, 20 Dec 2017 09:29:42 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] GRASP
Thread-Index: AdN5IhZ/InAT2FQPSLSGequLh0yxXQARtPkAABM6xMA=
Date: Wed, 20 Dec 2017 17:29:42 +0000
Message-ID: <8316cc707dd847a8b2d45e4b6b468f36@XCH15-06-08.nw.nos.boeing.com>
References: <fc31bd170b134c8292d33f52400b175b@XCH15-06-08.nw.nos.boeing.com> <268669d2-e36d-9fb1-cf1c-d3be4cb85e51@gmail.com>
In-Reply-To: <268669d2-e36d-9fb1-cf1c-d3be4cb85e51@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/v6ops/nehaZ_e5CkFe1S3ZKDp46BWc_kI>
Subject: Re: [v6ops] GRASP
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, 20 Dec 2017 17:29:47 -0000

Hi Brian,

> No. It isn't competing with ND or DHCPv6 in the least.

OK, that is great but whenever we talk about prefix delegation
you say "go see anima" - so I did.

I read draft-ietf-anima-prefix-management which cites both
DHCPv6 PD and GRASP, so I took a high-level pass over GRASP
and saw that it was specifying a new service discovery protocol
which made me wonder whether it was entering into a new
tussle space involving DHCPv6 PD and IPv6 ND.

If there is in fact no tussle, can we say that IPv6 ND is the
mandated neighbor discovery service for IPv6 and that
DHCPv6 PD is the mandated prefix delegation service?
It would make life much easier to be able to cite IPv6ND
and DHCPv6  PD normatively instead of constantly having
to take care to cite them only as examples.

Thanks - Fred

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: Tuesday, December 19, 2017 4:03 PM
> To: v6ops@ietf.org
> Subject: Re: [v6ops] GRASP
> 
> On 20/12/2017 12:42, Templin, Fred L wrote:
> > Brian - what is this GRASP thing:
> >
> > https://www.ietf.org/id/draft-ietf-anima-grasp-15.txt
> >
> > First of all, it looks like a protocol specification but it is coming from an
> > operations WG which seems odd to me. How is it that anima can exist
> > as an OPS group and produce standards-track specifications?
> 
> Easily. This was a chartered work item and until recently one of the Internet
> ADs served as AD for the WG, precisely because we were chartered to do
> protocol development.
> 
> > Second, it looks like it wants to be a link-local discovery protocol that can
> > replace existing discovery protocols like DHCPv6, IPv6 ND, etc. Is that the
> > intention - to replace well established protocols with something new?
> 
> No. It isn't competing with ND or DHCPv6 in the least. GRASP Objectives (the
> atoms of discovery) are higher level objects than anything you would discover
> with DHCP or ND. There *is* an element of overlap with DNSSD, but we're
> working to avoid that becoming a tussle (draft-eckert-anima-grasp-dnssd-00).
> 
> You should start with https://tools.ietf.org/html/draft-ietf-anima-reference-model
> to get the big picture. Or if you prefer bullet points:
> https://github.com/becarpenter/graspy/blob/master/AN-overview.pdf
> 
> Regards
>     Brian
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops