HI Behcet,

On 6/26/06, Behcet Sarikaya <[EMAIL PROTECTED]> wrote:


Hi Samita,


----- Original Message ----
From: Samita Chakrabarti <[EMAIL PROTECTED]>
To: Soohong Daniel Park <[EMAIL PROTECTED]>
Cc: [email protected]
Sent: Monday, June 26, 2006 9:05:10 PM
Subject: Re: [6lowpan] 6lowpan-nd version 2


Hi Daniel,

Please see my comments in-line.

> > Erik and I have updated
draft-chakrabarti-6lowpan-ipv6-nd-02.txt and
> > submitted for publication. The new update includes a section on generic
> > application of this draft for non-multicast, non-broadcast network.
> > At the last wg meeting, the request was made for such an update  for
> > the Wimax effort on IPv6.
>
> Let me clarify one point,
>
> I remember the relevent discussion in Dallas. Yes, we definitely
> need this aspect, however 16ng WG (IP over IEEE 802.16)
> has been newly created in INT area and they will take care of
> this issue as one of WG deliverable. So, please toss it to that.

There is no conflict with 16ng ND with this work. As Erik and
Basavaraj mentioned
before that we need to make sure that 6lowpan-ND and 16ng ND modifications
do not provide different  solutions for the same problem. Because the
solution
presented in 6lowpan-ND document can be generally applicable to any other
non-multicast/broadcast  energy-efficient network (16ng is
one of the immediate
applications), the  'general applicability' of this
draft may be useful for other type of power efficient networks as well.

Thus the idea is that 16ng-ND draft can update its text based on the
information
in the general applicability section of the 6lowpan-ND draft.
==>There is no 16ng-ND draft, there is presently a draft which in part has
the relay DAD which seems to be adopted from your draft.
==>can you be more specific?

Good point. There is no 16ng-ND draft. 16ng has a document,
draft-madanapalli-ipv6-over-802.16-ipv6cs-00  which talks about
IPv6 issues in 802.16 networks.  6lowpan-ND optimizations are
applicable to those situations as well, in general, but  they need to
apply the ideas into their own network components, such as ASN-GW
as opposed to 802.15.4 co-ordinators.

Thus at Dallas meeting it was agreed that either we split the
6lowpan-ND for generic and 6lowpan-specific solutions or update the
6lowpan-ND
draft with a separate section for generic behavior.  IPv6-ND-over-Foo
networks then can refer to this general section for applying into
their own situations.

Regards,
-Samita







==>Thanks,
==>--behcet


> Here is a 16ng WG approval;
>
http://eeca16.sogang.ac.kr/pipermail/16ng/Week-of-Mon-20060619/000154.html
>
> > Two questions to the working group and the chairs:
> >
> >  1) Should this draft( 6lowpan-ipv6-nd) be published as a WG document ?
>
> I don't have a strong objection and the current document really looks
good.
> However before that, we should trigger 6lowpan WG rechartering taking
> into account this issue and others concerned.

We have had extensive discussion on the usefulness of 6lowpan-ND
work at the January Interim meeting. My understanding from that meeting is
that IPv6 ND optimization is a no-brainer item in the new charter.

So, I agree that it'll be good to see the 6lowpan charter updated.

Thanks,
-Samita

>
> In my memory, there are five items.
>
> - 6lowpan bootstrapping and IPv6 ND optimization
> - Stateful header compression problem statements
> - Recommendations for 6lowpan applications
> - 6lowpan mesh routing
> - 6lowpan security analysis
>
> Geoff and Carsten, what is going on in rechartering ?
>
> >  2) Are we OK with publishing the draft as "IPv6 Neighbor Discovery
> > Optimization
> >      for IEEE 802.15.4 and other non-multicast networks" so that it
contains
> >      specifics on 6lowpan and a generic guideline for other relevant
networks?
>
> Above.
>
>
> Regards.
>
> Daniel (Soohong Daniel Park)
> Mobile Convergence Laboratory, SAMSUNG Electronics.
>

_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan



_______________________________________________
6lowpan mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/6lowpan

Reply via email to