Re: [IPv6] 4-in-1

Hello Behcet:

could you please provide an example to illustrate your meaning?

regards,

Pascal
________________________________
De : ipv6 <ipv6-bounces@ietf.org> de la part de Behcet Sarikaya <sarikaya2012@gmail.com>
Envoyé : vendredi 16 juin 2023 17:41
À : Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>
Cc : 6man@ietf.org <6man@ietf.org>
Objet : Re: [IPv6] 4-in-1

Hi Pascal,

It think the main comment on your draft was that the language, the model used was based on IEEE's link model from the 1970s, etc. used was archaic.
I don't think that can be fixed with a minor revision.

Behcet
On Fri, Jun 16, 2023 at 10:24 AM Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>> wrote:
Dear all:

I republished draft-ietf-6man-ipv6-over-wireless to address Brian's suggestion (WiND->SND), and Ted's point of mDNS references. Plus a few nits.

Left is Lorenzo's point of too much stuff for one document. It's effectively a 4-in-1, a problem statement (section 3), an architecture (section 4), a solution framework (section 5), and an applicability statement (section 6):

   3.  Issues with IPv6 ND-Based Access  . . . . . . . . . . . . . .   5
   4.  IPv6 over Non-Broadcast Networks Architecture . . . . . . . .  14
   5.  IPv6 over Non-Broadcast Networks Framework for Stateful address
   6.  SND Applicability . . . . . . . . . . . . . . . . . . . . . .  32

So should we split? Will reviewing and pushing 4 small docs through IESG help?

all the best

Pascal

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------