Re: draft-ietf-mboned-ieee802-mcast-problems-07 submitted, new WGLC to be initiated

"Holland, Jake" <[email protected]> Mon, 12 Aug 2019 18:34:30 +0000

Newsgroups	gmane.ietf.mboned
Message-ID	<[email protected]>

Hi Charlie,

While working on the shepherd write-up for ieee802-mcast-problems I saw that
there were some unaddressed nits auto-detected by the nits tool:

https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-mboned-ieee802-mcast-problems-07.txt

** The document seems to lack a both a reference to RFC 2119 and the
recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
keywords.

RFC 2119 keyword, line 639: '... It is RECOMMENDED that multicast-en...'

== Missing Reference: 'ICMPv6' is mentioned on line 558, but not defined

I'm not sure whether it's better to remove the single RECOMMENDED usage and
make it a weaker non-normative suggestion or to add the boilerplate, but it
probably should be fixed, and I suppose the ICMPv6 deserves a reference also.

Thanks and regards,
Jake

On 2019-07-26, 11:29, "Charlie Perkins" <[email protected]> wrote:

Hello folks,

Since the conclusion of the previous WGLC for
draft-ietf-mboned-ieee802-mcast-problems, the following changes have
been made.

o Improved wording in section describing ARPsponge.
o Included new text in Security Considerations to alert about
problems regarding Group Key management caused by multicast
unreliability and implementation bugs.
o Corrected occurrences of "which" versus "that" and "amount" versus
"number".
o Updated bibliographic citations, repaired broken URLs as needed.
o Many more editorial improvements and grammatical corrections.

Some of these changes, while not controversial, deserve at least the
opportunity for WG review. Please take a look at the new draft
draft-ietf-mboned-ieee802-mcast-problems-07.

Regards,
Charlie P.

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned