Re: [addr-select-dt] slide to 6man presentation

[Arifumi Matsumoto <[e-mail]>]

On 2010/07/26, at 18:13, Tim Chown wrote:

> Hi,
> 
> Some comments....
> 
> - the DT draft is missed from the slides: draft-ietf-6man-addr-select-considerations-02
> 
> May wish to have a slide summarising the most recent focuses in that draft, for example including some/all of:

Sorry for that.
I put together these slides from top of my head in the plane. 

However, we should not mention all the changes. To make it simple and easy to focus on the important points.

> 
> - frequent policy changes are linked to having either rapid traffic engineering changes/external routing changes or lots of mobile nodes within the site moving between points of attachment with different policies
> 
> - it seems sensible to acquire RFC3484 policy when acquiring other configuration information
> 
> - in a managed enterprise there is likely to be a managed policy, and DHCP available
> 
> - in dynamic/unmanaged networks using routing hints for address selection *may* be more appropriate

I cannot get what exactly mean by this sentence.
Do you assume a environment where a mobile node with multiple interface can make use of routing information for address selection ?

> 
> - the problem of handling policy conflict is a host issue, the method to distribute the policy is a network issue - we focus here on the network issue since the host issue is broadly applicable to many configuration parameters

Important point.
I knew that, but I could not find a space for that.
Maybe we need to add some slides to elaborate.

> - we should avoid delaying progression of a 3484 policy distribution method applicable to managed enterprise networks

Not only enterprise networks, but for networks where multiple upstream networks can talk with each other.

> I think this material could fit in a new Slide 3 and then you continue the arifumi-6man-addr-select-conflict reference after that, to keep the flow.
> 
> I see a new Troan multihoming draft came out this morning, I've not checked what changes there are yet.

The main changes are about the legacy host support. Support by using NAT66 to the wrongly source-addressed packets.

Regards,


> 
> Cheers,
> Tim
> 
> On 24 Jul 2010, at 23:49, Arifumi Matsumoto wrote:
> 
>> Hi,
>> 
>> I drafted the slide for 6man.
>> This version still has some clear errors, so
>> I have to fix them.
>> 
>> I really want you all to comment on this.
>> About the story itself, wording, typos, and whatever.
>> 
>> <ietf78-6man-dt.pdf>_______________________________________________
>> addr-select-dt mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/addr-select-dt
> 
> _______________________________________________
> addr-select-dt mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/addr-select-dt