[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Yet anoter charter version



Hi Kurt,

Looks good, some small comments:

> The shim6 WG is to produce specifications for a complete IPv6

-> Could we drop 'complete' - there are some things, like multihoming
policy that is out of scope, but probably is needed to actually
get the thing running.

> site-multihoming solution based on the architecture developed by the
> IETF multi6 WG. The multi6 WG was tasked with investigating solutions
> to the site multihoming problem that will allow the global routing
> system to scale. The outcome of the multi6 WG is a specific
> network-layer shim architecture for addressing and address handling of
> sites and nodes. This includes switching to different locator
> addresses when connectivity changes, but without the changes of
> address being visible to upper layers, which see a fixed Upper Layer
> Identifier address (ULID).
> 
> The shim6 WG is to complete this work with the required protocol developments
> and complete the architecture and security analysis of the required 
> protocols.
> 
> The background documents to be considered by the WG include:
> 
>   RFC 3582
>   draft-ietf-multi6-things-to-think-about-01.txt
>   draft-ietf-multi6-multihoming-threats-03.txt
> 
> The input documents that the WG will use as the basis for its design 
> are:
> 
>   draft-huston-l3shim-arch-00.txt
>   draft-ietf-multi6-functional-dec-00.txt
>   draft-ietf-multi6-l3shim-00.txt
>   draft-ietf-multi6-failure-detection-00.txt
>   draft-ietf-multi6-hba-00.txt
>   draft-ietf-multi6-app-refer-00.txt
> 
> The shim6 WG is to publish, as standards track RFCs, specifications with
> enough details to allow full interoperable implementations of the shim
                       -> fully

> layer approach to multihoming as agreed on by the multi6 WG. These
> implementations will have the ability to take advantage of
> multihoming without adding to the growth of the global routing table
> by using aggregates already announced by upstream providers.

Otherwise, I think this looks good.

John