Subject: RE: mboned: I-D ACTION:draft-ietf-mboned-addrdisc-problems-00.txt

From: "Manfredi, Albert E" <[email-masked]>
Date: Fri, 25 Mar 2005 14:47:15 -0500

Pekka,

From my point of view, the text Beau suggests cannot be stressed enough. Not just the re-engineering of networks part, but also the simple fact that the 239/8 space is way too small to allow it to become globally first come first served.

The whole concept sounds unworkable to me.

Bert

> -----Original Message-----
> From: Pekka Savola [mailto:[email-masked]]
> Sent: Friday, March 25, 2005 1:40 AM
> To: Beau Williamson; John Kristoff
> Cc: [email-masked]
> Subject: Re: mboned: I-D
> ACTION:draft-ietf-mboned-addrdisc-problems-00.txt
> 
> 
> On Thu, 24 Mar 2005, Beau Williamson wrote:
> >
> > I'd like to see the following text marked with ">>" (or 
> something like it) 
> > added to the end of the following section at some point in 
> the near future.
> 
> I agree with the main thrust of what you're saying, and I'm OK with 
> adding some text like that.
> 
> John (K.) however thought it might still be a good idea.  Would you 
> (John, others) be OK with the text proposal (below)?  Any 
> wordsmithing?
> 
> 
> > 3.1  Locally Scoped Address Assignment by IANA
> >
> > If we ignore the first problem about local scoping, the 
> easiest mitigation 
> > technique might be having IANA assign locally scoped 
> addresses on FCFS basis 
> > (like UDP/TCP port numbers).  This could be done inside or 
> outside of 239/8.
> >
> > ...
> >
> >>> Having IANA suddenly begin assigning addresses in the 
> 239/8 space has the 
> > potential for causing serious impact to existing 
> organizations that have 
> > deployed multicast as this address space has, up to now, 
> been considered 
> > "private" multicast address much like RFC 1918 address 
> space for unicast. 
> > Existing organizations have made use of the 239/8 address 
> space for various 
> > private scope ranges under the assumption that this space 
> is "private" and 
> > would never be assigned. These organizations would have to 
> completely 
> > re-engineer their private network's internal scoping and 
> scope address range 
> > plans should IANA begin to assign addresses in the 239/8 
> space. The impact of 
> > this should be CAREFULLY considered and ALL OTHER methods 
> explored before 
> > adopting this approach.
> >
> > Beau
> >
> > At 3/23/2005 03:12 PM, [email-masked] wrote:
> >> A New Internet-Draft is available from the on-line Internet-Drafts 
> >> directories.
> >> This draft is a work item of the MBONE Deployment Working 
> Group of the 
> >> IETF.
> >> 
> >>         Title           : Lightweight Multicast Address 
> Discovery Problem 
> >> Space
> >>         Author(s)       : P. Savola
> >>         Filename        : 
> draft-ietf-mboned-addrdisc-problems-00.txt
> >>         Pages           : 10
> >>         Date            : 2005-3-23
> >> 
> >> Typically applications developers have requested static IANA
> >>    assignments for the applications, even if the applications would
> >>    typically be only used within a site, between 
> consenting sites, or
> >>    would not eventually even use multicast at all.  This 
> memo describes
> >>    this problem space, and summarizes a number of proposed 
> approaches to
> >>    mitigating these problems.
> >> 
> >> A URL for this Internet-Draft is:
> >> 
> http://www.ietf.org/internet-drafts/draft-ietf-mboned-addrdisc
> -problems-00.txt
> >> 
> >> To remove yourself from the I-D Announcement list, send a 
> message to
> >> [email-masked] with the word unsubscribe in 
> the body of the 
> >> message.
> >> You can also visit 
> https://www1.ietf.org/mailman/listinfo/I-D-announce
> >> to change your subscription settings.
> >> 
> >> 
> >> Internet-Drafts are also available by anonymous FTP. Login 
> with the 
> >> username
> >> "anonymous" and a password of your e-mail address. After 
> logging in,
> >> type "cd internet-drafts" and then
> >>         "get draft-ietf-mboned-addrdisc-problems-00.txt".
> >> 
> >> A list of Internet-Drafts directories can be found in
> >> http://www.ietf.org/shadow.html
> >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >> 
> >> 
> >> Internet-Drafts can also be obtained by e-mail.
> >> 
> >> Send a message to:
> >>         [email-masked].
> >> In the body type:
> >>         "FILE 
> /internet-drafts/draft-ietf-mboned-addrdisc-problems-00.txt".
> >> 
> >> NOTE:   The mail server at ietf.org can return the document in
> >>         MIME-encoded form by using the "mpack" utility.  
> To use this
> >>         feature, insert the command "ENCODING mime" before 
> the "FILE"
> >>         command.  To decode the response(s), you will need 
> "munpack" or
> >>         a MIME-compliant mail reader.  Different 
> MIME-compliant mail 
> >> readers
> >>         exhibit different behavior, especially when dealing with
> >>         "multipart" MIME messages (i.e. documents which 
> have been split
> >>         up into multiple messages), so check your local 
> documentation on
> >>         how to manipulate these messages.
> >> 
> >> 
> >> Below is the data which will enable a MIME compliant mail reader
> >> implementation to automatically retrieve the ASCII version of the
> >> Internet-Draft.
> >> 
> --------------------------------------------------------------
> -----------
> >> CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
> >> 
> --------------------------------------------------------------
> -----------
> >> In order to maintain computing infrastructure integrity, 
> Cisco Systems
> >> Enterprise Messaging Services and InfoSec teams have set a 
> mail policy
> >> disallowing executable attachments in email.
> >> 
> >> This message contained an executable attachment type that 
> is prohibited
> >> by this policy. The attachment has been removed from this 
> message and
> >> copied to quarantine by our systems. It will be held in 
> quarantine for
> >> seven days in the event that the content needs to be retrieved.
> >> 
> >> Please be aware many viruses attempt to look like 
> legitimate email or
> >> notifications from anti-virus systems. We will clearly 
> mark a seperation
> >> between our notifications and the original email as follows:
> >> 
> >>   "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION 
> TECHNOLOGY"
> >> 
> >> For further reference information about viruses and email antivirus
> >> efforts within Cisco, please visit:
> >> 
> >> http://wwwin.cisco.com/it/ems/services/antiviral
> >> 
> >> If your concern isn't addressed by the information in this 
> notification
> >> or the above web page, you may open a support request:
> >> 
> >> http://wwwin.cisco.com/support/
> >> 
> >> Select "Messaging", "Email-Related", "Mail Routing"
> >> 
> >> Please include in the text of your case the following information:
> >> 
> >> * Full headers of the message. Documentation on displaying the full
> >> headers is available at this URL:
> >> 
> >> http://wwwin.cisco.com/support/library/faqs/solution002471.html
> >> 
> >> * This unique quarantine identifier: j2O3J4J2021491
> >> 
> >> If the matter is urgent, you may follow up by calling one 
> of the below
> >> referenced numbers. Please make every effort to provide the above
> >> requested information via the support web tool prior to 
> calling as it
> >> will greatly aid the resolution of your issue.
> >> 
> >> Americas:
> >> 1 408 526 8888
> >> 
> >> Asiapac
> >> +61 2 8446 8888
> >> 
> >> EMEA
> >> +31 20 485 4888
> >> 
> >> Japan
> >> +81 3 5549 6888
> >> 
> >> US (Toll Free)
> >> 1| 800| 888| 8187| (ext.68888)
> >> 
> >> Thank you for your cooperation,
> >> 
> >> Enterprise Messaging Services
> >> Cisco Systems, Inc
> >> Content-Type: Multipart/Alternative; Boundary="OtherAccess"
> >> 
> >> 
> >> --OtherAccess--
> >
> 
> -- 
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> _______________________________________________________________
> user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
> web archive:  http://darkwing.uoregon.edu/~llynch/mboned/
> 

_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/