Greg Shepherd | 8 Dec 20:31 2014
Picon

Fwd: [RFC State] <draft-ietf-mboned-auto-multicast-18> has been added to the RFC Editor database

Congratulations to everyone who contributed and endured! And a huge Thank You to Greg Bumgardner for sticking with the Author roll throughout the discuss resolutions.

Cheers,
Greg

---------- Forwarded message ----------
From: <rfc-editor <at> rfc-editor.org>
Date: Mon, Dec 8, 2014 at 11:19 AM
Subject: [RFC State] <draft-ietf-mboned-auto-multicast-18> has been added to the RFC Editor database
To: gbumgard <at> gmail.com
Cc: mboned-ads <at> tools.ietf.org, mboned-chairs <at> tools.ietf.org, rfc-editor <at> rfc-editor.org, lenny <at> juniper.net


Author(s),

We have received notice that your document draft-ietf-mboned-auto-multicast-18 has
been approved for publication as an RFC.  The document has
been added to the RFC Editor queue and you can check the status at
<http://www.rfc-editor.org/queue2.html#draft-ietf-mboned-auto-multicast>

If you submitted your XML file using the I-D submission tool, we have
already retrieved it.  If you did not submit the XML file via the I-D
submission tool, or if you have an updated version (e.g., updated
contact information), please send us the XML file at this time.  Please
attach the file as draft-ietf-mboned-auto-multicast-18.xml, and specify
any differences between the approved I-D and the document that the XML
produces.  We recommend using xml2rfc v2 <http://xml.resource.org/> to create
your document.  See the RSE's message about the RFC Editor's transition to
xml2rfc v2 here
<http://www.rfc-editor.org/pipermail/rfc-interest/2013-December/005835.html>.

If you created this document using -ms nroff, please send us the
source file.

This should help increase the pace with which documents move through
the RFC Editor queue.

Please let us know if you have any questions.

Thank you.

The RFC Editor Team


_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned
The IESG | 8 Dec 18:27 2014
Picon

Protocol Action: 'Automatic Multicast Tunneling' to Proposed Standard (draft-ietf-mboned-auto-multicast-18.txt)

The IESG has approved the following document:
- 'Automatic Multicast Tunneling'
  (draft-ietf-mboned-auto-multicast-18.txt) as Proposed Standard

This document is the product of the MBONE Deployment Working Group.

The IESG contact persons are Joel Jaeggli and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/

Technical Summary 

  The advantages and benefits provided by multicast technologies are 
  well known.  There are a number of application areas that are ideal 
  candidates for the use of multicast, including media broadcasting, 
  video conferencing, collaboration, real-time data feeds, data 
  replication, and software updates.  Unfortunately, many of these 
  applications lack multicast connectivity to networks that carry 
  traffic generated by multicast sources.  The reasons for the lack of 
  connectivity vary, but are primarily the result of service provider 
  policies and network limitations. 

  Automatic Multicast Tunneling (AMT) is a protocol that uses UDP-based 
  encapsulation to overcome the aforementioned lack of multicast 
  connectivity.  AMT enables sites, hosts or applications that do not 
  have native multicast access to a network with multicast connectivity 
  to a source, to request and receive SSM [RFC4607] and ASM [RFC1112] 
  traffic from a network that does provide multicast connectivity to 
  that source. 

Working Group Summary 

 This document has received strong support from the working group and no
 major controversies existed prior to the arriving at the IESG with 
 this document.

 Subsequent to the previous IESG review, efforts have been made to address IESG  
 discuss issues, deal with IANA concerns and spin up new work associated with  
 congestion guidance for multicast applications.

Document Quality 

  A number of AMT implementations exist today and significant deployment
  experience has been documented.  This document has received thorough
  review from the working group, and many have contributed to this effort
  over the last 11+ years.  In particular, Dave Thaler, Tom Pusateri,
  Thomas Morin and Greg Bumgardner deserve credit for most of the
  authorship of this document, and Bob Sayko, Doug Nortz and their
  colleagues at ATT deserve credit for extremely thorough review of the
  document.

Personnel 

  Lenny Giuliano is the Document Shepherd, Joel Jaeggli is the 
  Responsible Area Director. 

RFC Editor Note

OLD> Gateway support for the Teardown message is OPTIONAL but RECOMMENDED.
NEW> Gateway support for the Teardown message is RECOMMENDED.

Please move the reference to [RFC1321]  from the NORMATIVE reference section to the INFORMATIVE reference section.

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

internet-drafts | 1 Dec 22:24 2014
Picon

I-D Action: draft-ietf-mboned-auto-multicast-18.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 Multicast Tunneling
        Author          : Gregory Bumgardner
	Filename        : draft-ietf-mboned-auto-multicast-18.txt
	Pages           : 82
	Date            : 2014-12-01

Abstract:
   This document describes Automatic Multicast Tunneling (AMT), a
   protocol for delivering multicast traffic from sources in a
   multicast-enabled network to receivers that lack multicast
   connectivity to the source network.  The protocol uses UDP
   encapsulation and unicast replication to provide this functionality.

   The AMT protocol is specifically designed to support rapid deployment
   by requiring minimal changes to existing network infrastructure.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-auto-multicast-18

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-auto-multicast-18

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

Greg Shepherd | 11 Nov 21:07 2014
Picon

IETF 91 MBONED WG Minutes

Please review and respond. Thanks!

-----

MBONED Minutes

IETF 91

Nov 11, 2014


AMT draft status:

Joel Ja- AMT is close, only nonce discuss to review proposed text


BCP draft preso (Percy Terapore):

Chairs - Will work with authors to coordinate outreach to operators for feedback

Joel Jaglie- Change ‘AD’ to ‘Admin Domain’ if you want this to move faster

Stig Venaas - send to NOGs

Mike McBride - Have you presented at nanog? But we work with operators and this is really good .

Percy Terapore - will change AD to admin domain


Mcast MRAC:

Chair - Any feedback from security?

Michael Abrahamsen - mcast for 10 years. Lots of protocols to mcast running. here’s list of more protocols to operational reqs. It’s already operationally hard. Even LDP req for MPLS is a bit much. Setting up PIM and MSDP etc is already complex. There a tendency to invent new stuff which is operationally hard

Bill Attwod - the original proposal suggested changes to IGMP which was too much to ask. 

Stig Venaas - I don’t understand all of the security protocols 100%. This seems to make sense from a protocol point of view. Is this the right way to solve this? This is also in PIM. This does have benefits compared to the early proposals. Do we need to protect content, restrict access or restrict distribution

Bill Attwood - If ACL is enough then this isn’t needed

Stig Venaas - shared medium could distribute content to non-authenticated users

Bill this doesn’t protect that case

 - there’s a whole group missing from your diagram, switches

Bill Attwood - I’m aware of this issue, but haven’t yet explored.

Michael Abrahamsen - when you invent something new you need some spoofing protection - back to the shared medium issue. Some people provision ACLs for mcast distribution

Bill Attwood  - for IPTV, ACLs are implemented based on purchased agreements

Toerless Eckert - love to hear from operators that this solution solves problems they have



BIER update

Michael Abrahamsen - Is this tied to SPRING

Ice Wjiands- There are some similarities, but there are no SPRING procures we depend on for SPRING

Michael Abrahamsen - Its more of an operational question, its not much different

Dino Farinacci - I think what your saying is Spring has a new paradigm for both Uni and Multi, are you asking the BIER people to just use SPRING?

Michael Abrahamsen - When you’re telling people about it, it could benefit to tell them about it at the same time.

Ice Wjiands - Spring is source routing which is effectively impossible for multicast.


_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned
Greg Shepherd | 10 Nov 18:03 2014
Picon

BIER BoF Today, w/ WebEx details

bier
Monday, November 10, 2014
1:00 pm | Hawaii Time (Honolulu, GMT-10:00) | 2 hr

Join WebEx meeting:
https://workgreen.webex.com/workgreen/j.php?MTID=mdfb183b4cd0d2cfaeceacf3950895a00
Meeting number: 825 308 148
Meeting password: 1234

Looking forward to seeing (hearing) you all there!

Cheers,
Greg
_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned
internet-drafts | 27 Oct 15:24 2014
Picon

I-D Action: draft-tarapore-mboned-multicast-cdni-07.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           : Multicasting Applications Across Inter-Domain Peering Points
        Authors         : Percy S. Tarapore
                          Robert Sayko
                          Greg Shepherd
                          Toerless Eckert
                          Ram Krishnan
	Filename        : draft-tarapore-mboned-multicast-cdni-07.txt
	Pages           : 27
	Date            : 2014-10-27

Abstract:
   This document examines the process of transporting applications via
   multicast across inter-domain peering points. The objective is to
   describe the setup process for multicast-based delivery across
   administrative domains and document supporting functionality to
   enable this process.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-tarapore-mboned-multicast-cdni/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-tarapore-mboned-multicast-cdni-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-tarapore-mboned-multicast-cdni-07

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

internet-drafts | 27 Oct 09:18 2014
Picon

I-D Action: draft-ietf-mboned-mtrace-v2-11.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           : Mtrace Version 2: Traceroute Facility for IP Multicast
        Authors         : Hitoshi Asaeda
                          WeeSan Lee
	Filename        : draft-ietf-mboned-mtrace-v2-11.txt
	Pages           : 33
	Date            : 2014-10-27

Abstract:
   This document describes the IP multicast traceroute facility, named
   Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
   requires special implementations on the part of routers.  This
   specification describes the required functionality in multicast
   routers, as well as how an Mtrace2 client invokes a query and
   receives a reply.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-mtrace-v2/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-mtrace-v2-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-mtrace-v2-11

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

Leonard Giuliano | 16 Oct 20:07 2014
Picon

call for agenda items in MBONED


If you have something you'd like to present in MBONED in Honolulu, please 
let the chairs know.  Please include the name of the draft and the amount 
of time you'd like.

We are tentatively scheduled for Tues, 9-11:30AM.  BTW, this will be the 
first time where will hold our meeting jointly with the PIM WG.  We 
welcome feedback on how well this experiment works out.

Thanks,
Greg and Lenny

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

Tom Taylor | 3 Oct 03:50 2014
Picon

Comments on draft-ietf-mboned-64-multicast-address-format-06

I have a couple of comments on 
draft-ietf-mboned-64-multicast-address-format-06.

(1) Sec. 4.3 RFC 3307 requires the low-order 32 bits of a 
dynamically-allocated multicast address to lie in the range 0x80000000 
to 0xFFFFFFFF. That means the high-order bit of any embedded IPv4 
address may have to be flipped. You may potentially need a new flag to 
indicate this, which means another iteration through 6man.

(2) Sec. 3.5 should refer to RFC 5952.

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned

Greg Shepherd | 25 Sep 21:53 2014
Picon

Mulit-point (Multicast) BoF of interest

Hi Folks,

If you are interested in a new forwarding mechanism for Multicast, called: Bit Indexed Explicit Replication (BIER), please feel free to register to the BOF list bier <at> ietf.org(https://www.ietf.org/mailman/listinfo/bier)

We have a BOF request pending for Hawaii.

http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#Routing

These drafts are available for reading, more will follow later.

https://tools.ietf.org/id/draft-shepherd-bier-problem-statement-00.txt
https://tools.ietf.org/id/draft-wijnands-bier-architecture-00.txt
https://tools.ietf.org/id/draft-wijnands-mpls-bier-encapsulation-00.txt

Please join the email list and help generate discussion if you find this work interesting. I look forward to seeing all of you in Hawaii!

Cheers,
Greg
_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned
IJsbrand Wijnands | 25 Sep 10:57 2014
Picon

BIER BOF

Hi Folks,

If you are interested in a new forwarding mechanism for Multicast, called: Bit Indexed Explicit
Replication (BIER), please feel free to register to the BOF list bier <at> ietf.org (https://www.ietf.org/mailman/listinfo/bier)

We have a BOF request pending for Hawaii.

http://trac.tools.ietf.org/bof/trac/wiki/WikiStart#Routing

These drafts are available for reading, more will follow later.

https://tools.ietf.org/id/draft-wijnands-bier-architecture-00.txt
https://tools.ietf.org/id/draft-wijnands-mpls-bier-encapsulation-00.txt

Thx,

Ice.

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned


Gmane