From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:30:42 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04289
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:30:41 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i090Jeu1015939
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 16:19:40 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i090JdIc015937
	for mboned-outgoing; Thu, 8 Jan 2004 16:19:39 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i090Jdu1015917
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 16:19:39 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i090Jd6f005373
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 16:19:39 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i090Jdnf005370;
	Thu, 8 Jan 2004 16:19:39 -0800
Date: Thu, 8 Jan 2004 16:19:39 -0800
Message-Id: <200401090019.i090Jdnf005370@m106.maoz.com>
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: IETF 59 (Seoul) Agenda items
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	It's that time again. Please forward agenda items for the
	MBONED session to me.

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:31:01 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04379
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:31:00 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08IIku1029862
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 10:18:46 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08IIkZK029860
	for mboned-outgoing; Thu, 8 Jan 2004 10:18:46 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08IIju1029791
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 10:18:45 -0800 (PST)
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com [171.71.163.14])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i08IIcVM013271;
	Thu, 8 Jan 2004 10:18:38 -0800 (PST)
Received: from cisco.com (jmeylor-frame5.cisco.com [10.19.252.142])
	by mira-sjc5-b.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id APB61265;
	Thu, 8 Jan 2004 10:18:36 -0800 (PST)
Message-ID: <3FFD9EFC.9000901@cisco.com>
Date: Thu, 08 Jan 2004 10:18:36 -0800
From: John Meylor <jmeylor@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Meyer <dmm@1-4-5.net>
CC: Toerless Eckert <eckert@cisco.com>, Scott Bradner <sob@harvard.edu>,
        mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
References: <20040108153158.GA25032@cisco.com> <20040108154942.18303C3D1A@newdev.harvard.edu> <20040108160835.GA28512@1-4-5.net> <20040108161004.GI29479@cisco.com> <20040108161459.GA28577@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

looks good dave.

  john

David Meyer wrote:
> 	Scott?
> 
> On Thu, Jan 08, 2004 at 08:10:04AM -0800, Toerless Eckert wrote:
> 
>>>perfect.
>>
> 
> 	If you agree, I want to get the change to Bert
> 	before/during (hopefully not after) the telechat...
> 
> 	Dave
> 
> 
>>>On Thu, Jan 08, 2004 at 08:08:35AM -0800, David Meyer wrote:
>>>
>>>>On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner wrote:
>>>>
>>>>>>                Scott helped me craft this goal/milestone
>>>>>>                language, and the reference to 1123/1123 didn't
>>>>>>                imply IPv4 or IPv6. Its just a reference. Scott,
>>>>>>                do we need to rev this to call out v6 (since
>>>>>>                neither is mentioned, I assumed it would be clear
>>>>>>                that it was both)?
>>>>>>
>>>>>>I'd suggest calling it out - assumptions of v6-ness are often wrong :-)
>>>>>
>>>>	OK. How about this:
>>>>
>>>>	The bullet in the "Description of Working Group" part of
>>>>	the new charter that said: 
>>>>
>>>>- Develop a roadmap informational RFC that describes the current
>>>>  IETF multicast architecture, including references to the
>>>>  relevent IETF documents and guidance for implementers and
>>>>  network operators along the line of RFC 1122/1123.
>>>>
>>>>	changes to:
>>>>
>>>>- Develop a roadmap informational RFC that describes the current
>>>>  IPv4 and IPv6 IETF multicast architectures, including
>>>>  references to the relevent IETF documents and guidance for
>>>>  implementers and network operators. 
>>>>
>>>>	I'm concerned as I believe the IESG is considering this
>>>>	today, so I want to close now and get it to Bert (if its
>>>>	not too late). 
>>>>
>>>>	Dave
>>>>
>>>>	
>>>>
>>>>This mail is probably spam.  The original message has been attached
>>>>along with this report, so you can recognize or block similar unwanted
>>>>mail in future.  See http://spamassassin.org/tag/ for more details.
>>>>
>>>>Content preview:  On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner
>>>>  wrote: >> Scott helped me craft this goal/milestone >> language, and
>>>>  the reference to 1123/1123 didn't >> imply IPv4 or IPv6. Its just a
>>>>  reference. Scott, >> do we need to rev this to call out v6 (since >>
>>>>  neither is mentioned, I assumed it would be clear >> that it was both)?
>>>>  >> >> I'd suggest calling it out - assumptions of v6-ness are often
>>>>  wrong :-) [...] 
>>>>
>>>>Content analysis details:   (-8.90 points, 5 required)
>>>>X_AUTH_WARNING     (-0.4 points) Has a X-Authentication-Warning header
>>>>IN_REP_TO          (-0.4 points) Has a In-Reply-To header
>>>>REFERENCES         (-0.0 points) Has a valid-looking References header
>>>>EMAIL_ATTRIBUTION  (-0.5 points) BODY: Contains what looks like an email attribution
>>>>BAYES_00           (-5.2 points) BODY: Bayesian classifier says spam probability is 0 to 1%
>>>>                   [score: 0.0071]
>>>>QUOTED_EMAIL_TEXT  (-0.4 points) BODY: Contains what looks like a quoted email text
>>>>USER_AGENT_MUTT    (-2.8 points) User-Agent header indicates a non-spam MUA (Mutt)
>>>>REPLY_WITH_QUOTES  (0.0 points)  Reply with quoted text
>>>>AWL                (0.8 points)  AWL: Auto-whitelist adjustment
>>>
>>>-- 
>>>Thanks
>>>   Toerless Eckert
>>>   
>>
> _______________________________________________________________
> 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/


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:38:28 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06435
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:38:28 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07LHbu1027766
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 7 Jan 2004 13:17:37 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i07LHbY6027765
	for mboned-outgoing; Wed, 7 Jan 2004 13:17:37 -0800 (PST)
Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07LHau2027751
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <mboned@lists.uoregon.edu>; Wed, 7 Jan 2004 13:17:36 -0800 (PST)
Received: from mcs.anl.gov (cliff.mcs.anl.gov [140.221.9.17])
	by network-services.uoregon.edu (8.12.8/8.12.8) with ESMTP id i07LHZhO003851
	for <mboned@network-services.uoregon.edu>; Wed, 7 Jan 2004 13:17:35 -0800
Received: from charge.mcs.anl.gov (vpnclient18136.mcs.anl.gov [140.221.18.136])
	by mcs.anl.gov (8.11.6/8.9.3) with ESMTP id i07LHH9249922;
	Wed, 7 Jan 2004 15:17:18 -0600
Message-Id: <5.2.0.9.2.20040107150333.02118d60@pop.mcs.anl.gov>
X-Sender: nickless@pop.mcs.anl.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 07 Jan 2004 15:17:15 -0600
To: Pekka Savola <pekkas@netcore.fi>
From: Bill Nickless <nickless@mcs.anl.gov>
Subject: Re: mboned: I-D
  ACTION:draft-ietf-mboned-ipv4-mcast-unusable-01.txt]
Cc: David Meyer <dmm@1-4-5.net>, mboned@network-services.uoregon.edu
In-Reply-To: <Pine.LNX.4.44.0312221455190.1967-100000@netcore.fi>
References: <20031210232247.GA540@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

Good afternoon Pekka,

I thought about your comments over the holiday break, and here's what I 
came up with:

Operationally, I think there are at least three places where access control 
lists should (by best practice) be installed: in the hosts/customer 
routers, at the edge of the AS (for PIM), and between ASes (for 
MSDP).  Using the "belt and suspenders" paranoid approach, I would suggest 
that the elements in each of these three access controls would be cumulative.

In other words:

The lines in Section 6 that refer to Section 7 should be installed on hosts 
(probably Ethernet kernel drivers) and on host-facing routers.

The lines in Section 6 that refer to Sections 7 and 8 should be installed 
on PIM routers that face other administrative domains.

The lines in Section 6 that refer to Sections 7, 8, and 9 should be 
installed on MSDP-speaking routers that peer with other administrative domains.

At first glance, I don't think this document is the place to include the 
above explanation; instead, I think that's better put in a BCP.

I was working on this document first because it was holding up some other 
RFCs, but expect to go through the IPv4 BCP shortly as well to include 
things like the above.

Does this make sense?  Should I go ahead and make the semi-editorial 
changes and re-issue, or... ?

At 03:23 PM 12/22/2003 +0200, Pekka Savola wrote:

>Comments below -- mainly, I have one big concern wrt. the structure of
>the document, which has an impact if we want this to be operationally
>useful, rather than just a reference of weird v4 multicast addresses.
>I personally think the former is closer to the target, but with
>clarifying text, the latter could also be OK..
>
>First question: this is for Informational, right?  It could also be
>BCP, but Info is fine by me and less paperwork besides :-).
>
>Second meta-question: would we want to look for unusable v6 multicast
>addresses as well?  Especially for the IGMP/MLD snoopers control plane
>clash perspective.  We'll have to tackle that at some point, but maybe
>it can wait a bit...
>
>Substantial
>-----------
>
>I'm questioning the structure of the document for the purpose of its
>usefulness.  Section 6 lists all the potentially bad (in some context)
>prefixes, and they are further describes in the next sections,
>including those that are completely unusable, those that should not be
>used interdomain, etc.
>
>It seems to me that while this serves a documentation purpose, the
>better way to structure these restrictions would be to write them
>like:
>
>6. Unusable Everywhere
>
>....
>
>7. Always Unusable in Interdomain
>
>....
>
>
>8. Miscellaneous
>
>(Note: actually I don't believe 232.0.0.0/8 and section 9 needs to be
>spelled out that much in this particular document.
>draft-ietf-mboned-ssm232-06.txt already pretty much includes about
>everything necessary....)
>
>-- that way, folks who want to take advantage of these, e.g., to
>create their multicast filters on routers based on the advice, don't
>have to go through a list of all addresses to find which they should
>block at their MSDP/interdomain borders, which should be used anywhere
>etc.
>
>Operationally one huge list is a maybe a good reference, but not
>really that useful beyond that.
>
>Thoughts about this approach?  (One doubt I have personally is
>whether it's possible to separate these addresses to these
>"useful categories" like "never useful" or "not useful in
>interdomain".
>
>
>Semi-editorial
>--------------
>
>13. References
>
>==> these need to be split to informative/normative.
>
>Editorial
>---------
>
>1. Status of this Memo
>2. Abstract
>3. Table of Contents
>
>==> these must be unnumbered sections
>
>4. Conventions used in this document
>
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>     document are to be interpreted as described in RFC-2119 [RFC2119].
>
>5. Background
>
>==> this should probably be renamed to "Introduction", edited
>slightly, and the conventions, above, should be moved at the end of
>this section.
>
>14. Author's Address
>
>  ==> it'd probably also be a good idea to include the standard IPR
>notice, Copyright Notice and ISOC acknowledgement notices after this
>section.
>
>
>_______________________________________________________________
>user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
>web archive:  http://darkwing.uoregon.edu/~llynch/mboned/

===
Bill Nickless    http://www.mcs.anl.gov/people/nickless      +1 630 252 7390
PGP:0E 0F 16 80 C5 B1 69 52 E1 44 1A A5 0E 1B 74 F7     nickless@mcs.anl.gov

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:38:35 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06457
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:38:34 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GnNu1007310
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:49:23 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08GnNe7007306
	for mboned-outgoing; Thu, 8 Jan 2004 08:49:23 -0800 (PST)
Received: from multicasttech.com (IDENT:root@lennon.multicasttech.com [63.105.122.7])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GnMu1007258
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:49:23 -0800 (PST)
Received: from [12.161.102.11] (account marshall_eubanks HELO multicasttech.com)
  by multicasttech.com (CommuniGate Pro SMTP 3.4.8)
  with ESMTP-TLS id 2132109; Thu, 08 Jan 2004 11:49:18 -0500
Date: Thu, 8 Jan 2004 11:49:22 -0500
Subject: Re: mboned: Please comment (in the event you didn't see this)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v553)
Cc: Scott Bradner <sob@harvard.edu>, eckert@cisco.com,
        mboned@lists.uoregon.edu
To: David Meyer <dmm@1-4-5.net>
From: Marshall Eubanks <tme@multicasttech.com>
In-Reply-To: <20040108160835.GA28512@1-4-5.net>
Message-Id: <9C713D56-41FA-11D8-BB95-003065FC3726@multicasttech.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.553)
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

I like the new text.

On Thursday, January 8, 2004, at 11:08 AM, David Meyer wrote:

> On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner wrote:
>>>                 Scott helped me craft this goal/milestone
>>>                 language, and the reference to 1123/1123 didn't
>>>                 imply IPv4 or IPv6. Its just a reference. Scott,
>>>                 do we need to rev this to call out v6 (since
>>>                 neither is mentioned, I assumed it would be clear
>>>                 that it was both)?
>>>
>>> I'd suggest calling it out - assumptions of v6-ness are often wrong 
>>> :-)
>
> 	OK. How about this:
>
> 	The bullet in the "Description of Working Group" part of
> 	the new charter that said:
>
> - Develop a roadmap informational RFC that describes the current
>   IETF multicast architecture, including references to the
>   relevent IETF documents and guidance for implementers and
>   network operators along the line of RFC 1122/1123.
>
> 	changes to:
>
> - Develop a roadmap informational RFC that describes the current
>   IPv4 and IPv6 IETF multicast architectures, including
>   references to the relevent IETF documents and guidance for
>   implementers and network operators.
>
> 	I'm concerned as I believe the IESG is considering this
> 	today, so I want to close now and get it to Bert (if its
> 	not too late).
>
> 	Dave
>
> 	
> _______________________________________________________________
> user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
> web archive:  http://darkwing.uoregon.edu/~llynch/mboned/
>
                                  Regards
                                  Marshall Eubanks

T.M. Eubanks
e-mail : marshall.eubanks@telesuite.com
http://www.telesuite.com

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:40:22 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06755
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:40:21 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07KI7u1007695
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 7 Jan 2004 12:18:07 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i07KI7HR007691
	for mboned-outgoing; Wed, 7 Jan 2004 12:18:07 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07KI6u1007660
	for <mboned@lists.uoregon.edu>; Wed, 7 Jan 2004 12:18:06 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i07KI5T9008439;
	Wed, 7 Jan 2004 12:18:05 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i07KI5mj008436;
	Wed, 7 Jan 2004 12:18:05 -0800
Date: Wed, 7 Jan 2004 12:18:05 -0800
Message-Id: <200401072018.i07KI5mj008436@m106.maoz.com>
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
cc: sob@harvard.edu, bwijnen@lucent.com
Subject: mboned: draft-ietf-mboned-ipv4-mcast-unusable-01.txt
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Folks,

	Pekka had some fairly detailed comments on this one. I'm
	looking for some discussion on whether we need to
	reconsider the approach taken in the draft (noting that
	his was the only comment and the WG last call will end on
	01.09.2004).

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:47:51 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07951
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:47:51 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07LNau1007742
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 7 Jan 2004 13:23:36 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i07LNaBX007737
	for mboned-outgoing; Wed, 7 Jan 2004 13:23:36 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07LNZu1007716
	for <mboned@lists.uoregon.edu>; Wed, 7 Jan 2004 13:23:35 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i07LNWT9014563;
	Wed, 7 Jan 2004 13:23:32 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i07LNVgE014562;
	Wed, 7 Jan 2004 13:23:31 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jan 2004 13:23:31 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: draft-ietf-mboned-ipv4-mcast-unusable-01.txt
Message-ID: <20040107212331.GA14149@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Folks,

	First, sorry if this turns out to be a duplicate (my last
	posting seems to have disappeared). In any event, I had
	scheduled the WG last call on this document to end on
	01.09.2004. However, there was one set of comments from
	Pekka regarding, among other things, the structure of the
	document (see http://darkwing.uoregon.edu/~llynch/mboned/msg02187.html).
	What I'm looking for is some discussion on where we want
	to go with this one. We do have one draft that is hung on
	a normative reference to this (draft-ietf-mboned-msdp-deploy-04.txt), 
	so I would like to resolve this one.

	Comments to the list please.

	Thanks,

	Dave


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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:50:39 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08207
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:50:38 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08Flgu1010999
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 07:47:42 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08Flgce010997
	for mboned-outgoing; Thu, 8 Jan 2004 07:47:42 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08Flgu1010989
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 07:47:42 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i08Flb6f025883;
	Thu, 8 Jan 2004 07:47:37 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i08FlbTx025882;
	Thu, 8 Jan 2004 07:47:37 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@cisco.com using -f
Date: Thu, 8 Jan 2004 07:47:37 -0800
From: David Meyer <dmm@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
Cc: David Meyer <dmm@1-4-5.net>, mboned@lists.uoregon.edu, sob@harvard.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108154737.GA25860@cisco.com>
References: <20040107221009.GA5459@1-4-5.net> <20040108084143.GA29479@cisco.com> <20040108153158.GA25032@cisco.com> <20040108154414.GF29479@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108154414.GF29479@cisco.com>
User-Agent: Mutt/1.4.1i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Thu, Jan 08, 2004 at 07:44:14AM -0800, Toerless Eckert wrote:
>> On Thu, Jan 08, 2004 at 07:31:58AM -0800, David Meyer wrote:
>> > On Thu, Jan 08, 2004 at 12:41:43AM -0800, Toerless Eckert wrote:
>> > >> While MSDP MIB and rfc3171 are IPv4 only,
>> > 
>> > 	(i).	RFC 3307 (Allocation Guidelines for IPv6
>> > 		Multicast Addresses), is the analog to 3171 for
>> > 		IPv6. However, as you know it's a completely
>> > 		different problem.  
>> 
>> Right, eg: the two new work items MSDP MIB and rfc3171 nly
>> apply to IPv4 and the proposed WG work item text is ok and non-confusing.
>> 
>> > 	(ii).	The goal/milestone corresponding to what we were
>> > 		calling, for lack of a better name, IMDOC, is
>> > 
>> > 		- Develop a roadmap informational RFC that
>> > 		  describes the current IETF multicast
>> > 		  architecture, including references to the
>> > 		  relevent IETF documents and guidance for
>> > 		  implementers and network operators along the
>> > 		  line of RFC 1122/1123. 
>> > 
>> > 		Scott helped me craft this goal/milestone
>> > 		language, and the reference to 1123/1123 didn't
>> > 		imply IPv4 or IPv6. Its just a reference. Scott,
>> > 		do we need to rev this to call out v6 (since
>> > 		neither is mentioned, I assumed it would be clear
>> > 		that it was both)?
>> 
>> Well, _i_ was assuming that IMDOC is to cover both IPv4 and IPv6. If
>> we agree on this then i was just pointing out that the proposed
>> text may be misleading as it only refers to IPv4 only documents.
>> 
>> Am i correct to assume IMDOC is to cover both IPv4 and IPv6 ?

	Yes. I asked Scott for his opinion as too whether we need
	to call that out explicitly.

>> > 	BTW, who's spamassasin tagged the original message as
>> > 	spam? Cisco?
>> 
>> Sorry, no, just my personal one. Still haven't managed to configure
>> it really well, so i'm keeping a lot of debug output around, which i
>> sometimes forget to remove when replying.

	No worries. I was just wondering if I failed the standard
	SA.

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:50:40 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08220
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:50:39 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07MAAu1014582
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 7 Jan 2004 14:10:10 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i07MAAsN014581
	for mboned-outgoing; Wed, 7 Jan 2004 14:10:10 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i07MA9u1014570
	for <mboned@lists.uoregon.edu>; Wed, 7 Jan 2004 14:10:09 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i07MA96f005473
	for <mboned@lists.uoregon.edu>; Wed, 7 Jan 2004 14:10:09 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i07MA9QR005472
	for mboned@lists.uoregon.edu; Wed, 7 Jan 2004 14:10:09 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 7 Jan 2004 14:10:09 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040107221009.GA5459@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	One note: I have asked the secretariat to update the
	mailing list information. 

	Dave

----- Forwarded message from IESG Secretary <iesg-secretary@ietf.org> -----

>> From: IESG Secretary <iesg-secretary@ietf.org>
>> To: iesg@ietf.org, <iab@iab.org>, <dmm@1-4-5.net>, <sob@harvard.edu>
>> Subject: Internal WG Review: Recharter of MBONE Deployment (mboned)
>> Date: Fri, 2 Jan 2004 16:10:45 -0500 (EST)
>> 
>> 
>> A new charter for the MBONE Deployment working group (MBONED)
>> in the Operations and Management Area of the IETF is being considered.
>> The draft charter is provided below for your review and comment.
>> 
>> Review time is one week.
>> 
>> The IETF Secretariat
>> 
>> MBONE Deployment (mboned)
>> --------------------------------------------------
>> Note: The charter for MBONED is included below.
>> However, to assist you in your review, the changes from the previous
>> version as presented to the Secretariat by Bert Wijnen are as follows:
>> 1. The Goals and Milestones have been updated.
>> 2. Three additional activities have been added to the list. they are:
>> 
>>    - Update RFC 3171/BCP 51 based on experience.
>> 
>>    - Develop a roadmap informational RFC that describes the current
>>      IETF multicast architecture, including references to the
>>      relevent IETF documents and guidance for implementers and
>>      network operators along the line of RFC 1122/1123.
>> 
>>    - Complete the MSDP MIB
>> 
>> -------------------------------------------------
>> 
>>  Current Status: Active Working Group
>> 
>>  Chair(s):
>>      David Meyer  <dmm@1-4-5.net>
>> 
>>  Operations and Management Area Director(s):
>>      Bert Wijnen  <bwijnen@lucent.com>
>> 
>>  Operations and Management Area Advisor:
>>      Bert Wijnen  <bwijnen@lucent.com>
>> 
>>  Technical Advisor(s):
>>      Scott Bradner  <sob@harvard.edu>
>> 
>>  Mailing Lists:
>>      General Discussion:mboned@ns.uoregon.edu
>>      To Subscribe:      majordomo@ns.uoregon.edu
>>      Archive:           ftp://ftp.uoregon.edu/mailing-lists/mboned*
>> 
>> Description of Working Group:
>> 
>> The MBONE Deployment Working Group is a forum for coordinating
>> the deployment, engineering, and operation of multicast routing
>> protocols and procedures in the global Internet. This activity will
>> include, but not be limited to:
>> 
>> - Documenting deployment of multicast routing in the global Internet.
>> 
>> - Receive regular reports on the current state of the deployment of
>>   multicast technology. Create "practice and experience" documents that
>>   capture the experience of those who have deployed and are deploying
>>   various multicast technologies.
>> 
>> - Based on reports and other information, provide feedback to other
>>   relevant working groups.
>> 
>> - Develop mechanisms and procedures for sharing operational
>>   information to aid in operation of the multicast backbones and
>>   interconnects.
>> 
>> - Update RFC 3171/BCP 51 based on experience.
>> 
>> - Develop a roadmap informational RFC that describes the current
>>   IETF multicast architecture, including references to the
>>   relevent IETF documents and guidance for implementers and
>>   network operators along the line of RFC 1122/1123.
>> 
>> - Complete the MSDP MIB
>> 
>> This is not meant to be a protocol development Working Group.
>> 
>> Goals and Milestones:
>> 
>> Done Submit I-D on inter-provider coordination of the deployment of
>> pruning mrouteds.
>> Done Establish initial charter, goals, and long-term group agenda.
>> Done Submit I-D outlining requirements for the existing MBONE
>> infrastructure.
>> Done Submit I-D specifying the use of administratively scoped multicast
>> addresses (RFC 2365)
>> Done Submit I-D specifying the use of native multicast where appropriate
>> (e.g. exchange points).
>> Done Submit I-D on IP Multicast and Firewalls (RFC 2588)
>> Done Submit I-D specifying static allocations in 233/8 (RFC 3180)
>> Done Submit I-D on debugging multicast problems.
>> Done Submit final version of scope zone announcement protocol (MZAP RFC
>> 2776)
>> Done Submit final version of scoped address discovery protocol (SADP)
>> Done Submit I-D describing ISP multicast deployment practices
>> Done Submit I-D, with RPS WG, on extensions to RPSL to describe multicast
>> routing policy.
>> Done Submit I-D describing extended allocations in 233/8 (RFC 3138)
>> Done Submit I-D describing IANA Guidelines for IPv4 Multicast Address
>> Assignments (RFC 3171)
>> Done Submit I-D describing IP Multicast Applications issues (RFC 3170)
>> Done Submit I-D describing Anycast (RP) mechanism (RFC 3446)
>> Done Submit I-D describing Source-Specific Protocol Independent Multicast
>> in 232/8
>> Done Submit I-D describing MSDP Deployment Scenarios
>> Done Submit I-D describing IPv4 Multicast Unusable Group And Source
>> Addresses
>> Done Submit I-D describing Embedded RP for IPv6 Multicast Address
>> 
>> Apr 04 Submit I-D on PIM-SM Multicast Routing Security Issues
>> 
>> May 04 Submit I-D on IPv4/IPv6 multicast co-existence
>>        issues and strategies for IPv4 multicast and IPv6 multicast.
>> 
>> June 04 Update IANA Guidelines for IPv4 Multicast Address
>>         Assignments (RFC 3171/BCP 51)
>> 
>> Jun 04 Submit PIM-SM Multicast Routing Security Issues
>>        to IESG for Informational
>> 
>> June 04 Submit MSDP MIB to IESG for Experimental
>> 
>> Aug 04 Submit IPv4 multicast address allocation procedures IESG for BCP
>> 
>> Aug 04 Submit IPv4/v6 co-existence strategies to IESG for Informational
>> 
>> Aug 04 Submit multicast roadmap/reference architecture
>>        document to IESG for Informational
>> 

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:53:49 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08352
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:53:49 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GESu1000587
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:14:28 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08GESUX000579
	for mboned-outgoing; Thu, 8 Jan 2004 08:14:28 -0800 (PST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GERu1000473
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:14:28 -0800 (PST)
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 4157EC3E7F; Thu,  8 Jan 2004 11:14:22 -0500 (EST)
To: dmm@1-4-5.net, sob@harvard.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Cc: eckert@cisco.com, mboned@lists.uoregon.edu
In-Reply-To: <20040108160835.GA28512@1-4-5.net>
Message-Id: <20040108161422.4157EC3E7F@newdev.harvard.edu>
Date: Thu,  8 Jan 2004 11:14:22 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

- Develop a roadmap informational RFC that describes the current
  IPv4 and IPv6 IETF multicast architectures, including
  references to the relevent IETF documents and guidance for
  implementers and network operators. 

that looks good to me

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:53:50 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08369
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:53:50 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08Fnmu1012045
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 07:49:49 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08FnmcS012044
	for mboned-outgoing; Thu, 8 Jan 2004 07:49:48 -0800 (PST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08Fnlu1012001
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 07:49:48 -0800 (PST)
Received: by newdev.harvard.edu (Postfix, from userid 501)
	id 18303C3D1A; Thu,  8 Jan 2004 10:49:42 -0500 (EST)
To: dmm@1-4-5.net, eckert@cisco.com
Subject: Re: mboned: Please comment (in the event you didn't see this)
Cc: mboned@lists.uoregon.edu, sob@harvard.edu
In-Reply-To: <20040108153158.GA25032@cisco.com>
Message-Id: <20040108154942.18303C3D1A@newdev.harvard.edu>
Date: Thu,  8 Jan 2004 10:49:42 -0500 (EST)
From: sob@harvard.edu (Scott Bradner)
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

                Scott helped me craft this goal/milestone
                language, and the reference to 1123/1123 didn't
                imply IPv4 or IPv6. Its just a reference. Scott,
                do we need to rev this to call out v6 (since
                neither is mentioned, I assumed it would be clear
                that it was both)?

I'd suggest calling it out - assumptions of v6-ness are often wrong :-)

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:53:51 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08372
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:53:50 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08G8fu1026119
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:08:41 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08G8foH026115
	for mboned-outgoing; Thu, 8 Jan 2004 08:08:41 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08G8eu1026103
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:08:40 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i08G8Z6f028541;
	Thu, 8 Jan 2004 08:08:35 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i08G8ZJA028540;
	Thu, 8 Jan 2004 08:08:35 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 8 Jan 2004 08:08:35 -0800
From: David Meyer <dmm@1-4-5.net>
To: Scott Bradner <sob@harvard.edu>
Cc: eckert@cisco.com, mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108160835.GA28512@1-4-5.net>
References: <20040108153158.GA25032@cisco.com> <20040108154942.18303C3D1A@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108154942.18303C3D1A@newdev.harvard.edu>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner wrote:
>>                 Scott helped me craft this goal/milestone
>>                 language, and the reference to 1123/1123 didn't
>>                 imply IPv4 or IPv6. Its just a reference. Scott,
>>                 do we need to rev this to call out v6 (since
>>                 neither is mentioned, I assumed it would be clear
>>                 that it was both)?
>> 
>> I'd suggest calling it out - assumptions of v6-ness are often wrong :-)

	OK. How about this:

	The bullet in the "Description of Working Group" part of
	the new charter that said: 

- Develop a roadmap informational RFC that describes the current
  IETF multicast architecture, including references to the
  relevent IETF documents and guidance for implementers and
  network operators along the line of RFC 1122/1123.

	changes to:

- Develop a roadmap informational RFC that describes the current
  IPv4 and IPv6 IETF multicast architectures, including
  references to the relevent IETF documents and guidance for
  implementers and network operators. 

	I'm concerned as I believe the IESG is considering this
	today, so I want to close now and get it to Bert (if its
	not too late). 

	Dave

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:56:35 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08676
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:56:34 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GFUu1001777
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:15:30 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08GFUG9001771
	for mboned-outgoing; Thu, 8 Jan 2004 08:15:30 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GFTu1001703
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:15:29 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i08GFP6f028637;
	Thu, 8 Jan 2004 08:15:25 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i08GFPrE028636;
	Thu, 8 Jan 2004 08:15:25 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 8 Jan 2004 08:15:25 -0800
From: David Meyer <dmm@1-4-5.net>
To: Scott Bradner <sob@harvard.edu>
Cc: eckert@cisco.com, mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108161525.GA28630@1-4-5.net>
References: <20040108160835.GA28512@1-4-5.net> <20040108161422.4157EC3E7F@newdev.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108161422.4157EC3E7F@newdev.harvard.edu>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Thu, Jan 08, 2004 at 11:14:22AM -0500, Scott Bradner wrote:
>> - Develop a roadmap informational RFC that describes the current
>>   IPv4 and IPv6 IETF multicast architectures, including
>>   references to the relevent IETF documents and guidance for
>>   implementers and network operators. 
>> 
>> that looks good to me

Sorry, filtering. I'll ship to Bert....

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:56:35 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08689
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:56:35 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08FiNu1009352
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 07:44:23 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08FiNE8009351
	for mboned-outgoing; Thu, 8 Jan 2004 07:44:23 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08FiMu1009261
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 07:44:22 -0800 (PST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i08FiElx020752;
	Thu, 8 Jan 2004 07:44:14 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id HAA02634;
	Thu, 8 Jan 2004 07:44:14 -0800 (PST)
Date: Thu, 8 Jan 2004 07:44:14 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Meyer <dmm@1-4-5.net>
Cc: mboned@lists.uoregon.edu, sob@harvard.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108154414.GF29479@cisco.com>
References: <20040107221009.GA5459@1-4-5.net> <20040108084143.GA29479@cisco.com> <20040108153158.GA25032@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108153158.GA25032@cisco.com>
User-Agent: Mutt/1.4i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Thu, Jan 08, 2004 at 07:31:58AM -0800, David Meyer wrote:
> On Thu, Jan 08, 2004 at 12:41:43AM -0800, Toerless Eckert wrote:
> >> While MSDP MIB and rfc3171 are IPv4 only,
> 
> 	(i).	RFC 3307 (Allocation Guidelines for IPv6
> 		Multicast Addresses), is the analog to 3171 for
> 		IPv6. However, as you know it's a completely
> 		different problem.  

Right, eg: the two new work items MSDP MIB and rfc3171 nly
apply to IPv4 and the proposed WG work item text is ok and non-confusing.

> 	(ii).	The goal/milestone corresponding to what we were
> 		calling, for lack of a better name, IMDOC, is
> 
> 		- Develop a roadmap informational RFC that
> 		  describes the current IETF multicast
> 		  architecture, including references to the
> 		  relevent IETF documents and guidance for
> 		  implementers and network operators along the
> 		  line of RFC 1122/1123. 
> 
> 		Scott helped me craft this goal/milestone
> 		language, and the reference to 1123/1123 didn't
> 		imply IPv4 or IPv6. Its just a reference. Scott,
> 		do we need to rev this to call out v6 (since
> 		neither is mentioned, I assumed it would be clear
> 		that it was both)?

Well, _i_ was assuming that IMDOC is to cover both IPv4 and IPv6. If
we agree on this then i was just pointing out that the proposed
text may be misleading as it only refers to IPv4 only documents.

Am i correct to assume IMDOC is to cover both IPv4 and IPv6 ?

> 	BTW, who's spamassasin tagged the original message as
> 	spam? Cisco?

Sorry, no, just my personal one. Still haven't managed to configure
it really well, so i'm keeping a lot of debug output around, which i
sometimes forget to remove when replying.

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:56:37 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08706
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:56:36 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GACu1027248
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:10:12 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08GACNO027247
	for mboned-outgoing; Thu, 8 Jan 2004 08:10:12 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GACu1027199
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:10:12 -0800 (PST)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 08 Jan 2004 08:17:59 +0000
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i08GA4GN025917;
	Thu, 8 Jan 2004 08:10:04 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id IAA07526;
	Thu, 8 Jan 2004 08:10:04 -0800 (PST)
Date: Thu, 8 Jan 2004 08:10:04 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Meyer <dmm@1-4-5.net>
Cc: Scott Bradner <sob@harvard.edu>, mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108161004.GI29479@cisco.com>
References: <20040108153158.GA25032@cisco.com> <20040108154942.18303C3D1A@newdev.harvard.edu> <20040108160835.GA28512@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108160835.GA28512@1-4-5.net>
User-Agent: Mutt/1.4i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

perfect.

On Thu, Jan 08, 2004 at 08:08:35AM -0800, David Meyer wrote:
> On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner wrote:
> >>                 Scott helped me craft this goal/milestone
> >>                 language, and the reference to 1123/1123 didn't
> >>                 imply IPv4 or IPv6. Its just a reference. Scott,
> >>                 do we need to rev this to call out v6 (since
> >>                 neither is mentioned, I assumed it would be clear
> >>                 that it was both)?
> >> 
> >> I'd suggest calling it out - assumptions of v6-ness are often wrong :-)
> 
> 	OK. How about this:
> 
> 	The bullet in the "Description of Working Group" part of
> 	the new charter that said: 
> 
> - Develop a roadmap informational RFC that describes the current
>   IETF multicast architecture, including references to the
>   relevent IETF documents and guidance for implementers and
>   network operators along the line of RFC 1122/1123.
> 
> 	changes to:
> 
> - Develop a roadmap informational RFC that describes the current
>   IPv4 and IPv6 IETF multicast architectures, including
>   references to the relevent IETF documents and guidance for
>   implementers and network operators. 
> 
> 	I'm concerned as I believe the IESG is considering this
> 	today, so I want to close now and get it to Bert (if its
> 	not too late). 
> 
> 	Dave
> 
> 	
> 
> This mail is probably spam.  The original message has been attached
> along with this report, so you can recognize or block similar unwanted
> mail in future.  See http://spamassassin.org/tag/ for more details.
> 
> Content preview:  On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner
>   wrote: >> Scott helped me craft this goal/milestone >> language, and
>   the reference to 1123/1123 didn't >> imply IPv4 or IPv6. Its just a
>   reference. Scott, >> do we need to rev this to call out v6 (since >>
>   neither is mentioned, I assumed it would be clear >> that it was both)?
>   >> >> I'd suggest calling it out - assumptions of v6-ness are often
>   wrong :-) [...] 
> 
> Content analysis details:   (-8.90 points, 5 required)
> X_AUTH_WARNING     (-0.4 points) Has a X-Authentication-Warning header
> IN_REP_TO          (-0.4 points) Has a In-Reply-To header
> REFERENCES         (-0.0 points) Has a valid-looking References header
> EMAIL_ATTRIBUTION  (-0.5 points) BODY: Contains what looks like an email attribution
> BAYES_00           (-5.2 points) BODY: Bayesian classifier says spam probability is 0 to 1%
>                    [score: 0.0071]
> QUOTED_EMAIL_TEXT  (-0.4 points) BODY: Contains what looks like a quoted email text
> USER_AGENT_MUTT    (-2.8 points) User-Agent header indicates a non-spam MUA (Mutt)
> REPLY_WITH_QUOTES  (0.0 points)  Reply with quoted text
> AWL                (0.8 points)  AWL: Auto-whitelist adjustment

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:56:38 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08727
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:56:37 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08FW3u1003166
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 07:32:03 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08FW3x3003165
	for mboned-outgoing; Thu, 8 Jan 2004 07:32:03 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08FW2u1003151
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 07:32:02 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i08FVw6f025260;
	Thu, 8 Jan 2004 07:31:58 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i08FVwfs025259;
	Thu, 8 Jan 2004 07:31:58 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 8 Jan 2004 07:31:58 -0800
From: David Meyer <dmm@1-4-5.net>
To: Toerless Eckert <eckert@cisco.com>
Cc: mboned@lists.uoregon.edu, sob@harvard.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108153158.GA25032@cisco.com>
References: <20040107221009.GA5459@1-4-5.net> <20040108084143.GA29479@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108084143.GA29479@cisco.com>
User-Agent: Mutt/1.4.1i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Toreless,

On Thu, Jan 08, 2004 at 12:41:43AM -0800, Toerless Eckert wrote:
>> While MSDP MIB and rfc3171 are IPv4 only,

	(i).	RFC 3307 (Allocation Guidelines for IPv6
		Multicast Addresses), is the analog to 3171 for
		IPv6. However, as you know it's a completely
		different problem.  

>> i think the IMDOC effort must of course also include IPv6, but
>> given that rfc1112 does address IPv4, it would be good to add
>> something like "for both IPv4 and IPv6" to the end of the
>> roadmap RFC goal statement. 

	(ii).	The goal/milestone corresponding to what we were
		calling, for lack of a better name, IMDOC, is

		- Develop a roadmap informational RFC that
		  describes the current IETF multicast
		  architecture, including references to the
		  relevent IETF documents and guidance for
		  implementers and network operators along the
		  line of RFC 1122/1123. 

		Scott helped me craft this goal/milestone
		language, and the reference to 1123/1123 didn't
		imply IPv4 or IPv6. Its just a reference. Scott,
		do we need to rev this to call out v6 (since
		neither is mentioned, I assumed it would be clear
		that it was both)?


	BTW, who's spamassasin tagged the original message as
	spam? Cisco?

	Dave


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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:56:39 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08743
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:56:38 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GF5u1001146
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 08:15:05 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i08GF5Ku001143
	for mboned-outgoing; Thu, 8 Jan 2004 08:15:05 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i08GF4u1001130
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 08:15:04 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i08GEx6f028596;
	Thu, 8 Jan 2004 08:14:59 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i08GExY2028595;
	Thu, 8 Jan 2004 08:14:59 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 8 Jan 2004 08:14:59 -0800
From: David Meyer <dmm@1-4-5.net>
To: Toerless Eckert <eckert@cisco.com>
Cc: David Meyer <dmm@1-4-5.net>, Scott Bradner <sob@harvard.edu>,
        mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108161459.GA28577@cisco.com>
References: <20040108153158.GA25032@cisco.com> <20040108154942.18303C3D1A@newdev.harvard.edu> <20040108160835.GA28512@1-4-5.net> <20040108161004.GI29479@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040108161004.GI29479@cisco.com>
User-Agent: Mutt/1.4.1i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Scott?

On Thu, Jan 08, 2004 at 08:10:04AM -0800, Toerless Eckert wrote:
>> perfect.

	If you agree, I want to get the change to Bert
	before/during (hopefully not after) the telechat...

	Dave

>> 
>> On Thu, Jan 08, 2004 at 08:08:35AM -0800, David Meyer wrote:
>> > On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner wrote:
>> > >>                 Scott helped me craft this goal/milestone
>> > >>                 language, and the reference to 1123/1123 didn't
>> > >>                 imply IPv4 or IPv6. Its just a reference. Scott,
>> > >>                 do we need to rev this to call out v6 (since
>> > >>                 neither is mentioned, I assumed it would be clear
>> > >>                 that it was both)?
>> > >> 
>> > >> I'd suggest calling it out - assumptions of v6-ness are often wrong :-)
>> > 
>> > 	OK. How about this:
>> > 
>> > 	The bullet in the "Description of Working Group" part of
>> > 	the new charter that said: 
>> > 
>> > - Develop a roadmap informational RFC that describes the current
>> >   IETF multicast architecture, including references to the
>> >   relevent IETF documents and guidance for implementers and
>> >   network operators along the line of RFC 1122/1123.
>> > 
>> > 	changes to:
>> > 
>> > - Develop a roadmap informational RFC that describes the current
>> >   IPv4 and IPv6 IETF multicast architectures, including
>> >   references to the relevent IETF documents and guidance for
>> >   implementers and network operators. 
>> > 
>> > 	I'm concerned as I believe the IESG is considering this
>> > 	today, so I want to close now and get it to Bert (if its
>> > 	not too late). 
>> > 
>> > 	Dave
>> > 
>> > 	
>> > 
>> > This mail is probably spam.  The original message has been attached
>> > along with this report, so you can recognize or block similar unwanted
>> > mail in future.  See http://spamassassin.org/tag/ for more details.
>> > 
>> > Content preview:  On Thu, Jan 08, 2004 at 10:49:42AM -0500, Scott Bradner
>> >   wrote: >> Scott helped me craft this goal/milestone >> language, and
>> >   the reference to 1123/1123 didn't >> imply IPv4 or IPv6. Its just a
>> >   reference. Scott, >> do we need to rev this to call out v6 (since >>
>> >   neither is mentioned, I assumed it would be clear >> that it was both)?
>> >   >> >> I'd suggest calling it out - assumptions of v6-ness are often
>> >   wrong :-) [...] 
>> > 
>> > Content analysis details:   (-8.90 points, 5 required)
>> > X_AUTH_WARNING     (-0.4 points) Has a X-Authentication-Warning header
>> > IN_REP_TO          (-0.4 points) Has a In-Reply-To header
>> > REFERENCES         (-0.0 points) Has a valid-looking References header
>> > EMAIL_ATTRIBUTION  (-0.5 points) BODY: Contains what looks like an email attribution
>> > BAYES_00           (-5.2 points) BODY: Bayesian classifier says spam probability is 0 to 1%
>> >                    [score: 0.0071]
>> > QUOTED_EMAIL_TEXT  (-0.4 points) BODY: Contains what looks like a quoted email text
>> > USER_AGENT_MUTT    (-2.8 points) User-Agent header indicates a non-spam MUA (Mutt)
>> > REPLY_WITH_QUOTES  (0.0 points)  Reply with quoted text
>> > AWL                (0.8 points)  AWL: Auto-whitelist adjustment
>> 
>> -- 
>> Thanks
>>    Toerless Eckert
>>    
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


From owner-mboned@lists.uoregon.edu  Fri Jan  9 10:58:12 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09202
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 10:58:11 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i088fqu1017358
	for <mboned-outgoing@darkwing.uoregon.edu>; Thu, 8 Jan 2004 00:41:52 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i088fqw6017357
	for mboned-outgoing; Thu, 8 Jan 2004 00:41:52 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i088fpu1017094
	for <mboned@lists.uoregon.edu>; Thu, 8 Jan 2004 00:41:51 -0800 (PST)
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i088fiQu012671;
	Thu, 8 Jan 2004 00:41:44 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id AAA19392;
	Thu, 8 Jan 2004 00:41:43 -0800 (PST)
Date: Thu, 8 Jan 2004 00:41:43 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Meyer <dmm@1-4-5.net>
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040108084143.GA29479@cisco.com>
References: <20040107221009.GA5459@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040107221009.GA5459@1-4-5.net>
User-Agent: Mutt/1.4i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

While MSDP MIB and rfc3171 are IPv4 only, i think the IMDOC effort
must of course also include IPv6, but given that rfc1112 does only
address IPv4, it would be good to add something like "for both IPv4
and IPv6" to the end of the roadmap RFC goal statement.

On Wed, Jan 07, 2004 at 02:10:09PM -0800, David Meyer wrote:
> 	One note: I have asked the secretariat to update the
> 	mailing list information. 
> 
> 	Dave
> 
> ----- Forwarded message from IESG Secretary <iesg-secretary@ietf.org> -----
> 
> >> From: IESG Secretary <iesg-secretary@ietf.org>
> >> To: iesg@ietf.org, <iab@iab.org>, <dmm@1-4-5.net>, <sob@harvard.edu>
> >> Subject: Internal WG Review: Recharter of MBONE Deployment (mboned)
> >> Date: Fri, 2 Jan 2004 16:10:45 -0500 (EST)
> >> 
> >> 
> >> A new charter for the MBONE Deployment working group (MBONED)
> >> in the Operations and Management Area of the IETF is being considered.
> >> The draft charter is provided below for your review and comment.
> >> 
> >> Review time is one week.
> >> 
> >> The IETF Secretariat
> >> 
> >> MBONE Deployment (mboned)
> >> --------------------------------------------------
> >> Note: The charter for MBONED is included below.
> >> However, to assist you in your review, the changes from the previous
> >> version as presented to the Secretariat by Bert Wijnen are as follows:
> >> 1. The Goals and Milestones have been updated.
> >> 2. Three additional activities have been added to the list. they are:
> >> 
> >>    - Update RFC 3171/BCP 51 based on experience.
> >> 
> >>    - Develop a roadmap informational RFC that describes the current
> >>      IETF multicast architecture, including references to the
> >>      relevent IETF documents and guidance for implementers and
> >>      network operators along the line of RFC 1122/1123.
> >> 
> >>    - Complete the MSDP MIB
> >> 
> >> -------------------------------------------------
> >> 
> >>  Current Status: Active Working Group
> >> 
> >>  Chair(s):
> >>      David Meyer  <dmm@1-4-5.net>
> >> 
> >>  Operations and Management Area Director(s):
> >>      Bert Wijnen  <bwijnen@lucent.com>
> >> 
> >>  Operations and Management Area Advisor:
> >>      Bert Wijnen  <bwijnen@lucent.com>
> >> 
> >>  Technical Advisor(s):
> >>      Scott Bradner  <sob@harvard.edu>
> >> 
> >>  Mailing Lists:
> >>      General Discussion:mboned@ns.uoregon.edu
> >>      To Subscribe:      majordomo@ns.uoregon.edu
> >>      Archive:           ftp://ftp.uoregon.edu/mailing-lists/mboned*
> >> 
> >> Description of Working Group:
> >> 
> >> The MBONE Deployment Working Group is a forum for coordinating
> >> the deployment, engineering, and operation of multicast routing
> >> protocols and procedures in the global Internet. This activity will
> >> include, but not be limited to:
> >> 
> >> - Documenting deployment of multicast routing in the global Internet.
> >> 
> >> - Receive regular reports on the current state of the deployment of
> >>   multicast technology. Create "practice and experience" documents that
> >>   capture the experience of those who have deployed and are deploying
> >>   various multicast technologies.
> >> 
> >> - Based on reports and other information, provide feedback to other
> >>   relevant working groups.
> >> 
> >> - Develop mechanisms and procedures for sharing operational
> >>   information to aid in operation of the multicast backbones and
> >>   interconnects.
> >> 
> >> - Update RFC 3171/BCP 51 based on experience.
> >> 
> >> - Develop a roadmap informational RFC that describes the current
> >>   IETF multicast architecture, including references to the
> >>   relevent IETF documents and guidance for implementers and
> >>   network operators along the line of RFC 1122/1123.
> >> 
> >> - Complete the MSDP MIB
> >> 
> >> This is not meant to be a protocol development Working Group.
> >> 
> >> Goals and Milestones:
> >> 
> >> Done Submit I-D on inter-provider coordination of the deployment of
> >> pruning mrouteds.
> >> Done Establish initial charter, goals, and long-term group agenda.
> >> Done Submit I-D outlining requirements for the existing MBONE
> >> infrastructure.
> >> Done Submit I-D specifying the use of administratively scoped multicast
> >> addresses (RFC 2365)
> >> Done Submit I-D specifying the use of native multicast where appropriate
> >> (e.g. exchange points).
> >> Done Submit I-D on IP Multicast and Firewalls (RFC 2588)
> >> Done Submit I-D specifying static allocations in 233/8 (RFC 3180)
> >> Done Submit I-D on debugging multicast problems.
> >> Done Submit final version of scope zone announcement protocol (MZAP RFC
> >> 2776)
> >> Done Submit final version of scoped address discovery protocol (SADP)
> >> Done Submit I-D describing ISP multicast deployment practices
> >> Done Submit I-D, with RPS WG, on extensions to RPSL to describe multicast
> >> routing policy.
> >> Done Submit I-D describing extended allocations in 233/8 (RFC 3138)
> >> Done Submit I-D describing IANA Guidelines for IPv4 Multicast Address
> >> Assignments (RFC 3171)
> >> Done Submit I-D describing IP Multicast Applications issues (RFC 3170)
> >> Done Submit I-D describing Anycast (RP) mechanism (RFC 3446)
> >> Done Submit I-D describing Source-Specific Protocol Independent Multicast
> >> in 232/8
> >> Done Submit I-D describing MSDP Deployment Scenarios
> >> Done Submit I-D describing IPv4 Multicast Unusable Group And Source
> >> Addresses
> >> Done Submit I-D describing Embedded RP for IPv6 Multicast Address
> >> 
> >> Apr 04 Submit I-D on PIM-SM Multicast Routing Security Issues
> >> 
> >> May 04 Submit I-D on IPv4/IPv6 multicast co-existence
> >>        issues and strategies for IPv4 multicast and IPv6 multicast.
> >> 
> >> June 04 Update IANA Guidelines for IPv4 Multicast Address
> >>         Assignments (RFC 3171/BCP 51)
> >> 
> >> Jun 04 Submit PIM-SM Multicast Routing Security Issues
> >>        to IESG for Informational
> >> 
> >> June 04 Submit MSDP MIB to IESG for Experimental
> >> 
> >> Aug 04 Submit IPv4 multicast address allocation procedures IESG for BCP
> >> 
> >> Aug 04 Submit IPv4/v6 co-existence strategies to IESG for Informational
> >> 
> >> Aug 04 Submit multicast roadmap/reference architecture
> >>        document to IESG for Informational
> >> 
> 
> ----- End forwarded message -----
> _______________________________________________________________
> user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
> web archive:  http://darkwing.uoregon.edu/~llynch/mboned/
> 
> This mail is probably spam.  The original message has been attached
> along with this report, so you can recognize or block similar unwanted
> mail in future.  See http://spamassassin.org/tag/ for more details.
> 
> Content preview:  One note: I have asked the secretariat to update the
>   mailing list information. Dave ----- Forwarded message from IESG
>   Secretary <iesg-secretary@ietf.org> ----- [...] 
> 
> Content analysis details:   (-8.40 points, 5 required)
> X_AUTH_WARNING     (-0.4 points) Has a X-Authentication-Warning header
> BAYES_00           (-5.2 points) BODY: Bayesian classifier says spam probability is 0 to 1%
>                    [score: 0.0063]
> QUOTED_EMAIL_TEXT  (-0.4 points) BODY: Contains what looks like a quoted email text
> USER_AGENT_MUTT    (-2.8 points) User-Agent header indicates a non-spam MUA (Mutt)
> AWL                (0.4 points)  AWL: Auto-whitelist adjustment

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 11:24:58 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11155
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 11:24:57 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09GLmu1007661
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 08:21:48 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09GLmJ1007659
	for mboned-outgoing; Fri, 9 Jan 2004 08:21:48 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09GLlu1007653
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 08:21:47 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i09GLl6f010309;
	Fri, 9 Jan 2004 08:21:47 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i09GLlmQ010308;
	Fri, 9 Jan 2004 08:21:47 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 9 Jan 2004 08:21:47 -0800
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040109162147.GA10255@1-4-5.net>
References: <20040107221009.GA5459@1-4-5.net> <Pine.LNX.4.44.0401091615060.29733-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0401091615060.29733-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Pekka,

	Thanks for the thoughtful comments.

On Fri, Jan 09, 2004 at 04:31:14PM +0200, Pekka Savola wrote:
>> Hi,
>> 
>> This has probably already been shipped, but a few comments so they can 
>> be addressed in the next revision..

	Yep. Let's see if I can answer your questions though...

>> 
>> I assume by "Submit I-D" you mean submitting it to the IESG for 
>> publication as RFC.. But you could mean it also like "Submit the first 
>> draft and make it a WG work item" -- this would typically be said like 
>> "Publish XXX as WG I-D".

	Nope. I tried to follow what others were doing. What I
	have been able to glean from the other charters is that
	Submit ususally means "publish I-D". However, I agree
	that we could tighten this up by using language like
	"publish". I suppose we need to document guidelines
	for how to write a charter....

>> On Wed, 7 Jan 2004, David Meyer wrote:
>> > >> Done Submit I-D on debugging multicast problems.

	Debugging handbook.

>> I do not see any RFC on this?  Did this get anywhere?  This could be 
>> rather useful work...
>> 
>> > >> Done Submit final version of scoped address discovery protocol (SADP)
>> 
>> I don't see RFC on this, but maybe it isn't even necessary :-)

	We had a I-D, but it timed out (years ago), as it was
	not deemed useful

>> 
>> > >> Done Submit I-D describing ISP multicast deployment practices
>> 
>> I guess this refers to draft-ietf-mboned-ipv4-mcast-bcp, which is 
>> expired, and which isn't submitted yet...?

	Yep.

>> > >> Done Submit I-D, with RPS WG, on extensions to RPSL to describe multicast
>> > >> routing policy.
>> 
>> This has been submitted, yes, but the work is still unfinished 
>> (unresolved IETF Last Call contents).  Maybe no change needed..

	Well, this was an action ITEM that (believe this) that
	Jeff Young had put into the original charter so that he
	could describe his (MCI) DVMRP tunnel infrastructure. We
	did that, but then let it go to get the RPSL doc
	published (that was rife with problems due to IESG
	instability; John Curran finally got it through for us). 

>> > >> Done Submit I-D describing IPv4 Multicast Unusable Group And Source
>> > >> Addresses
>> 
>> This has not been submitted yet (though one can hope it will be)!

	Submit v. publish again.

>> 
>> > >> Done Submit I-D describing Embedded RP for IPv6 Multicast Address
>> 
>> Neither is this!

	Ditto

>> 
>> > >> Apr 04 Submit I-D on PIM-SM Multicast Routing Security Issues
>> > >> 
>> > >> May 04 Submit I-D on IPv4/IPv6 multicast co-existence
>> > >>        issues and strategies for IPv4 multicast and IPv6 multicast.
>> 
>> For these (and any other "Submit I-D" milestones which aren't DONE 
>> yet), I'd strongly recommend enhancing the wording a bit:
>>  - reword "Submit" to "Submit to the IESG"
>>  - add the category "... for consideration as Informational RFC"
>> 
>> I find especially the latter very useful information.

	Agree.

>> 
>> > >> June 04 Update IANA Guidelines for IPv4 Multicast Address
>> > >>         Assignments (RFC 3171/BCP 51)
>> > >> 
>> > >> Jun 04 Submit PIM-SM Multicast Routing Security Issues
>> > >>        to IESG for Informational
>> > >> 
>> > >> June 04 Submit MSDP MIB to IESG for Experimental
>> > >> 
>> > >> Aug 04 Submit IPv4 multicast address allocation procedures IESG for BCP
>> > >> 
>> > >> Aug 04 Submit IPv4/v6 co-existence strategies to IESG for Informational
>> > >> 
>> > >> Aug 04 Submit multicast roadmap/reference architecture
>> > >>        document to IESG for Informational
>> 
>> Oh, maybe you didn't mean "Submit I-D" as I meant, -- if so, some of 
>> the "Submit I-D" milestones, which haven't gone to the IESG yet, 
>> should also be listed as milestones for IESG submission.

	Correct. 

	So, want to co-author "Guidelines for Writing WG Charters"
	with me (really)? Seems I've been writing a lot of these
	lately... 

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 11:25:48 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11246
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 11:25:47 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09GNuu1009105
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 08:23:56 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09GNu4m009104
	for mboned-outgoing; Fri, 9 Jan 2004 08:23:56 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09GNtu1009096
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 08:23:55 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i09GNt6f010337;
	Fri, 9 Jan 2004 08:23:55 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i09GNtwg010336;
	Fri, 9 Jan 2004 08:23:55 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 9 Jan 2004 08:23:55 -0800
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Bill Nickless <nickless@mcs.anl.gov>, mboned@lists.uoregon.edu
Subject: Re: mboned: I-D  ACTION:draft-ietf-mboned-ipv4-mcast-unusable-01.txt]
Message-ID: <20040109162355.GB10255@1-4-5.net>
References: <5.2.0.9.2.20040107150333.02118d60@pop.mcs.anl.gov> <Pine.LNX.4.44.0401091631420.29733-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0401091631420.29733-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Fri, Jan 09, 2004 at 04:39:07PM +0200, Pekka Savola wrote:
>> Hi,
>> 
>> On Wed, 7 Jan 2004, Bill Nickless wrote:
>> > Operationally, I think there are at least three places where access control 
>> > lists should (by best practice) be installed: in the hosts/customer 
>> > routers, at the edge of the AS (for PIM), and between ASes (for 
>> > MSDP).  
>> 
>> Agreed.
>> 
>> > Using the "belt and suspenders" paranoid approach, I would suggest 
>> > that the elements in each of these three access controls would be cumulative.
>> 
>> To a degree..
>> 
>> > In other words:
>> > 
>> > The lines in Section 6 that refer to Section 7 should be installed on hosts 
>> > (probably Ethernet kernel drivers) and on host-facing routers.
>> 
>> This may not always be feasible, but otherwise I'd agree.
>>  
>> > The lines in Section 6 that refer to Sections 7 and 8 should be installed 
>> > on PIM routers that face other administrative domains.
>> > 
>> > The lines in Section 6 that refer to Sections 7, 8, and 9 should be 
>> > installed on MSDP-speaking routers that peer with other administrative domains.
>> 
>> Yep.
>>  
>> > At first glance, I don't think this document is the place to include the 
>> > above explanation; instead, I think that's better put in a BCP.
>> 
>> I agree that if we want to *recommend* something, it should be better 
>> put in a BCP.
>> 
>> But what I'm mostly worried about here is the organization of the 
>> data.  I think it would probably be better, for everyone (and easier 
>> to refer to in the BCP as well) if it was organized by separating 
>> practically the three different categories of addresses to separate 
>> sections.
>> 
>> But if others disagree with this, that's fine  -- this is not a 
>> critical thing for the development of the document.
>> 
>> -- 
>> Pekka Savola                 "You each name yourselves king, yet the
>> Netcore Oy                    kingdom bleeds."
>> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

	Let's see if we can close on this. The WG LC timer runs
	out on this today. Pekka's were the only comments. Are
	there others (as he doesn't seem to feel that strongly
	about this; Pekka, correct me if I'm wrong).

	Dave

	[Note: Please use mboned@lists.uoregon.edu rather than
	mboned@ns.uoregon.edu. Thanks, Dave[
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


From owner-mboned@lists.uoregon.edu  Fri Jan  9 12:27:55 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15341
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 12:27:54 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09EdRu1009921
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 06:39:27 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09EdRRg009920
	for mboned-outgoing; Fri, 9 Jan 2004 06:39:27 -0800 (PST)
Received: from network-services.uoregon.edu (network-services.uoregon.edu [128.223.60.21])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09EdQu2009903
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 06:39:27 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by network-services.uoregon.edu (8.12.8/8.12.8) with ESMTP id i09EdOhO013618
	for <mboned@network-services.uoregon.edu>; Fri, 9 Jan 2004 06:39:25 -0800
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i09Ed7M30380;
	Fri, 9 Jan 2004 16:39:11 +0200
Date: Fri, 9 Jan 2004 16:39:07 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Bill Nickless <nickless@mcs.anl.gov>
cc: David Meyer <dmm@1-4-5.net>, <mboned@network-services.uoregon.edu>
Subject: Re: mboned: I-D  ACTION:draft-ietf-mboned-ipv4-mcast-unusable-01.txt]
In-Reply-To: <5.2.0.9.2.20040107150333.02118d60@pop.mcs.anl.gov>
Message-ID: <Pine.LNX.4.44.0401091631420.29733-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

Hi,

On Wed, 7 Jan 2004, Bill Nickless wrote:
> Operationally, I think there are at least three places where access control 
> lists should (by best practice) be installed: in the hosts/customer 
> routers, at the edge of the AS (for PIM), and between ASes (for 
> MSDP).  

Agreed.

> Using the "belt and suspenders" paranoid approach, I would suggest 
> that the elements in each of these three access controls would be cumulative.

To a degree..

> In other words:
> 
> The lines in Section 6 that refer to Section 7 should be installed on hosts 
> (probably Ethernet kernel drivers) and on host-facing routers.

This may not always be feasible, but otherwise I'd agree.
 
> The lines in Section 6 that refer to Sections 7 and 8 should be installed 
> on PIM routers that face other administrative domains.
> 
> The lines in Section 6 that refer to Sections 7, 8, and 9 should be 
> installed on MSDP-speaking routers that peer with other administrative domains.

Yep.
 
> At first glance, I don't think this document is the place to include the 
> above explanation; instead, I think that's better put in a BCP.

I agree that if we want to *recommend* something, it should be better 
put in a BCP.

But what I'm mostly worried about here is the organization of the 
data.  I think it would probably be better, for everyone (and easier 
to refer to in the BCP as well) if it was organized by separating 
practically the three different categories of addresses to separate 
sections.

But if others disagree with this, that's fine  -- this is not a 
critical thing for the development of the document.

-- 
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/


From owner-mboned@lists.uoregon.edu  Fri Jan  9 12:36:28 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16811
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 12:36:27 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09EVQu1006339
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 06:31:26 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09EVQK0006336
	for mboned-outgoing; Fri, 9 Jan 2004 06:31:26 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09EVOu1006303
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 06:31:25 -0800 (PST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i09EVEk30193;
	Fri, 9 Jan 2004 16:31:14 +0200
Date: Fri, 9 Jan 2004 16:31:14 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: David Meyer <dmm@1-4-5.net>
cc: mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
In-Reply-To: <20040107221009.GA5459@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0401091615060.29733-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

Hi,

This has probably already been shipped, but a few comments so they can 
be addressed in the next revision..

I assume by "Submit I-D" you mean submitting it to the IESG for 
publication as RFC.. But you could mean it also like "Submit the first 
draft and make it a WG work item" -- this would typically be said like 
"Publish XXX as WG I-D".

On Wed, 7 Jan 2004, David Meyer wrote:
> >> Done Submit I-D on debugging multicast problems.

I do not see any RFC on this?  Did this get anywhere?  This could be 
rather useful work...

> >> Done Submit final version of scoped address discovery protocol (SADP)

I don't see RFC on this, but maybe it isn't even necessary :-)

> >> Done Submit I-D describing ISP multicast deployment practices

I guess this refers to draft-ietf-mboned-ipv4-mcast-bcp, which is 
expired, and which isn't submitted yet...?

> >> Done Submit I-D, with RPS WG, on extensions to RPSL to describe multicast
> >> routing policy.

This has been submitted, yes, but the work is still unfinished 
(unresolved IETF Last Call contents).  Maybe no change needed..

> >> Done Submit I-D describing IPv4 Multicast Unusable Group And Source
> >> Addresses

This has not been submitted yet (though one can hope it will be)!

> >> Done Submit I-D describing Embedded RP for IPv6 Multicast Address

Neither is this!

> >> Apr 04 Submit I-D on PIM-SM Multicast Routing Security Issues
> >> 
> >> May 04 Submit I-D on IPv4/IPv6 multicast co-existence
> >>        issues and strategies for IPv4 multicast and IPv6 multicast.

For these (and any other "Submit I-D" milestones which aren't DONE 
yet), I'd strongly recommend enhancing the wording a bit:
 - reword "Submit" to "Submit to the IESG"
 - add the category "... for consideration as Informational RFC"

I find especially the latter very useful information.

> >> June 04 Update IANA Guidelines for IPv4 Multicast Address
> >>         Assignments (RFC 3171/BCP 51)
> >> 
> >> Jun 04 Submit PIM-SM Multicast Routing Security Issues
> >>        to IESG for Informational
> >> 
> >> June 04 Submit MSDP MIB to IESG for Experimental
> >> 
> >> Aug 04 Submit IPv4 multicast address allocation procedures IESG for BCP
> >> 
> >> Aug 04 Submit IPv4/v6 co-existence strategies to IESG for Informational
> >> 
> >> Aug 04 Submit multicast roadmap/reference architecture
> >>        document to IESG for Informational

Oh, maybe you didn't mean "Submit I-D" as I meant, -- if so, some of 
the "Submit I-D" milestones, which haven't gone to the IESG yet, 
should also be listed as milestones for IESG submission.

-- 
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/


From owner-mboned@lists.uoregon.edu  Fri Jan  9 13:31:34 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22932
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 13:31:33 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09IQtu1015678
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 10:26:55 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09IQt1p015677
	for mboned-outgoing; Fri, 9 Jan 2004 10:26:55 -0800 (PST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09IQsu1015641
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 10:26:54 -0800 (PST)
Received: from jackson.cs.ucsb.edu (jackson [128.111.52.10])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id i09IQoM17353;
	Fri, 9 Jan 2004 10:26:51 -0800 (PST)
Received: from jackson.cs.ucsb.edu (localhost [127.0.0.1])
	by jackson.cs.ucsb.edu (8.12.8/8.11.6) with ESMTP id i09IQoti018700;
	Fri, 9 Jan 2004 10:26:50 -0800
Received: (from almeroth@localhost)
	by jackson.cs.ucsb.edu (8.12.8/8.12.8/Submit) id i09IQnv9018698;
	Fri, 9 Jan 2004 10:26:49 -0800
Date: Fri, 9 Jan 2004 10:26:49 -0800
From: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Message-Id: <200401091826.i09IQnv9018698@jackson.cs.ucsb.edu>
To: dmm@1-4-5.net, pekkas@netcore.fi
Subject: Re: mboned: Please comment (in the event you didn't see this)
Cc: mboned@lists.uoregon.edu
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

>>>> On Wed, 7 Jan 2004, David Meyer wrote:
>>>> > >> Done Submit I-D on debugging multicast problems.
>>
>>	Debugging handbook.
>>
>>>> I do not see any RFC on this?  Did this get anywhere?  This could be 
>>>> rather useful work...
>>>> 
>>>> > >> Done Submit final version of scoped address discovery protocol (SADP)
>>>> 
>>>> I don't see RFC on this, but maybe it isn't even necessary :-)
>>
>>	We had a I-D, but it timed out (years ago), as it was
>>	not deemed useful

It was hard to make it useful, and more importantly, it was a document
that changed almost weekly.

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


From owner-mboned@lists.uoregon.edu  Fri Jan  9 13:41:21 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23224
	for <mboned-archive@lists.ietf.org>; Fri, 9 Jan 2004 13:41:21 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09IaHu1000643
	for <mboned-outgoing@darkwing.uoregon.edu>; Fri, 9 Jan 2004 10:36:17 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i09IaHjM000639
	for mboned-outgoing; Fri, 9 Jan 2004 10:36:17 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i09IaGu1000628
	for <mboned@lists.uoregon.edu>; Fri, 9 Jan 2004 10:36:16 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i09IaG6f012370;
	Fri, 9 Jan 2004 10:36:16 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i09IaGkE012369;
	Fri, 9 Jan 2004 10:36:16 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 9 Jan 2004 10:36:16 -0800
From: David Meyer <dmm@1-4-5.net>
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>
Cc: pekkas@netcore.fi, mboned@lists.uoregon.edu
Subject: Re: mboned: Please comment (in the event you didn't see this)
Message-ID: <20040109183616.GA12363@1-4-5.net>
References: <200401091826.i09IQnv9018698@jackson.cs.ucsb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200401091826.i09IQnv9018698@jackson.cs.ucsb.edu>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Fri, Jan 09, 2004 at 10:26:49AM -0800, Kevin C. Almeroth wrote:
>> >>>> On Wed, 7 Jan 2004, David Meyer wrote:
>> >>>> > >> Done Submit I-D on debugging multicast problems.
>> >>
>> >>	Debugging handbook.
>> >>
>> >>>> I do not see any RFC on this?  Did this get anywhere?  This could be 
>> >>>> rather useful work...
>> >>>> 
>> >>>> > >> Done Submit final version of scoped address discovery protocol (SADP)
>> >>>> 
>> >>>> I don't see RFC on this, but maybe it isn't even necessary :-)
>> >>
>> >>	We had a I-D, but it timed out (years ago), as it was
>> >>	not deemed useful
>> 
>> It was hard to make it useful, and more importantly, it was a document
>> that changed almost weekly.

	Yep.

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


From owner-mboned@lists.uoregon.edu  Mon Jan 12 11:42:57 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04990
	for <mboned-archive@lists.ietf.org>; Mon, 12 Jan 2004 11:42:56 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0CGb6u1014349
	for <mboned-outgoing@darkwing.uoregon.edu>; Mon, 12 Jan 2004 08:37:06 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0CGb58c014343
	for mboned-outgoing; Mon, 12 Jan 2004 08:37:05 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0CGb5u1013914
	for <mboned@lists.uoregon.edu>; Mon, 12 Jan 2004 08:37:05 -0800 (PST)
Received: from sj-core-3.cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 12 Jan 2004 08:37:14 -0800
Received: from edison.cisco.com (edison.cisco.com [171.71.180.109])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i0CGadQu007055;
	Mon, 12 Jan 2004 08:36:40 -0800 (PST)
Received: from bwilliam-t30.cisco.com (bwilliam-t30.cisco.com [64.101.135.114]) by edison.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA27183; Mon, 12 Jan 2004 08:36:39 -0800 (PST)
Message-Id: <6.0.0.22.2.20040112093233.03b775d8@mail1.cisco.com>
X-Sender: bwilliam@mail1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 12 Jan 2004 09:38:38 -0600
To: "Kevin C. Almeroth" <almeroth@cs.ucsb.edu>, dmm@1-4-5.net,
        pekkas@netcore.fi
From: Beau Williamson <bwilliam@cisco.com>
Subject: Re: mboned: Please comment (in the event you didn't see this)
Cc: mboned@lists.uoregon.edu
In-Reply-To: <200401091826.i09IQnv9018698@jackson.cs.ucsb.edu>
References: <200401091826.i09IQnv9018698@jackson.cs.ucsb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

At 12:26 PM 1/9/2004, Kevin C. Almeroth wrote:
> >>>> > >> Done Submit final version of scoped address discovery protocol 
> (SADP)
> >>>>
> >>>> I don't see RFC on this, but maybe it isn't even necessary :-)
> >>
> >>      We had a I-D, but it timed out (years ago), as it was
> >>      not deemed useful
>
>It was hard to make it useful, and more importantly, it was a document
>that changed almost weekly.

If you are talking about SADP, I'm curious as to why it isn't useful. This 
seems almost exactly what we need to solve some of the problems we are 
having now regarding applications like Norton Ghost and others that need a 
light-weight address discovery protocol.

Now I admit there's still some work to be done to make this work but I'm 
not sure we want to abandon the basic idea of using a well-known, 
Scope-Relative address [SADP-RELATIVE?] to either:

1) Periodically Announce a service

2) Request the address of a service (ala the SADP spec).

3) or both

As far as I can see, the biggest problem is that we don't really have MZAP 
support in any products and that results in a lack of an ability to 
determine what the actual SADP Scope Relative addresses are.  I think we 
can get around that with an extension to RFC 2365 that "fixes" the 
Site-Local and Organization--Local range so that these two scopes/zones are 
well-known.

Beau 

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


From owner-mboned@lists.uoregon.edu  Mon Jan 12 13:52:04 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10760
	for <mboned-archive@lists.ietf.org>; Mon, 12 Jan 2004 13:52:04 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0CIlSux029753
	for <mboned-outgoing@darkwing.uoregon.edu>; Mon, 12 Jan 2004 10:47:29 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0CIlS37029733
	for mboned-outgoing; Mon, 12 Jan 2004 10:47:28 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0CIlSux029681
	for <mboned@lists.uoregon.edu>; Mon, 12 Jan 2004 10:47:28 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0CIlS6f015115
	for <mboned@lists.uoregon.edu>; Mon, 12 Jan 2004 10:47:28 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0CIlSZ3015114
	for mboned@lists.uoregon.edu; Mon, 12 Jan 2004 10:47:28 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Mon, 12 Jan 2004 10:47:28 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: informal survey: Who's going to Seoul?
Message-ID: <20040112184728.GA15102@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Folks,

	I'm trying to run an informal survey of who's going to
	Seoul (for scheduling purposes). Please drop me a note
	oob if you're planning on atttending.

	Thanks,

	Dave

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


From owner-mboned@lists.uoregon.edu  Wed Jan 14 18:42:52 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21933
	for <mboned-archive@lists.ietf.org>; Wed, 14 Jan 2004 18:42:51 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0ENYltv019364
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 14 Jan 2004 15:34:47 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0ENYlMR019363
	for mboned-outgoing; Wed, 14 Jan 2004 15:34:47 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0ENYjtv019247;
	Wed, 14 Jan 2004 15:34:45 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0ENYj6f032598;
	Wed, 14 Jan 2004 15:34:45 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0ENYipa032597;
	Wed, 14 Jan 2004 15:34:44 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 14 Jan 2004 15:34:44 -0800
From: David Meyer <dmm@1-4-5.net>
To: msdp@lists.uoregon.edu
Cc: fenner@research.att.com, zinin@psg.com, mboned@lists.uoregon.edu
Subject: mboned: Closing the MSDP WG
Message-ID: <20040114233444.GA32361@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Alex/Bill,

	The MSDP WG has concluded its work on the MSDP spec (the
	MSDP MIB will be finished in the MBONED WG). As such, I'm
	requesting that you close the MSDP WG. 

	I want to thank all of you who worked on MSDP for your
	hard work, attention to detail, and perseverance. Well
	done all. 

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 10:09:30 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02676
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 10:09:30 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF4v1M013968
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 07:04:57 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KF4ux4013962
	for mboned-outgoing; Tue, 20 Jan 2004 07:04:56 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF4t1M013874
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 07:04:55 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02344;
	Tue, 20 Jan 2004 10:04:52 -0500 (EST)
Message-Id: <200401201504.KAA02344@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mboned@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: mboned: I-D ACTION:draft-ietf-mboned-rfc3171bis-01.txt
Date: Tue, 20 Jan 2004 10:04:52 -0500
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

--NextPart

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		: IANA Guidelines for IPv4 Multicast Address Assignments
	Author(s)	: Z. Albanna
	Filename	: draft-ietf-mboned-rfc3171bis-01.txt
	Pages		: 13
	Date		: 2004-1-19
	
The Internet Assigned Numbers Authority is charged with allocating
parameter values for fields in protocols which have been designed,
created or are maintained by the Internet Engineering Task Force.
This document provides guidelines for the assignment of the IPv4 IP
multicast address space.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-rfc3171bis-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-rfc3171bis-01.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mboned-rfc3171bis-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-20102623.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mboned-rfc3171bis-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mboned-rfc3171bis-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-20102623.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 10:09:31 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02679
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 10:09:30 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF521M014195
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 07:05:02 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KF52Wg014193
	for mboned-outgoing; Tue, 20 Jan 2004 07:05:02 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF501M014074
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 07:05:00 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02360;
	Tue, 20 Jan 2004 10:04:57 -0500 (EST)
Message-Id: <200401201504.KAA02360@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mboned@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: mboned: I-D ACTION:draft-ietf-mboned-msdp-deploy-05.txt
Date: Tue, 20 Jan 2004 10:04:57 -0500
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

--NextPart

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		: Multicast Source Discovery Protocol (MSDP) Deployment Scenarios
	Author(s)	: M. McBride
	Filename	: draft-ietf-mboned-msdp-deploy-05.txt
	Pages		: 18
	Date		: 2004-1-19
	
This document describes best current practices for intra-domain and
inter-domain deployment of the Multicast Source Discovery Protocol
(MSDP) in conjunction with Protocol Independent Multicast Sparse Mode
(PIM-SM)

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-msdp-deploy-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-msdp-deploy-05.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mboned-msdp-deploy-05.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-20102705.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mboned-msdp-deploy-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mboned-msdp-deploy-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-20102705.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 10:09:36 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02730
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 10:09:35 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF561M014447
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 07:05:07 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KF565o014444
	for mboned-outgoing; Tue, 20 Jan 2004 07:05:06 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KF541M014366
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 07:05:05 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02376;
	Tue, 20 Jan 2004 10:05:02 -0500 (EST)
Message-Id: <200401201505.KAA02376@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mboned@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: mboned: I-D ACTION:draft-ietf-mboned-ssm232-07.txt
Date: Tue, 20 Jan 2004 10:05:02 -0500
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

--NextPart

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		: Source-Specific Protocol Independent Multicast in 232/8
	Author(s)	: D. Meyer, R. Rockell, G. Shepherd
	Filename	: draft-ietf-mboned-ssm232-07.txt
	Pages		: 10
	Date		: 2004-1-19
	
IP Multicast group addresses in the 232/8 (232.0.0.0 to
232.255.255.255) range are designated as source-specific multicast
[SSM] destination addresses and are reserved for use by source-
specific applications and protocols [IANA]. This document defines
operational recommendations to ensure source-specific behavior within
the 232/8 range.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-ssm232-07.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ssm232-07.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mboned-ssm232-07.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-20102717.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mboned-ssm232-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mboned-ssm232-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-20102717.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 10:30:01 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04692
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 10:30:00 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KFRhwI002321
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 07:27:43 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KFRhS7002320
	for mboned-outgoing; Tue, 20 Jan 2004 07:27:43 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KFRgwI002315
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 07:27:42 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KFRg3K032315
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 07:27:42 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KFRgCC032314
	for mboned@lists.uoregon.edu; Tue, 20 Jan 2004 07:27:42 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2004 07:27:42 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120152742.GA32267@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Folks,

	This note starts the WG Last Call for 
	draft-mboned-ipv4-uni-based-mcast-01.txt. The last call
	will end at 1700 PST on 02.03.2004. Please address
	comments to the list.

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 11:53:32 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12135
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 11:53:29 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KGnlwI008996
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 08:49:47 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KGnlCE008993
	for mboned-outgoing; Tue, 20 Jan 2004 08:49:47 -0800 (PST)
Received: from shepfarm.com (IDENT:GaV+xxUHxhjS/4pY30Kk2mfcZVvGArOK@shepfarm.com [198.58.3.10])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KGnkwI008965
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 08:49:46 -0800 (PST)
Received: from shepfarm.com (IDENT:3ct1hY3YLRpJCYqmdGG1ioNYkAlmw9PD@shepfarm.com [198.58.3.10])
	by shepfarm.com (8.12.10/8.11.3) with ESMTP id i0KIfKTk020510;
	Tue, 20 Jan 2004 10:41:20 -0800
Date: Tue, 20 Jan 2004 10:41:19 -0800 (PST)
From: shep@shepfarm.com
To: David Meyer <dmm@1-4-5.net>
cc: mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
In-Reply-To: <20040120152742.GA32267@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0401201040450.16965-100000@shepfarm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


The link to the draft is dead:

http://www.ietf.org/internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt

Can someone point me to a copy?

Thanks,
Greg

On Tue, 20 Jan 2004, David Meyer wrote:

> 
> 	Folks,
> 
> 	This note starts the WG Last Call for 
> 	draft-mboned-ipv4-uni-based-mcast-01.txt. The last call
> 	will end at 1700 PST on 02.03.2004. Please address
> 	comments to the list.
> 
> 	Thanks,
> 
> 	dave
> _______________________________________________________________
> 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/


From owner-mboned@lists.uoregon.edu  Tue Jan 20 11:56:48 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12324
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 11:56:48 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KGskwI023855
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 08:54:46 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KGskUc023852
	for mboned-outgoing; Tue, 20 Jan 2004 08:54:46 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KGsjwI023789
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 08:54:45 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KGsj3K002017;
	Tue, 20 Jan 2004 08:54:45 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KGsjUg002016;
	Tue, 20 Jan 2004 08:54:45 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2004 08:54:45 -0800
From: David Meyer <dmm@1-4-5.net>
To: shep@shepfarm.com
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120165445.GA1973@1-4-5.net>
References: <20040120152742.GA32267@1-4-5.net> <Pine.LNX.4.44.0401201040450.16965-100000@shepfarm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0401201040450.16965-100000@shepfarm.com>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Tue, Jan 20, 2004 at 10:41:19AM -0800, shep@shepfarm.com wrote:
>> 
>> The link to the draft is dead:
>> 
>> http://www.ietf.org/internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
>> 
>> Can someone point me to a copy?

Thanks Greg. Dave just posted a new copy to the I-D repository,
but of course, it's not there yet. I put it on
http://www.1-4-5.net/~dmm/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
until it gets there (note that it is misnamed in the document text).
	
Thanks,

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 12:11:24 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13056
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 12:11:24 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KH8mwI010521
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 09:08:48 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KH8mGR010520
	for mboned-outgoing; Tue, 20 Jan 2004 09:08:48 -0800 (PST)
Received: from shepfarm.com (IDENT:6g8Dpd/XxAdpn2lTucxcrAFPuDuDKlwz@shepfarm.com [198.58.3.10])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KH8mwI010458
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:08:48 -0800 (PST)
Received: from shepfarm.com (IDENT:Cg5H3RVnH5OQoQrR1x38vwvPTBJXtWx7@shepfarm.com [198.58.3.10])
	by shepfarm.com (8.12.10/8.11.3) with ESMTP id i0KJ0OTk020561;
	Tue, 20 Jan 2004 11:00:24 -0800
Date: Tue, 20 Jan 2004 11:00:24 -0800 (PST)
From: shep@shepfarm.com
To: David Meyer <dmm@1-4-5.net>
cc: mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
In-Reply-To: <20040120165445.GA1973@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0401201055140.16965-100000@shepfarm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


Thanks Dave.

Comments:

From section 1.

o    bidirectional shared tree routing protocols may easily locate
     the direction to the root by doing a route lookup on a
     unicast address derived from the multicast group address.

The above assumes some correlation between the bidir RP address and the 
subnet from which the group address is derived. This is not a safe 
assumption. I feel this paragraph should be removed from the document.

Greg 

On Tue, 20 Jan 2004, David Meyer wrote:

> On Tue, Jan 20, 2004 at 10:41:19AM -0800, shep@shepfarm.com wrote:
> >> 
> >> The link to the draft is dead:
> >> 
> >> http://www.ietf.org/internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
> >> 
> >> Can someone point me to a copy?
> 
> Thanks Greg. Dave just posted a new copy to the I-D repository,
> but of course, it's not there yet. I put it on
> http://www.1-4-5.net/~dmm/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
> until it gets there (note that it is misnamed in the document text).
> 	
> Thanks,
> 
> Dave
> 

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 12:17:09 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13249
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 12:17:09 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHEewI001387
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 09:14:40 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KHEeQO001383
	for mboned-outgoing; Tue, 20 Jan 2004 09:14:40 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHEdwI001357
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:14:39 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KHEd3K002354
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:14:39 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KHEdVc002353
	for mboned@lists.uoregon.edu; Tue, 20 Jan 2004 09:14:39 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2004 09:14:39 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120171439.GA2286@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	A few immediate comments:

	Editorial comments:

	(i).	What category (not specified). 

	(ii).	RFC 2770 is obsoleted by 3180 (which is BCP)

	(iii).	draft names itself
		draft-mboned-ipv4-uni-based-mcast-01.txt (should
		be draft-ietf-mboned-ipv4-uni-based-mcast-01.txt)

	(iv).	While not required, no TOC

	(v).	Section 3: IANA Considerations:
		The /8 should be timed out in a year or so,
		depending on the category we want.

	(vi).	No IPR statement.

	Non-editorial comments:

	(i).	What problems does this solve? In general, the
		256 address limitation imposed by GLOP doesn't
		seem to be much of a problem (rather, it is those
		who need globally unique addresses that may or
		may not be connected to the public Internet,
		etc), i.e., an administrative entity running out
		of GLOP addressing isn't the issue we're facing.

	(ii).	Section 4 Security Considerations

		Why is GLOP dynamic addressing? I would imagine
		that what most folks mean by dynamic addressing
		would fall more commonly along the lines of
		MADCAP, etc.

	Dave


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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 12:19:43 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13377
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 12:19:43 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHHwwI010711
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 09:17:58 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KHHwgq010706
	for mboned-outgoing; Tue, 20 Jan 2004 09:17:58 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHHvwI010327
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:17:57 -0800 (PST)
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 20 Jan 2004 09:18:43 -0800
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id i0KHHojQ011242;
	Tue, 20 Jan 2004 09:17:50 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id JAA09337;
	Tue, 20 Jan 2004 09:17:49 -0800 (PST)
Date: Tue, 20 Jan 2004 09:17:49 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Meyer <dmm@1-4-5.net>, dthaler@microsoft.com
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120171749.GM26592@cisco.com>
References: <20040120152742.GA32267@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040120152742.GA32267@1-4-5.net>
User-Agent: Mutt/1.4i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

Dave,

I assume you mean draft-ietf-mboned-ipv4-uni-based-mcast-01.txt,
but that draft has been deleted from the IETF drafts directory as it
seems on April 30, 2003, so it is a bit rough to offer comments to a draft
not in official existance for about 9 months. Is there a working URL for
the draft on www.ietf.org ? Am i just too stupid to look ? 

Thanks
	Toerless

On Tue, Jan 20, 2004 at 07:27:42AM -0800, David Meyer wrote:
> 
> 	Folks,
> 
> 	This note starts the WG Last Call for 
> 	draft-mboned-ipv4-uni-based-mcast-01.txt. The last call
> 	will end at 1700 PST on 02.03.2004. Please address
> 	comments to the list.
> 
> 	Thanks,
> 
> 	dave
> _______________________________________________________________
> 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/


From owner-mboned@lists.uoregon.edu  Tue Jan 20 12:22:59 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13492
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 12:22:59 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHL5wI022214
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 09:21:05 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KHL5TV022213
	for mboned-outgoing; Tue, 20 Jan 2004 09:21:05 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHL4wI022140
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:21:04 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KHKw3K002504;
	Tue, 20 Jan 2004 09:20:58 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KHKwGA002503;
	Tue, 20 Jan 2004 09:20:58 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@cisco.com using -f
Date: Tue, 20 Jan 2004 09:20:58 -0800
From: David Meyer <dmm@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
Cc: David Meyer <dmm@1-4-5.net>, dthaler@microsoft.com,
        mboned@lists.uoregon.edu
Subject: Re: mboned: WG Last Call for draft-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120172058.GA2497@cisco.com>
References: <20040120152742.GA32267@1-4-5.net> <20040120171749.GM26592@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040120171749.GM26592@cisco.com>
User-Agent: Mutt/1.4.1i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Tue, Jan 20, 2004 at 09:17:49AM -0800, Toerless Eckert wrote:
>> Dave,
>> 
>> I assume you mean draft-ietf-mboned-ipv4-uni-based-mcast-01.txt,
>> but that draft has been deleted from the IETF drafts directory as it
>> seems on April 30, 2003, so it is a bit rough to offer comments to a draft
>> not in official existance for about 9 months. Is there a working URL for
>> the draft on www.ietf.org ? Am i just too stupid to look ? 

	Nope, you're not. I put it on 1-4-5.net (see subsequent
	emails). 

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 12:42:44 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13961
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 12:42:43 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHe3wI003095
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 09:40:03 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KHe3kF003090
	for mboned-outgoing; Tue, 20 Jan 2004 09:40:03 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KHe2wI003038
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:40:02 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KHe23K003246
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 09:40:02 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KHe2dQ003245
	for mboned@lists.uoregon.edu; Tue, 20 Jan 2004 09:40:02 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2004 09:40:02 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120174002.GA3212@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Folks,

	My mistake. I thought this one was on the I-D
	repository. I'm cancelling the LC and I'll reissue it
	when it gets there (if there isn't significant negative
	feedback before then). 

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 14:05:42 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16327
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 14:05:41 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KIwgwI025685
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 10:58:42 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KIwgOM025684
	for mboned-outgoing; Tue, 20 Jan 2004 10:58:42 -0800 (PST)
Received: from mailout.TechFak.Uni-Bielefeld.DE (mailout.TechFak.Uni-Bielefeld.DE [129.70.136.245])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KIwdwI025494
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 10:58:40 -0800 (PST)
Received: from grimsvotn.TechFak.Uni-Bielefeld.DE (grimsvotn.TechFak.Uni-Bielefeld.DE [129.70.137.40])
	by momotombo.TechFak.Uni-Bielefeld.DE (8.11.7p1+Sun/8.11.6/TechFak/2003/04/16/pk) with ESMTP id i0KIwcv00788
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 19:58:38 +0100 (MET)
Received: from localhost (pk@localhost)
	by grimsvotn.TechFak.Uni-Bielefeld.DE (8.11.7+Sun/8.9.1) with SMTP id i0KIwcR29801
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 19:58:38 +0100 (MET)
Message-Id: <200401201858.i0KIwcR29801@grimsvotn.TechFak.Uni-Bielefeld.DE>
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk owned process doing -bs
X-Authentication-Warning: grimsvotn.TechFak.Uni-Bielefeld.DE: pk@localhost didn't use HELO protocol
To: mboned@lists.uoregon.edu
Subject: Re: mboned: I-D ACTION:draft-ietf-mboned-ipv4-mcast-unusable-01.txt] 
In-reply-to: Your message of "Fri, 09 Jan 2004 08:23:55 PST."
             <20040109162355.GB10255@1-4-5.net> 
X-PGP-Fingerprint: 85 89 64 AD 73 79 92 1F  C8 76 95 2D 15 09 19 93
X-Organization: Uni Bielefeld, Technische Fakultaet
X-Phone: +49 521 106 2902
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12380.1074159579.1@grimsvotn.TechFak.Uni-Bielefeld.DE>
Date: Tue, 20 Jan 2004 19:58:38 +0100
From: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

> 	out on this today. Pekka's were the only comments. Are

sorry for being late, but here's another group that might not be usable
"locally". 239.7.7.0 is used by SGI's sdpd (Session Directory Server Daemon)
and thus not only unavailable for inter domain multicast (as of section 8),
but also on site.

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 14:54:16 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17804
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 14:54:15 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KJhewI018586
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 11:43:40 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KJheiO018583
	for mboned-outgoing; Tue, 20 Jan 2004 11:43:40 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KJhdwI018551
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 11:43:39 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0KJhd3K005973;
	Tue, 20 Jan 2004 11:43:39 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0KJhdBM005972;
	Tue, 20 Jan 2004 11:43:39 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 20 Jan 2004 11:43:39 -0800
From: David Meyer <dmm@1-4-5.net>
To: Peter Koch <pk@TechFak.Uni-Bielefeld.DE>
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: I-D ACTION:draft-ietf-mboned-ipv4-mcast-unusable-01.txt]
Message-ID: <20040120194339.GA5949@1-4-5.net>
References: <20040109162355.GB10255@1-4-5.net> <200401201858.i0KIwcR29801@grimsvotn.TechFak.Uni-Bielefeld.DE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200401201858.i0KIwcR29801@grimsvotn.TechFak.Uni-Bielefeld.DE>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Tue, Jan 20, 2004 at 07:58:38PM +0100, Peter Koch wrote:
>> > 	out on this today. Pekka's were the only comments. Are
>> 
>> sorry for being late, but here's another group that might not be usable
>> "locally". 239.7.7.0 is used by SGI's sdpd (Session Directory Server Daemon)
>> and thus not only unavailable for inter domain multicast (as of section 8),
>> but also on site.

	Just curious. Do you know if this predates RFC 2365 (07.1998)?

	Thanks,

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 15:27:19 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19649
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 15:27:13 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KKNtwI019041
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 12:23:55 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KKNtQ2019039
	for mboned-outgoing; Tue, 20 Jan 2004 12:23:55 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KKNswI018688
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 12:23:54 -0800 (PST)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 20 Jan 2004 12:27:46 +0000
Received: from cisco.com (cypher.cisco.com [171.69.11.143])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0KKNlGN016630;
	Tue, 20 Jan 2004 12:23:47 -0800 (PST)
Received: (from eckert@localhost)
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id MAA15911;
	Tue, 20 Jan 2004 12:23:46 -0800 (PST)
Date: Tue, 20 Jan 2004 12:23:46 -0800
From: Toerless Eckert <eckert@cisco.com>
To: David Meyer <dmm@1-4-5.net>
Cc: mboned@lists.uoregon.edu
Subject: Re: mboned: draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
Message-ID: <20040120202346.GB26592@cisco.com>
References: <20040120174002.GA3212@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040120174002.GA3212@1-4-5.net>
User-Agent: Mutt/1.4i
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

On Tue, Jan 20, 2004 at 09:40:02AM -0800, David Meyer wrote:
> 	Folks,
> 
> 	My mistake. I thought this one was on the I-D
> 	repository. I'm cancelling the LC and I'll reissue it
> 	when it gets there

No problem. I thought it was the authors responsibility to  make sure
a draft he wants going forward is available.

>       (if there isn't significant negative feedback before then). 

Oh, that's my prompt: 

  I think the draft shows a very logical and well written technical
  possibility, and i don't want to argue the technical merits, but
  rather the operational implications:

  Unlike the current IANA address allocation or hopefully a future
  extended GLOB address assignment via some registry, this mechanism
  does not create any documentation as to what application or
  purpose is associated with a particular group address. I do
  very much like to have this for addresses intended to be used on
  a permanent/well-known basis in the global scope.

  If instead we are talking about non-global scope or non-permanent
  assignments, then of course documentation isn't all that important,
  but this draft does not help there. It does not cover non global
  scope addresses, and i think it does not provide much value for
  non-permanent assignment: If you just want to broadcast across the
  internet in ASM some TV channels for some period of time, the current
  FCFS assignment in 224.2/16 has proven to be quite sufficient: conflict
  resolution is not a problem, the only problem is DoS, and that's an
  ASM problem not an address-range problem and the new method does not
  change it.

  But even if we agree on some value of this method for temporary usage,
  it is far outweighted in my opinion by the problem that it will
  be used in an uncontrolled way to allocate addresses on an effectively
  much more permanent basis by users:

  Example:

    - A small application developer writes a multicast application, wants
      to have a well-known multicast address for it, and simply takes the
      one address that he gets through the class-C network of his company.
      He puts out his application and it actually spreads across the
      internet (dream mode on: It might be a file-sharing application
      using multicast ;-). Now this developer changes the ISP, or goes
      out of business, or simply a year passes and the IETF reconsiders
      the assignment for the /8 to this mechanism, and voila, you've got
      trouble because now you've got an address assigned and in use where
      you either don't know anymore who owned it (imagine the new company
      getting the class-C network and seeing that their only group-address
      for this mechanism is widely spread by the prior owner.

   I think that all address assignment we see will finally fall into this
   category. So effectively we can forget about trying to establish
   this method as a temporary solution, it will by effect of users simply
   applying it in the above described way become a FCFS undocumented
   permanent assignment of global scope multicast addresses - and why
   would i want to have that ?
   

   So, here's what i think we could do:

   a) Don't do this at all, but instead pursue eGLOB.

   b) Change this draft to define a controlled allocation of global
      scope multicast addresses by IANA or some delegated allocation
      authority.

      Here's how:

       - If user comes to request global scope IP multicast address
	 from this space, he has to:

	 1. Provide documentation what this is used for and how long
	    it is inteded to be kept.

	 2. Declare which IP unicast prefix he owns and against which
	    his address request is to be accountet.

	 3. Authenticate himself by using credentials for that
	    unicast prefi (eg: verified email addresses or the like
	 
	 There is NO NEED to provide justification for the allocation
	 (as there is now if you simply want to get multicast addresses
	  from IANA). Instead the policy is: If you control N IP unicast
	  addresses, you can get up to N/256 multicast addresses.
	 
       - The address assignment agent will then hand out an amount of
	 IP multicast addreses not exceeding 1/256th of the IP unicast
	 address space in total for this requester.
      
      This method has a lot of advantages:

      1. It creates documentation and a traceable pointer back to
	 a responsible contact for the address, but it does not
	 require justification.

      2. The whole process can be fully automated via a web-page
	 (with access to unicast prefix registry information and for example
	  using some automated email exchange to validate identity).
      
      3. Given that it can be fully automated, it can create a web-accessible
	 list of allocated addresses.
	 
	 This would make it possible for operators to download
	 periodically an updated list of assignments automatically and 
	 put it into filter lists at key locations (eg: MIXes).
	 
	 Thus we can get an automatic filtering to only allow documented
	 and allocated global scope addresses. Which is very valuable
	 because now operators know always a responsible owner to contact
	 for multicast traffic flowing through their network.
       
       4. Address assignments can be automatically invalidated if they
	  expire, or when the owner information of the unicast prefix used
	  as credentials changes.
       
       5. Depending on what we define as the policy it is not necessary
	  to actually invalidate assignments when the owner changes
	  the service providers because the assignment does not have
	  to be necesarily the fixed algorithmic mapping.
	  
	  Instead this algorithmic mapping can be just the default
	  algorithm applied by the allocation authority, but effectively
	  it can use _any_ fre multicast prefix delegated to it by IANA
	  for this type of allocation.

	  Example:
	  
	  User owns 192.44.81/24, goes to web page to request 
	  a global scope multicast address. Fills in web-page stating
	  purpose and contact information, validates with email address
	  and may also have some other fields - like for example a
	  password for this allocation (allocation server will just store
	  MD5 of this).

	  Web-server sends email with password to email-address listed
	  in registry for 192.44.81. When reply with this password is
	  received by allocaiton server, it will hand out one ip multicast
	  address. This could by default be 237.192.44.81, or it could
	  be any other address (eg: when that one address was already
	  taken by a previous owner).

	  When the user later on changes service provider, he may loose
	  192.44.81/24, but he wants to maintain his assigned address.
	  So he revalidates with the allocation server by using his
	  password, which the allocation server validates against the
	  MD5 stored with this allocation). Now the user has just to
	  provide new unicast prefixes owned by him to be used as
	  effectively the "payment" to keep this allocation.
	  ... still all automated.

      And by the way: I would not have a problem if one global
      scope IP multicast address assigned via such a method would for
      example cost $10..$50 per year. With this amount of money it should
      be easy to find some registry willing to operate the automated
      allocation server.

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


From owner-mboned@lists.uoregon.edu  Tue Jan 20 15:47:28 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21203
	for <mboned-archive@lists.ietf.org>; Tue, 20 Jan 2004 15:47:28 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KKigwI000347
	for <mboned-outgoing@darkwing.uoregon.edu>; Tue, 20 Jan 2004 12:44:42 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.10/8.12.10/Submit) id i0KKig8i000345
	for mboned-outgoing; Tue, 20 Jan 2004 12:44:42 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.12.10/8.12.10) with ESMTP id i0KKiewI000172
	for <mboned@lists.uoregon.edu>; Tue, 20 Jan 2004 12:44:40 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20733;
	Tue, 20 Jan 2004 15:44:37 -0500 (EST)
Message-Id: <200401202044.PAA20733@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mboned@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: mboned: I-D ACTION:draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
Date: Tue, 20 Jan 2004 15:44:37 -0500
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

--NextPart

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		: Unicast-Prefix-based IPv4 Multicast Addresses
	Author(s)	: D. Thaler
	Filename	: draft-ietf-mboned-ipv4-uni-based-mcast-01.txt
	Pages		: 5
	Date		: 2004-1-20
	
This specification defines an extension to the multicast
addressing architecture of the IP Version 4 protocol.  The
extension presented in this document allows for unicast-prefix-
based allocation of multicast addresses.  By delegating multicast
addresses at the same time as unicast prefixes, network operators
will be able to identify their multicast addresses without needing
to run an inter-domain allocation protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ipv4-uni-based-mcast-01.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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-1-20142821.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mboned-ipv4-uni-based-mcast-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mboned-ipv4-uni-based-mcast-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-1-20142821.I-D@ietf.org>

--OtherAccess--

--NextPart--


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


From owner-mboned@lists.uoregon.edu  Wed Jan 21 17:04:35 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12999
	for <mboned-archive@lists.ietf.org>; Wed, 21 Jan 2004 17:04:34 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0LLxKt9011114
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 21 Jan 2004 13:59:20 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i0LLxKAh011104
	for mboned-outgoing; Wed, 21 Jan 2004 13:59:20 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0LLxKKo011012
	for <mboned@lists.uoregon.edu>; Wed, 21 Jan 2004 13:59:20 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0LLxK3K018446;
	Wed, 21 Jan 2004 13:59:20 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0LLxK9r018445;
	Wed, 21 Jan 2004 13:59:20 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 21 Jan 2004 13:59:20 -0800
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: I-D deadline approaching
Message-ID: <20040121215920.GB18420@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

	Folks, 

	Heads up: The deadline to submit initial documents (-00)
	for Seoul is 02.09.2004.

	Dave

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


From owner-mboned@lists.uoregon.edu  Wed Jan 21 18:19:17 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17028
	for <mboned-archive@lists.ietf.org>; Wed, 21 Jan 2004 18:19:17 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0LNDomF011525
	for <mboned-outgoing@darkwing.uoregon.edu>; Wed, 21 Jan 2004 15:13:50 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i0LNDo6I011510
	for mboned-outgoing; Wed, 21 Jan 2004 15:13:50 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0LNDnMH011442
	for <mboned@lists.uoregon.edu>; Wed, 21 Jan 2004 15:13:49 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0LNDm3K020069;
	Wed, 21 Jan 2004 15:13:48 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0LNDmd6020066;
	Wed, 21 Jan 2004 15:13:48 -0800
Date: Wed, 21 Jan 2004 15:13:48 -0800
Message-Id: <200401212313.i0LNDmd6020066@m106.maoz.com>
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: draft agenda for Seoul
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Please forward agenda items to me/the list. 

	Thanks,

	Dave

----

MBONE Deployment WG (mboned)

Date/Time TBD
=============

CHAIR: David Meyer <dmm@1-4-5.net>

AGENDA

 o Agenda Bashing					5 minutes
   Meyer                                           

 o Charter Update/Review                                20 minutes
   Meyer 

 o Review and status of work items			30 minutes
   Active Drafts
   -------------
   draft-ietf-mboned-ssm232-07.txt			5 minutes   
     Shepherd, et al
   draft-ietf-mboned-embeddedrp-00.txt			5 minutes
     Savola/Haberman
   draft-ietf-mboned-ipv4-mcast-unusable-01.txt		5 minutes
     Nickless
   draft-ietf-mboned-ipv4-uni-based-mcast-01.txt	5 minutes
     Thaler
   draft-ietf-mboned-msdp-deploy-05.txt			5 minutes
     McBride, et al
   draft-ietf-mboned-rfc3171bis-01.txt			5 minutes
     Albanna, et al

   Expired Drafts
   -------------
   draft-ietf-mboned-iesg-gap-analysis-01.txt


 o Update on the IMDOC Initiative/charter issues       45 minutes
   Meylor/Meyer
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


From owner-mboned@lists.uoregon.edu  Sat Jan 24 06:50:11 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06226
	for <mboned-archive@lists.ietf.org>; Sat, 24 Jan 2004 06:50:11 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0OBYOMR011185
	for <mboned-outgoing@darkwing.uoregon.edu>; Sat, 24 Jan 2004 03:34:24 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i0OBYOVq011184
	for mboned-outgoing; Sat, 24 Jan 2004 03:34:24 -0800 (PST)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0OBYMbf011177
	for <mboned@lists.uoregon.edu>; Sat, 24 Jan 2004 03:34:23 -0800 (PST)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i0OBYFY31041;
	Sat, 24 Jan 2004 13:34:15 +0200
Date: Sat, 24 Jan 2004 13:34:15 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: mboned@lists.uoregon.edu
cc: Lehtonen Rami <rami.lehtonen@teliasonera.com>, <dmm@1-4-5.net>
Subject: mboned: New I-D on PIM-SM multicast routing security
Message-ID: <Pine.LNX.4.44.0401241312170.30601-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk

Hello all,

When discussing the security properties of Embedded RP at the last
IETF, it was identified that it would be useful to analyze the
multicast routing security issues in general.

So, me, Rami Lehtonen and Dave Meyer got down to it.  Here's the 
result.  The main thing it lacks at the moment are concrete proposals 
on which kind of rate-limiting (etc.) mechanisms would be useful.   
We'd like to get feedback/discussion on that (and other comments are 
also very welcome).

http://www.ietf.org/internet-drafts/draft-savola-mboned-mroutesec-00.txt

Comments welcome.  Rami acts as the editor of the document.

Pekka, Rami & Dave

---------- Forwarded message ----------
Date: Fri, 23 Jan 2004 16:00:05 -0500
From: Internet-Drafts@ietf.org
To: IETF-Announce:  ;
Subject: I-D ACTION:draft-savola-mboned-mroutesec-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: PIM-SM Multicast Routing Security Issues and Enhancements
	Author(s)	: P. Savola
	Filename	: draft-savola-mboned-mroutesec-00.txt
	Pages		: 17
	Date		: 2004-1-23
	
This memo describes security threats for the larger (intra-domain, or
inter-domain) multicast routing infrastructures. Only Protocol
Independent Multicast - Sparse Mode (PIM-SM) is analyzed, in its
three main operational modes: the traditional Any Source Multicast
(ASM) model, Source-Specific Multicast (SSM) model, and the ASM model
enhanced by the Embedded RP group-to-RP mapping mechanism.  This memo
also describes enhancements to the protocol operations to mitigate
these threats.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-savola-mboned-mroutesec-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-savola-mboned-mroutesec-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:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-savola-mboned-mroutesec-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.


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


From owner-mboned@lists.uoregon.edu  Mon Jan 26 13:31:17 2004
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15151
	for <mboned-archive@lists.ietf.org>; Mon, 26 Jan 2004 13:31:11 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0QIPSsI005508
	for <mboned-outgoing@darkwing.uoregon.edu>; Mon, 26 Jan 2004 10:25:28 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i0QIPSSs005503
	for mboned-outgoing; Mon, 26 Jan 2004 10:25:28 -0800 (PST)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i0QIPRO7005476
	for <mboned@lists.uoregon.edu>; Mon, 26 Jan 2004 10:25:28 -0800 (PST)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0QIPR3K020594
	for <mboned@lists.uoregon.edu>; Mon, 26 Jan 2004 10:25:27 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.10/8.12.10/Submit) id i0QIPRPX020591;
	Mon, 26 Jan 2004 10:25:27 -0800
Date: Mon, 26 Jan 2004 10:25:27 -0800
Message-Id: <200401261825.i0QIPRPX020591@m106.maoz.com>
From: David Meyer <dmm@1-4-5.net>
To: mboned@lists.uoregon.edu
Subject: mboned: draft agenda for Seoul
Sender: owner-mboned@lists.uoregon.edu
Precedence: bulk


	Please let me know if there are additional agenda items.

	Thanks,

	Dave

----
MBONE Deployment WG (mboned)

Date/Time TBD
=============

CHAIR: David Meyer <dmm@1-4-5.net>

AGENDA

 o Administriva						5 minutes

   - Mailing list: majordomo@lists.uoregon.edu
     subscribe mboned

   - Scribe?

   - Blue Sheets

 o Agenda Bashing					5 minutes
   Meyer                                           

 o Charter Update/Review                                20 minutes
   Meyer 

 o Review and status of work items			30 minutes
   Active Drafts
   -------------
   draft-ietf-mboned-ssm232-07.txt			5 minutes   
     Shepherd, et al
   draft-ietf-mboned-embeddedrp-00.txt			5 minutes
     Savola/Haberman
   draft-ietf-mboned-ipv4-mcast-unusable-01.txt		5 minutes
     Nickless
   draft-ietf-mboned-ipv4-uni-based-mcast-01.txt	5 minutes
     Thaler
   draft-ietf-mboned-msdp-deploy-05.txt			5 minutes
     McBride, et al
   draft-ietf-mboned-rfc3171bis-01.txt			5 minutes
     Albanna, et al

   Expired Drafts
   -------------
   draft-ietf-mboned-iesg-gap-analysis-01.txt

 o  PIM-SM Multicast Routing Security Issues and Enhancements
    draft-savola-mboned-mroutesec-00.txt
    Savola, et. al					10 minutes

 o Multicast Address Allocation Issues
   draft-ietf-mboned-rfc3171bis-01.txt
   All							10 minutes

 o Update on the IMDOC Initiative/charter issues        40 minutes
   Meylor/Meyer
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive:  http://darkwing.uoregon.edu/~llynch/mboned/


