Stig Venaas | 30 Mar 19:46 2015

Seeking volunteers for multicast YANG model design team

Hi

As I mentioned in the mboned meeting, the pim wg is forming a design
team to work on YANG multicast models. The work will focus on models
related to the pim protocols, but also IGMP/MLD.

We have several vendors, but would like to see operators participating
as well. Please get in touch with me if you're interested. The goal is
to come up with models fairly quickly. We will probably be meeting
virtually every 2 weeks.

Stig

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

Leonard Giuliano | 25 Mar 15:36 2015
Picon

MBONED draft minutes


Draft notes from yesterday's lively and spirited MBONED meeting (thank you 
Duke F. for taking them).  Please take a look while it's fresh on your 
mind and send any edits as it was tough to keep up with all the fast and 
furious discussions.

Agenda begins:
 	Status of Active WG Docs
 	RFC7450 Greg B, finally made to RFC status after  14 years

Percy Tarapore presented : (draft-tarapore-mboned-multicast-cdni)
 	Percy would like to know if name should be changes, what version, 
need guidance
o	Lenny  recommend name change and version to start at zero
 	Lenny questioned relevance of AMT tunnel  (section 3)
 	Percy ask for thoughts where 2 domains my not utilize same 
protocols (section 4.2)
o	From audience
 	1st  recommendation is to put into separate document
 	2nd recommendation is to state in document that this will not be 
addressed
 	3rd recommendation is if there is a consensus that this is not a 
good idea, then do not put into document.  Do not need to include every 
corner case/crazy idea a SP might have.
 	(there were other comments, but they fit into the same as above)
 	Asking for overall feedback (section 4.3)
 	Lenny: what about ASM?  Specifically, should MSDP be mentioned 
since it has been used for peering in the past?
 	Consensus: No, should focus on SSM only for interdomain and not 
document ASM since it is not recommended.
(Continue reading)

Greg Shepherd | 24 Mar 20:11 2015
Picon

Open Source AMT

_______________________________________________
MBONED mailing list
MBONED <at> ietf.org
https://www.ietf.org/mailman/listinfo/mboned
Toerless Eckert | 6 Mar 17:54 2015
Picon

MBoned: Re: WG Review: L3VPN Service Model (l3sm)

Any thoughts on this ? Anybody from mboned planning to contribute to
this work to ensure that L3VPN multicast would be represented in the
data model created ?

In-Reply-To: <20150306163644.31050.21402.idtracker <at> ietfa.amsl.com>

On Fri, Mar 06, 2015 at 08:36:44AM -0800, The IESG wrote:
> From: The IESG <iesg-secretary <at> ietf.org>
> To: IETF-Announce <ietf-announce <at> ietf.org>
> Subject: 
> 
> A new IETF working group has been proposed in the Operations and
> Management Area. The IESG has not made any determination yet. The
> following draft charter was submitted, and is provided for informational
> purposes only. Please send your comments to the IESG mailing list (iesg
> at ietf.org) by 2015-03-16.
> 
> L3VPN Service Model  (l3sm)
> ------------------------------------------------
> Current Status: Proposed WG
> 
> Assigned Area Director:
>   Benoit Claise <bclaise <at> cisco.com>
> 
> 
> Charter:
> 
> The IETF and the industry in general is currently specifying a set of
> YANG models for network element and protocol configuration. This is an
> essential first step, but the end goal is full system configuration that
> allows the deployment of services across networks. Services are built
> from a combination of network element and protocol configuration, but are
> specified to service users in more abstract terms.
> 
> The Layer Three Virtual Private Network Service Model (L3SM) working
> group is a short-lived WG tasked to create a YANG data model that
> describes a L3VPN service (a L3VPN service model) that can be used for
> communication between customers and network operators, and to provide
> input to automated control and configuration applications.
> 
> It needs to be clearly understood that this L3VPN service model is not an
> L3VPN configuration model. That is, it does not provide details for
> configuring network elements or protocols. Instead it contains the
> characteristics of the service, as discussed between the operators and
> their customers. A separate process is responsible for mapping this
> service model onto the protocols and network elements depending on how
> the network operator chooses to realise the service.
> 
> The deliverable from this working group will provide information to
> evaluate the set of YANG models that have already been developed or are
> under development, and will help identify any missing models or details. 
> The deliverable can be viewed as driving requirements for protocol
> configuration model so that the service parameters can be mapped into
> inputs used by the protocol models.
> 
> It is hoped that this working group will provide evidence that such
> service models can be quickly constructed and agreed upon. If successful,
> further service models may be developed in other working groups
> 
> The working group should consider draft-l3vpn-service-yang as a starting
> point.
> 
> Milestones:
>   Jan 2016 - L3VPN Service (YANG) Model to the IESG for publication as
> Proposed Standard RFC
>   Jan 2016 - Close the working group

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

internet-drafts | 4 Mar 08:14 2015
Picon

I-D Action: draft-ietf-mboned-multrans-addr-acquisition-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           : Address Acquisition For Multicast Content When Source and Receiver Support Differing IP Versions
        Authors         : Tina Tsou
                          Axel Clauberg
                          Mohamed Boucadair
                          Stig Venaas
                          Qiong Sun
	Filename        : draft-ietf-mboned-multrans-addr-acquisition-05.txt
	Pages           : 10
	Date            : 2015-03-03

Abstract:
   Each IPTV operator has their own arrangements for pre-provisioning
   program information including addresses of the multicast groups
   corresponding to broadcast programs on the subscriber receiver.
   During the transition from IPv4 to IPv6, scenarios can occur where
   the IP version supported by the receiver differs from that supported
   by the source.  This memo examines what has to be done to allow the
   receiver to acquire multicast address information in the version it
   supports in such scenarios.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-multrans-addr-acquisition/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-multrans-addr-acquisition-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-multrans-addr-acquisition-05

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 | 2 Mar 17:02 2015
Picon

Call for MBONED agenda items in Dallas


The MBONED mtg is scheduled for Tues, 3/24, at 1PM.  Rather than trying to 
fit both MBONED and PIM in the same time slot, we will go consecutively in 
the same room (PIM  <at>  9-11:30AM, MBONED  <at>  1-3PM, lunch in between).

If you would like an agenda slot to present in MBONED, please email Greg 
and me with your draft name and the amount of time you'd like.

-Lenny

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

Leonard Giuliano | 19 Feb 00:21 2015
Picon

RFC 7450 on Automatic Multicast Tunneling (fwd)


The AMT spec is finally an RFC- just 2 days shy of it's 14th birthday. 
Thanks go out to the many folks who have coathored, edited and contributed 
to this document over the years.  And very special recognition goes to 
Greg Bumgardner, who for the last 3 years has worked tirelessly to get 
this document passed the longest yard and over the goal line.

-Lenny

---------- Forwarded message ----------
Date: Wed, 18 Feb 2015 15:02:16 -0800
From: rfc-editor <at> rfc-editor.org
To: ietf-announce <at> ietf.org, rfc-dist <at> rfc-editor.org
Cc: mboned <at> ietf.org, drafts-update-ref <at> iana.org, rfc-editor <at> rfc-editor.org
Subject: [MBONED] RFC 7450 on Automatic Multicast Tunneling

A new Request for Comments is now available in online RFC libraries.

         RFC 7450

         Title:      Automatic Multicast Tunneling
         Author:     G. Bumgardner
         Status:     Standards Track
         Stream:     IETF
         Date:       February 2015
         Mailbox:    gbumgard <at> gmail.com
         Pages:      82
         Characters: 188711
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-mboned-auto-multicast-18.txt

         URL:        https://www.rfc-editor.org/info/rfc7450

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.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   https://www.ietf.org/mailman/listinfo/ietf-announce
   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

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

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

rfc-editor | 19 Feb 00:02 2015

RFC 7450 on Automatic Multicast Tunneling

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7450

        Title:      Automatic Multicast Tunneling 
        Author:     G. Bumgardner
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2015
        Mailbox:    gbumgard <at> gmail.com
        Pages:      82
        Characters: 188711
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mboned-auto-multicast-18.txt

        URL:        https://www.rfc-editor.org/info/rfc7450

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.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor <at> rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

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

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


Gmane