[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: comments on draft-daniel-ipv6-ra-mo-flags-00.txt
- To: Radhakrishnan Suryanarayanan <rkrishnan.s@xxxxxxxxxxx>
- Subject: Re: comments on draft-daniel-ipv6-ra-mo-flags-00.txt
- From: JINMEI Tatuya / $B?@L@x#:H(B
<jinmei@xxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 13 Aug 2004 14:34:31 +0900
- Cc: Soohong Daniel Park <soohong.park@xxxxxxxxxxx>,Syam Madanapalli <syam@xxxxxxxxxxx>, ipv6@xxxxxxxx,Pekka Savola <pekkas@xxxxxxxxxx>, greg.daley@xxxxxxxxxxxxxxxxx
- Delivery-date: Fri, 13 Aug 2004 08:48:31 +0300
- Envelope-to: archive@lists.atm.tut.fi
- In-reply-to: <06a001c480f4$b1314bf0$40476c6b@sisodomain.com>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,<mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,<mailto:ipv6-request@ietf.org?subject=unsubscribe>
- Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
- References: <Pine.LNX.4.44.0408102347400.7781-100000@netcore.fi><005e01c47faf$a61058b0$7b476c6b@sisodomain.com><y7vacwzsnao.wl@ocean.jinmei.org><411C4A29.5010200@eng.monash.edu.au><06a001c480f4$b1314bf0$40476c6b@sisodomain.com>
- Sender: ipv6-bounces@xxxxxxxx
- User-agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0(SAKAKI)
>>>>> On Fri, 13 Aug 2004 10:46:22 +0530,
>>>>> Radhakrishnan Suryanarayanan <rkrishnan.s@samsung.com> said:
>> > An implementation might explore an implementation dependent trick like
>> > combining routers and parameters to mitigate the bad effect of the
>> > admin error. However, I'd really want to make it outside the scope of
>> > the M/O document.
>>
>> I agree with this,
>>
>> In this case, we need to ensure that the router advertisement which
>> we're basing the decision on has the flags set.
>>
>> It may even be worthwhile explicitly stating that management of
>> flags from multiple routers is not in scope.
> Since the idea of the draft is for BCP/Informational on M&O, we shall as
> well add an
> appendix section to describe handling of the flags from multiple routers.
I don't mind adding the appendix as long we just describe possible
issues (if any) and do NOT try to provide workaround like combining
router/parameters.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
jinmei@isl.rdc.toshiba.co.jp
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------