Re: mumti6dt drafts as WG drafts?

Well, yes, the solution architecture draft is intended to give the
overview.

It's quite likely that when the various pieces have stabilized,
they should be combined into a more complete document. But that is
really a question for whichever WG is tasked with doing the complete
specification, so it is not a question for multi6 today. The idea now
was to get the existing drafts into a good state individually.

     Brian

Mohan Parthasarathy wrote:
> Brian,
> 
> So, the solution architecture document will come later on based on the
> WG documents i guess. What is the rationale behind having it as
> separate documents still ? Having read some of them, i felt that it might be
> good to have some of them at least merged to understand the solution
> better. For example, the first three below (shim, hba and func) can be
> merged. 
> 
> -mohan
> 
> 
>>In accordance with the consensus to proceed with the direction
>>proposed by the design team, does anyone object to the next versions
>>of the following drafts being formally adopted as WG drafts?
>>This would mean they have names like draft-ietf-multi6-*
>>
>>Please let us know this week if you object, and why.
>>
>>     Multihoming Level 3 Shim Approach
>>     (draft-nordmark-multi6dt-shim-00.txt)
>>     Hash Based Addresses (HBA)
>>     (draft-bagnulo-multi6dt-hba-00.txt)
>>     Functional decomposition of the M6 protocol
>>     (draft-bagnulo-multi6dt-functional-dec-00.txt)
>>     Failure Detection and Locator Selection in Multi6
>>     (draft-arkko-multi6dt-failure-detection-00.txt)
>>     Multi6 Application Referral Issues
>>     (draft-nordmark-multi6dt-refer-00.txt)
>>
>>
>>    Brian
>>    multi6 co-chair
>>
> 
>