+1, and we also hope to present the softwire mesh MIB
Dear Chairs:
Are there any plans to discuss the MIBs at the interim meeting? According
to our softwire WG milestones, our MIBs also need more discussions.
-1.
MIBs are boring. ;-)
cheers,
Ole
Best Regards
Yu
Hi Tina,
I agree with Yiu. FYI, we had a discussion between co-authors of the draft
whether we maintain
http://tools.ietf.org/html/draft-qin-softwire-dslite-multicast-04#section-8 or
remove it.
You can read in that section:
Additionally,
mechanisms such as MLD Snooping, MLD Proxying,
Hi Tina,
I agree with Yiu. FYI, we had a discussion between co-authors of the draft
whether we maintain
http://tools.ietf.org/html/draft-qin-softwire-dslite-multicast-04#section-8 or
remove it.
You can read in that section:
Additionally,
mechanisms such as MLD Snooping, MLD
Alain
I would like to have a presentation our draft.
http://tools.ietf.org/html/draft-sakura-6rd-datacenter-01
I was assigned time slot on IETF81,but I could not...
This is informative 6rd draft for operators,I think.
Please assign a slot for this.
And if it is possible,please assign faster of
isn't this interim there to discuss the new stateless approaches. not to be
overflow meeting for whatever didn't make it on the agenda at the last IETF
meeting?
if we get time to spare fine, but I would certainly have liked this meeting to
be focused on the stateless solutions. and with the
Ole
Ok.I won't,if this interim will focuses discussion of new stateless solution
and it is not enough time.
And if it is possible,please assign faster of time slot.
Let's move to lower priority of time slot.
Regards,
-Shishio
Ole Troan wrote:
isn't this interim there to discuss the new
Hi, Alain and Yong,
We would like to have a presentation of two related drafts in the
interim meeting.
https://datatracker.ietf.org/doc/draft-xli-behave-divi-pd/
https://datatracker.ietf.org/doc/draft-xli-behave-divi/
Please assign a slot for this.
Thanks!
Xing Li
于 2011/8/22 23:37,
Bonjour Med,
Thank you for your comments.
What Yiu said is not reflected in figure 3. In the current figure, mAFTR can
receive (PIMv6 Join, PIMv6 Routers in between). However, if the IPv6 network is
layer 2 network, mAFTR should be able to receive MLD report as well. mAFTR also
performs
Hi all,
In section 6.3, To avoid fragmentation, a
service provider may increase the MTU size by 40 bytes on the IPv6
network or mAFTR and mB4 may use IPv6 Path MTU discovery.
How to use IPv6 Path MTU discovery to avoid fragmentation?
Best Regards,
Tina TSOU
hi,
On Fri, Aug 26, 2011 at 10:31 AM, Tina TSOU tina.tsou.zout...@huawei.comwrote:
Bonjour Med,
Thank you for your comments.
What Yiu said is not reflected in figure 3. In the current figure, mAFTR
can receive (PIMv6 Join, PIMv6 Routers in between). However, if the IPv6
network is layer 2
Hi,
On Fri, Aug 26, 2011 at 10:36 AM, Tina TSOU tina.tsou.zout...@huawei.comwrote:
Hi all,
In section 6.3, To avoid fragmentation, a
service provider may increase the MTU size by 40 bytes on the IPv6
network or mAFTR and mB4 may use IPv6 Path MTU discovery.
How to use IPv6 Path MTU
11 matches
Mail list logo
