[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MBONED] Fwd: I-D Action:draft-ietf-mboned-rfc3171bis-06.txt
Hi Michelle,
I hope I am not too late to take a look at this draft. Overall it looks pretty good. I have few questions and suggestions on this.
• In section 3, in the table, it will be better if we either use number of multicast addresses available fo use or '/x' method to represent the size of a given block.
• In section 5.1, s/for protocol control that/for protocol control traffic that/
• In section 9.2, in the following line "Addresses within this block MUST NOT appear on the public Internet.". Are we talking about the AD-HOC Block II when we say 'this block'? I think not. Can we clarify this?
• In section 12.2, A small typo in "temporary assignment or the addresses assigned", 'or' -> 'of'
• In section 12.2, after the one month period, can the registrant who was using these addresses, get allocated these addresses again? It is mentioned that this won't be available for one calender year but as it is not being used by anyone so can the last registrant can get it before this period ends.
Thanks,
Bharat
________________________________________
From: mboned-bounces at ietf.org [mboned-bounces at ietf.org] On Behalf Of Michelle Cotton [michelle.cotton at icann.org]
Sent: Tuesday, March 24, 2009 2:04 AM
To: ah at tr-sys.de; Leo Vegoda; dmm at 1-4-5.net; tme at multicasttech.com; mboned at ietf.org
Subject: Re: [MBONED] Fwd: I-D Action:draft-ietf-mboned-rfc3171bis-06.txt
As part of the mini-last call Marshall just announced in the WG meeting here in San Francisco, we need to sort this out now.
Can someone let us know if something needs to be done regarding the gap Alfred describes? This needs to be sorted out before Friday so that Marshall can submit to the IESG.
Thanks!
Michelle
IANA
On 3/23/09 12:51 PM, "ah at tr-sys.de" <ah at tr-sys.de> wrote:
Hello all,
> Today, Marshall Eubanks wrote:
>
> We regard this draft as now ready to go to the IESG, and will
> so announce in session today.
>
> I plan to do this after the close of this week (after Friday).
> Please consider this as a informal "mini-last call" to make
> sure that all of the issues raised were addressed.
>
> Regards
> Marshall
I had raised an (IMHO) important technical issue for the -05 version
of the rfc3171bis draft and now see it has _not_ been addressed.
! The only significant sub-topic left open in the -05 draft version
! is the remaining (single) gap in the multicast address space covered
! by the table in Section 3; for completeness and clarity, the tagged
! line shown below should be inserted at the indicated place:
!
! ----snip----
! 224.2.0.0 - 224.2.255.255 (/16) SDP/SAP Block
! |
! |224.3.0.0 - 224.251.255.255 (249 /16) RESERVED
! :
! :224.252.0.0 - 224.255.255.255 (/14) RESERVED
! ----snip----
!
! Or is this address range designated for other purposes?
!
! The third range is the ex "DIS Transient Groups" range returned
! to IANA. If the missing long range shall remain in the RESERVED
! state, conceivably the latter two ranges could be joined:
!
! ----snip----
! 224.2.0.0 - 224.2.255.255 (/16) SDP/SAP Block
! |
! |224.3.0.0 - 224.255.255.255 (253 /16) RESERVED
! ----snip----
For reference, please see:
http://www.ietf.org/mail-archive/web/mboned/current/msg00779.html
http://www.ietf.org/mail-archive/web/mboned/current/msg00780.html
for the original message (including other minor issues as well)
and Michelle's call for comments on the list.
Browsing the MBONED list archive, I unfortunately could not find
any follow-up messages filed there;
thus, the flaw should not be blamed to the draft authors.
++++>> WG, please take care of this gap and advice the authors.
++++>> Thanks!
Kind regards,
Alfred HÎnes.
--
+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. |
| Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 |
| D-71254 Ditzingen | E-Mail: ah at TR-Sys.de |
+------------------------+--------------------------------------------+
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are not
to copy, disclose, or distribute this e-mail or its contents to any other person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
every reasonable precaution to minimize this risk, but is not liable for any damage
you may sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***