[lisp] Fwd: WG Review: IDentity Enabled Networks (ideas)

FYI.

Dino

> Begin forwarded message:
> 
> From: The IESG <iesg-secretary@ietf.org>
> Subject: WG Review: IDentity Enabled Networks (ideas)
> Date: September 29, 2017 at 9:13:28 AM PDT
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: ideas@ietf.org
> Reply-To: ietf@ietf.org
> 
> A new IETF WG has been proposed in the Routing Area. The IESG has not made
> any determination yet. The following draft charter was submitted, and is
> provided for informational purposes only. Please send your comments to the
> IESG mailing list (iesg@ietf.org) by 2017-10-09.
> 
> IDentity Enabled Networks (ideas)
> -----------------------------------------------------------------------
> Current status: Proposed WG
> 
> Chairs:
>  Padma Pillay-Esnault <padma.ietf@gmail.com>
> 
> Assigned Area Director:
>  Alvaro Retana <aretana@cisco.com>
> 
> Routing Area Directors:
>  Alia Atlas <akatlas@gmail.com>
>  Alvaro Retana <aretana@cisco.com>
>  Deborah Brungard <db3546@att.com>
> 
> Mailing list:
>  Address: ideas@ietf.org
>  To subscribe: https://www.ietf.org/mailman/listinfo/ideas
>  Archive: https://mailarchive.ietf.org/arch/browse/ideas/
> 
> Group page: https://datatracker.ietf.org/group/ideas/
> 
> Charter: https://datatracker.ietf.org/doc/charter-ietf-ideas/
> 
> Network solutions based on the concept of Identifier-Locator separation are
> increasingly considered to support mobility, overlay networking for
> virtualization and multi-homing across heterogeneous access networks.
> Identifier-locator separation protocols require infrastructure that allows
> nodes to discover the network topological location(s) of its peer(s) for
> packet delivery. A common infrastructure and protocol could be used by
> identifier/locator protocols as well as network virtualization. However,
> additional infrastructure and new protocol extensions are needed to address
> new requirements that go well beyond the traditional discovery service and
> mapping of identifier-to-location for packet delivery. Identifier-locator
> protocols are also useful for additional services involving dynamic
> association of a name to a set of network addresses - these include dynamic
> multicast, cloud service anycast and context-aware IoT queries.
> 
> The IDEAS WG is chartered to produce a framework document that defines the
> expected behavior of a mapping system across the multiple existing use cases.
> The framework will aim at a homogeneous behavior across use cases, and it
> will call out specific trade-offs that may be considered in the development
> of solutions.  We refer to the framework providing the set of services as
> Generic Identity Services (GRIDS).
> 
> Some of the areas that must be considered when developing the framework
> include:
> 
> - Description of interfaces for different protocols to interact with the
> framework (e.g. id-loc split protocols, management protocols, etc)
> 
> - Description of identifier/locator mapping resolution and mapping update
> (e.g. discovery, pub/sub, multi-homing, ...)
> 
> - Registration and lifecycle management of identities and their associated
> identifiers.
> 
> - Identity authentication and authorization (e.g. access to framework, update
> of information for identifiers..)
> 
> - Description of required basic network policies and policy enforcement needs
> (e.g. ability to look up an identifier-locator pair, permit forwarding
> traffic for particular endpoints on a per-identity basis, etc.)
> 
> - Analysis of the concepts of identity-identifier split and dynamic
> identifier changes, including their implications on anonymity and privacy.
> Explicitly, the framework must define privacy requirements and how potential
> extensions/solutions should meet them.
> 
> - Security analysis of the complete system, including authentication,
> authorization requirements and protection of any metadata.
> 
> - Operational and deployment considerations
> 
> The IDEAS WG will closely coordinate with the LISP and HIP WGs (and with
> others as needed) in order to keep them well-informed of the progress.  Any
> extension to existing protocols that is identified while developing the
> framework document will be carried out in the responsible WG for that
> protocol; any extension work to be done in this WG will require re-chartering.
> 
> WG deliverables include:
> 
> (1) Generic Identity Services Framework
> 
> (2) Other WG sustaining/informational documents may include:
> 
> - Problem statement
> - Use cases
> - Requirements for identifier/locator mapping and resolution
> - Requirements for identity authentication and authorization service (for
> GRIDS) - Applications of the architecture for use cases - Threat model
> document
> 
> These documents will not be published as RFCs, but will be maintained in a
> draft form or on a collaborative Working Group wiki to support the efforts of
> the Working Group and help new comers.
> 
> Milestones
> 
> January 2018 Adopt WG draft for the Generic Identity Services framework
> July 2018 WGLC for the Generic Identity Services framework
> September 2018 Send Generic Identity Services framework draft to the IESG
> November 2018 Recharter or Close
> 
> 