headers
Ron Bonica | 1 Oct 2007 19:08
Favicon

draft-ietf-behave-multicast

Folks,

draft-ietf-behave-multicast is up for IESG review this Thursday. I know
that a few of you have already reviewed and commented on this document,
so there shouldn't be many problems.

However, if anyone sees any reason why this document should not
progress, please email the list ASAP.

                                    Ron

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www1.ietf.org/mailman/listinfo/mboned
Permalink | Reply | 1 comment |
headers
Tim Chown | 2 Oct 2007 10:09
Picon
Favicon

Re: draft-ietf-behave-multicast

On Mon, Oct 01, 2007 at 01:08:22PM -0400, Ron Bonica wrote:
> Folks,
> 
> draft-ietf-behave-multicast is up for IESG review this Thursday. I know
> that a few of you have already reviewed and commented on this document,
> so there shouldn't be many problems.
> 
> However, if anyone sees any reason why this document should not
> progress, please email the list ASAP.

Just a handful of relatively minor comments:

1)  The draft mentions MLD and MLDv2, yet states that IPv6 is out of scope
    (though there are interesting ways to have a proxy proxy between IPv4
     and IPv6 groups as per Stig's draft :)

2)  The draft appears to focus on IGMP handling by NAT (presumably typically
    SOHO devices), so maybe the title of the document should reflect that.
    The text states that NATed networks and PIM handling are out of scope so 
    maybe we should call the document something more specific?

3)  The text refers to 'inside segment(s)', does that mean that the
    text is in fact covering a case with a NAT device serving multiple
    internal subnets?   Or is the text referring to forwarding between
    internal interfaces purely layer 2 forwarding/bridging?

4)  Perhaps clarify more clearly where Reports should be expected to flow 
    inside->out, and Queries from outside->in.

5)  REQ5 mentions 'a protocol'... a bit vague - maybe just say the issue
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Eubanks | 2 Oct 2007 23:31

Note these dates

With regards to Vancouver :

November 12, Monday - Internet Draft Cut-off for initial document  
(-00) submission by 09:00 ET (14:00 UTC/GMT), upload using IETF ID  
Submission Tool.

November 19, Monday - Internet Draft final submission cut-off by  
09:00 ET (14:00 UTC/GMT), upload using IETF ID Submission Tool.

November 21, Wednesday - Draft Working Group agendas due by 17:00 ET  
(22:00 UTC/GMT), upload using IETF Meeting Materials Management Tool.

November 23, Friday - Early-Bird registration and payment cut-off at  
12:00 noon ET (17:00 UTC/GMT)

November 26, Monday - Revised Working Group agendas due by 12:00 ET  
(17:00 UTC/GMT), upload using IETF Meeting Materials Management Tool.

November 26, Monday - Registration cancellation cut-off at 17:00 ET  
(22:00 UTC/GMT)

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www1.ietf.org/mailman/listinfo/mboned
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 4 Oct 2007 23:15
Picon
Favicon

I-D ACTION:draft-ietf-mboned-maccnt-req-05.txt

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		: Requirements for Multicast AAA coordinated 
                          between Content Provider(s) and Network 
                          Service Provider(s)
	Author(s)	: H. He, et al.
	Filename	: draft-ietf-mboned-maccnt-req-05.txt
	Pages		: 25
	Date		: 2007-10-4
	
This memo presents requirements in the area of accounting and 
     access control for IP multicasting.  The scope of the requirements 
     is limited to cases that Authentication, Accounting and 
     Authorization (AAA) functions are coordinated between Content 
     Provider(s) and Network Service Provider(s). General requirements 
     for accounting and admission control capabilities including 
     quality-of-service (QoS) related issues are listed.  This memo 
     assumes that these capabilities can be realized by functions 
     implemented at edges of a network based on IGMP or MLD.  Finally, 
     cases for Content Delivery Services (CDS) are described as 
     application examples which could benefit from multicasting 
     accounting and access control capabilities as described in the 
     memo. 

     This memo defines requirements related to AAA issues for multi-
     entity provider models in which the network service provider and 
     content provider cooperate to provide CDS and various related AAA 
     functions for purposes such as protecting and accounting for the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Internet-Drafts | 8 Oct 2007 18:15
Picon
Favicon

I-D ACTION:draft-ietf-mboned-auto-multicast-08.txt

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		: Automatic IP Multicast Without Explicit Tunnels (AMT)
	Author(s)	: D. Thaler, et al.
	Filename	: draft-ietf-mboned-auto-multicast-08.txt
	Pages		: 38
	Date		: 2007-10-8
	
Automatic Multicast Tunneling (AMT) allows multicast communication
   amongst isolated multicast-enabled sites or hosts, attached to a
   network which has no native multicast support.  It also enables them
   to exchange multicast traffic with the native multicast
   infrastructure and does not require any manual configuration.  AMT
   uses an encapsulation interface so that no changes to a host stack or
   applications are required, all protocols (not just UDP) are handled,
   and there is no additional overhead in core routers.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After
(Continue reading)

Permalink | Reply | 0 comments |
headers
Greg Shepherd | 8 Oct 2007 22:13
Picon

Fwd: Last Call: draft-ietf-mboned-routingarch (Overview of the Internet Multicast Routing Architecture) to BCP

After reviewing this (again) it seems best fit as INFO and not BCP.
Can we make that change request to the IESG?

Greg

---------- Forwarded message ----------
From: The IESG <iesg-secretary <at> ietf.org>
Date: Sep 5, 2007 1:22 PM
Subject: [MBONED] Last Call: draft-ietf-mboned-routingarch (Overview
of the  Internet Multicast Routing Architecture) to BCP
To: IETF-Announce <ietf-announce <at> ietf.org>
Cc: mboned <at> ietf.org

The IESG has received a request from the MBONE Deployment WG (mboned) to
consider the following document:

- 'Overview of the Internet Multicast Routing Architecture '
   <draft-ietf-mboned-routingarch-09.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2007-09-19. Exceptionally,
comments may be sent to iesg <at> ietf.org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mboned-routingarch-09.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13102&rfc_flag=0
(Continue reading)

Permalink | Reply | 8 comments |
headers
Manfredi, Albert E | 9 Oct 2007 01:28
Picon
Favicon

RE: Last Call: draft-ietf-mboned-routingarch (Overview ofthe Internet Multicast Routing Architecture) to BCP

Good comment. I second that.

Bert 

-----Original Message-----
From: Greg Shepherd [mailto:gjshep <at> gmail.com] 
Sent: Monday, October 08, 2007 4:14 PM
To: mboned <at> ietf.org
Subject: Fwd: [MBONED] Last Call: draft-ietf-mboned-routingarch
(Overview ofthe Internet Multicast Routing Architecture) to BCP

After reviewing this (again) it seems best fit as INFO and not BCP.
Can we make that change request to the IESG?

Greg

---------- Forwarded message ----------
From: The IESG <iesg-secretary <at> ietf.org>
Date: Sep 5, 2007 1:22 PM
Subject: [MBONED] Last Call: draft-ietf-mboned-routingarch (Overview
of the  Internet Multicast Routing Architecture) to BCP
To: IETF-Announce <ietf-announce <at> ietf.org>
Cc: mboned <at> ietf.org

The IESG has received a request from the MBONE Deployment WG (mboned) to
consider the following document:

- 'Overview of the Internet Multicast Routing Architecture '
   <draft-ietf-mboned-routingarch-09.txt> as a BCP
(Continue reading)

Permalink | Reply | 7 comments |
headers
Pekka Savola | 9 Oct 2007 07:20
Picon

RE: Last Call: draft-ietf-mboned-routingarch (Overview ofthe Internet Multicast Routing Architecture) to BCP

Hi,

As it appears, this topic came up in IESG review as well.

Could you expand on why you believe Info is more appropriate than a 
BCP?  The draft does include statements about status of deployments 
and makes some recommendations as well, so it isn't just a tutorial on 
multicast routing.

On Mon, 8 Oct 2007, Manfredi, Albert E wrote:
> Good comment. I second that.
>
> Bert
>
> -----Original Message-----
> From: Greg Shepherd [mailto:gjshep <at> gmail.com]
> Sent: Monday, October 08, 2007 4:14 PM
> To: mboned <at> ietf.org
> Subject: Fwd: [MBONED] Last Call: draft-ietf-mboned-routingarch
> (Overview ofthe Internet Multicast Routing Architecture) to BCP
>
> After reviewing this (again) it seems best fit as INFO and not BCP.
> Can we make that change request to the IESG?
>
> Greg
>
> ---------- Forwarded message ----------
> From: The IESG <iesg-secretary <at> ietf.org>
> Date: Sep 5, 2007 1:22 PM
> Subject: [MBONED] Last Call: draft-ietf-mboned-routingarch (Overview
(Continue reading)

Permalink | Reply | 6 comments |
headers
Greg Shepherd | 9 Oct 2007 13:44
Picon

Re: Last Call: draft-ietf-mboned-routingarch (Overview ofthe Internet Multicast Routing Architecture) to BCP

On 10/8/07, Pekka Savola <pekkas <at> netcore.fi> wrote:
> Hi,
>
> As it appears, this topic came up in IESG review as well.
>
> Could you expand on why you believe Info is more appropriate than a
> BCP?  The draft does include statements about status of deployments
> and makes some recommendations as well, so it isn't just a tutorial on
> multicast routing.

Even with the recommendations it still is a snap-shot of the current
state of mcast.

Greg

> On Mon, 8 Oct 2007, Manfredi, Albert E wrote:
> > Good comment. I second that.
> >
> > Bert
> >
> > -----Original Message-----
> > From: Greg Shepherd [mailto:gjshep <at> gmail.com]
> > Sent: Monday, October 08, 2007 4:14 PM
> > To: mboned <at> ietf.org
> > Subject: Fwd: [MBONED] Last Call: draft-ietf-mboned-routingarch
> > (Overview ofthe Internet Multicast Routing Architecture) to BCP
> >
> > After reviewing this (again) it seems best fit as INFO and not BCP.
> > Can we make that change request to the IESG?
> >
(Continue reading)

Permalink | Reply | 3 comments |
headers
Pekka Savola | 9 Oct 2007 14:19
Picon

Re: Last Call: draft-ietf-mboned-routingarch (Overview ofthe Internet Multicast Routing Architecture) to BCP

On Tue, 9 Oct 2007, Greg Shepherd wrote:
> On 10/8/07, Pekka Savola <pekkas <at> netcore.fi> wrote:
>> As it appears, this topic came up in IESG review as well.
>>
>> Could you expand on why you believe Info is more appropriate than a
>> BCP?  The draft does include statements about status of deployments
>> and makes some recommendations as well, so it isn't just a tutorial on
>> multicast routing.
>
> Even with the recommendations it still is a snap-shot of the current
> state of mcast.

Isn't that pretty close to the definition of "best current practice"? 
Is there a conflict somewhere?

--

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www1.ietf.org/mailman/listinfo/mboned
Permalink | Reply | 2 comments |

Gmane