
From lenny@juniper.net  Wed Jan  5 14:05:44 2011
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96BB83A6CD9 for <mboned@core3.amsl.com>; Wed,  5 Jan 2011 14:05:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYLCUAbEx4yY for <mboned@core3.amsl.com>; Wed,  5 Jan 2011 14:05:43 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by core3.amsl.com (Postfix) with ESMTP id D7D383A6C52 for <mboned@ietf.org>; Wed,  5 Jan 2011 14:05:42 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTSTrtbAMMrQfb5e/hwTB69+2yyxViGy+@postini.com; Wed, 05 Jan 2011 14:07:51 PST
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 5 Jan 2011 14:06:55 -0800
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id p05M6sU38869; Wed, 5 Jan 2011 14:06:54 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (localhost [127.0.0.1])	by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id p05M6sI4036067; Wed, 5 Jan 2011 14:06:54 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost)	by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id p05M6sgK036064;	Wed, 5 Jan 2011 14:06:54 -0800 (PST)
X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs
Date: Wed, 5 Jan 2011 14:06:54 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
Message-ID: <20110105133836.X27165@zircon.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Cc: "Shepherd, Greg -- Greg Shepherd" <gjshep@gmail.com>
Subject: [MBONED] IETF 80 (Prague) agenda requests
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 22:05:44 -0000

It's that time again to call for agenda items.  If you'd like to request a 
time slot in MBONED in Prague, please reply to the chairs with the topic 
and amount of time needed.  We'd like to get the agenda determined early 
this time, so please send in requests by Jan 20.

Thanks,
Lenny and Greg

From tme@americafree.tv  Wed Jan  5 20:12:09 2011
Return-Path: <tme@americafree.tv>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A33603A6ECA for <mboned@core3.amsl.com>; Wed,  5 Jan 2011 20:12:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.19
X-Spam-Level: 
X-Spam-Status: No, score=-102.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JM8KznHY49oe for <mboned@core3.amsl.com>; Wed,  5 Jan 2011 20:12:08 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id BCF2A3A6EBC for <mboned@ietf.org>; Wed,  5 Jan 2011 20:12:08 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id A5C2C995C22E for <mboned@ietf.org>; Wed,  5 Jan 2011 23:14:15 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Jan 2011 23:14:15 -0500
Message-Id: <A879EDC0-15F6-4F7C-9CB4-BC96E6FB5271@americafree.tv>
To: MBONED WG <mboned@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [MBONED] Next generation TV over the Internet: This revolution will be televised
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 04:12:09 -0000

Thought people would want to see this by our co-chair.=20

Marshall

=
http://www.networkworld.com/news/tech/2011/010511-tech-update-next-gen-tv.=
html



From tme@americafree.tv  Thu Jan  6 18:04:04 2011
Return-Path: <tme@americafree.tv>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A6543A6E37 for <mboned@core3.amsl.com>; Thu,  6 Jan 2011 18:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.207
X-Spam-Level: 
X-Spam-Status: No, score=-102.207 tagged_above=-999 required=5 tests=[AWL=0.392, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2aVMDp4lLWV for <mboned@core3.amsl.com>; Thu,  6 Jan 2011 18:04:03 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 2AED63A6D1C for <mboned@ietf.org>; Thu,  6 Jan 2011 18:04:03 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 50B45997AA57 for <mboned@ietf.org>; Thu,  6 Jan 2011 21:06:09 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 6 Jan 2011 21:06:07 -0500
References: <017401cbadf9$eb9eb5a0$c2dc20e0$@com>
To: MBONED WG <mboned@ietf.org>
Message-Id: <769E7D25-A1BE-41D5-8DC2-8A117C77A84E@americafree.tv>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [MBONED] Fwd: [Softwires] 6rd multicast
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 02:04:04 -0000

I thought this group should see this.

Regards
Marshall


Begin forwarded message:

> From: Tina Tsou <tena@huawei.com>
> Date: January 6, 2011 6:32:01 PM EST
> To: 'Softwires' <softwires@ietf.org>
> Subject: [Softwires] 6rd multicast
> 
> Hi all,
> 
> http://datatracker.ietf.org/doc/draft-tsou-softwire-6rd-multicast/
> 
> is available.
> 
> This document describes how IPv6 multicast can be extended across an
>   IPv4 network to an IPv6 host, using the native multicast capabilities
>   of the IPv4 network.
> 
> This is a first draft, and definitely needs more work.
> 
> 
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
> 
> 
> 
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
> 


From Internet-Drafts@ietf.org  Fri Jan  7 00:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AECF43A67F0; Fri,  7 Jan 2011 00:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.361
X-Spam-Level: 
X-Spam-Status: No, score=-102.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBWIpMMBiKES; Fri,  7 Jan 2011 00:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DBCD3A67E2; Fri,  7 Jan 2011 00:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110107081501.18122.34709.idtracker@localhost>
Date: Fri, 07 Jan 2011 00:15:01 -0800
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action:draft-ietf-mboned-mtrace-v2-08.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 08:15:02 -0000

--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           : Mtrace Version 2: Traceroute Facility for IP Multicast
	Author(s)       : H. Asaeda, et al.
	Filename        : draft-ietf-mboned-mtrace-v2-08.txt
	Pages           : 41
	Date            : 2011-01-07

This document describes the IP multicast traceroute facility.  Unlike
unicast traceroute, multicast traceroute requires special
implementations on the part of routers.  This specification describes
the required functionality in multicast routers, as well as how
management applications can use the router functionality.

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

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

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: Message/External-body; name="draft-ietf-mboned-mtrace-v2-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-07000237.I-D@ietf.org>


--NextPart--

From asaeda@sfc.wide.ad.jp  Fri Jan  7 00:57:53 2011
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1AE93A67E5 for <mboned@core3.amsl.com>; Fri,  7 Jan 2011 00:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.096
X-Spam-Level: 
X-Spam-Status: No, score=-99.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQ0TP8vqv6sm for <mboned@core3.amsl.com>; Fri,  7 Jan 2011 00:57:52 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id D4C0E3A67E3 for <mboned@ietf.org>; Fri,  7 Jan 2011 00:57:52 -0800 (PST)
Received: from localhost (unknown [IPv6:2001:200:0:8801:225:ff:feee:626f]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 45D60278091 for <mboned@ietf.org>; Fri,  7 Jan 2011 17:59:56 +0900 (JST)
Date: Fri, 07 Jan 2011 17:59:56 +0900 (JST)
Message-Id: <20110107.175956.185733348.asaeda@sfc.wide.ad.jp>
To: mboned@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
X-Mailer: Mew version 6.2 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [MBONED] revising mtrace2 draft (-08)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2011 08:57:53 -0000

Hello folks,

I've revised the mtrace2 draft to -08 version.
http://www.ietf.org/internet-drafts/draft-ietf-mboned-mtrace-v2-08.txt

The changes are mainly editorial and the draft status is AD review,
but you may need to know some changes for the implementation. Please
read the revised draft carefully and give me your comments.

I summarize the changes that would affect the mtrace2 implementation
as follows;

1. Response -> Reply
   Mtrace2 has three message types, "query", "request", and
   "response". It also has two block types, "standard response" and
   "augumented block", which are finally replied as the mtrace2
   response message. Ron said these namings are confusing. I hence
   changed the name of "response" message to "reply" message.

2. Destination Address -> Mtrace2 Client Address
   The name of "Destination Address" specified in mtrace2 query header
   was the address of mtrace2 querier. This name is ambiguous, hence
   it was changed to "Mtrace2 Client Address".

3. Unnumbered interface
   There was no clear definition about the case if an mtrace2 request/
   reply message reaches on an unnumbered interface. The revised draft
   says that an mtrace2 request/reply should be sent with the address
   of the router's reception interface, but if the router's interface
   address is unnumbered, the router can use one of its numbered
   interface address as the source address.

4. Mtrace2 Query/Request received by non-supported router
   There were no precise information about non-supported router; when
   mtrace2 query/request messages are arrived at a router that does
   not understand mtrace2 messages, what happens? Section 9.1.3 and
   9.2.3 are the corresponding sections.

If you have some question or concern about these changes, please mail
me or to this ML.

Regards,
--
Hitoshi Asaeda

From tme@americafree.tv  Tue Jan 11 01:29:04 2011
Return-Path: <tme@americafree.tv>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 760A33A6A13 for <mboned@core3.amsl.com>; Tue, 11 Jan 2011 01:29:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.241
X-Spam-Level: 
X-Spam-Status: No, score=-102.241 tagged_above=-999 required=5 tests=[AWL=0.358, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6tyo6f3XRkJ for <mboned@core3.amsl.com>; Tue, 11 Jan 2011 01:29:03 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 73D3E3A69F8 for <mboned@ietf.org>; Tue, 11 Jan 2011 01:29:03 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 642789A05C02 for <mboned@ietf.org>; Tue, 11 Jan 2011 04:31:19 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Jan 2011 04:31:18 -0500
References: <20110110194329.11611.49520.idtracker@localhost>
To: MBONED WG <mboned@ietf.org>
Message-Id: <4CEEA5D6-15B4-4ABB-B1B7-E3597D9A4752@americafree.tv>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [MBONED] Fwd: Protocol Action: 'RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions' to Proposed Standard (draft-ietf-avt-rtcp-port-for-ssm-04.txt)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2011 09:29:04 -0000

Seems relevant.=20

Marshall


Begin forwarded message:

> From: The IESG <iesg-secretary@ietf.org>
> Date: January 10, 2011 2:43:29 PM EST
> To: IETF-Announce <ietf-announce@ietf.org>
> Cc: Internet Architecture Board <iab@iab.org>, avt mailing list =
<avt@ietf.org>, avt chair <avt-chairs@tools.ietf.org>, RFC Editor =
<rfc-editor@rfc-editor.org>
> Subject: Protocol Action: 'RTP Control Protocol (RTCP) Port for =
Source-Specific Multicast (SSM) Sessions' to Proposed Standard =
(draft-ietf-avt-rtcp-port-for-ssm-04.txt)
>=20
> The IESG has approved the following document:
> - 'RTP Control Protocol (RTCP) Port for Source-Specific Multicast =
(SSM)
>   Sessions'
>  (draft-ietf-avt-rtcp-port-for-ssm-04.txt) as a Proposed Standard
>=20
> This document is the product of the Audio/Video Transport Working =
Group.
>=20
> The IESG contact persons are Robert Sparks and Gonzalo Camarillo.
>=20
> A URL of this Internet Draft is:
> http://datatracker.ietf.org/doc/draft-ietf-avt-rtcp-port-for-ssm/
>=20
>=20
>=20
> Technical Summary
>=20
> The Session Description Protocol (SDP) has an attribute that allows =
RTP
> applications to specify an address and a port associated with the RTP
> Control Protocol (RTCP) traffic.  In RTP-based source-specific
> multicast (SSM) sessions, the same attribute is used to designate the
> address and the RTCP port of the Feedback Target in the SDP =
description.=20
> However, the RTCP port associated with the SSM session itself cannot =
be
> specified by the same attribute to avoid ambiguity, and thus, is
> required to be derived from the "m=3D" line of the media description.=20=

> Deriving the RTCP port from the "m=3D" line imposes an unnecessary
> restriction.  This document removes this restriction by introducing a
> new SDP attribute.
>=20
>=20
> Working Group Summary
>=20
> The document achieved consensus in the AVT working group.=20
>=20
> Document Quality
>=20
> The document was reviewed by both the AVT and MMUSIC working groups.
>=20
> Personnel
>=20
> Keith Drage is the document shepherd. Robert Sparks is the responsible =
AD.
>=20
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20


From bill@cse.concordia.ca  Wed Jan 12 11:14:39 2011
Return-Path: <bill@cse.concordia.ca>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 627A73A6A16 for <mboned@core3.amsl.com>; Wed, 12 Jan 2011 11:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.575
X-Spam-Level: 
X-Spam-Status: No, score=-1.575 tagged_above=-999 required=5 tests=[AWL=-0.465, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ft8sPpjIOiNR for <mboned@core3.amsl.com>; Wed, 12 Jan 2011 11:14:38 -0800 (PST)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by core3.amsl.com (Postfix) with ESMTP id 462DE3A6A3D for <mboned@ietf.org>; Wed, 12 Jan 2011 11:14:38 -0800 (PST)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from bill@cse.concordia.ca) (8.13.7/8.13.7) with ESMTP id p0CJGvic012120;  Wed, 12 Jan 2011 14:16:57 -0500
Message-ID: <4D2DFE2B.7020809@cse.concordia.ca>
Date: Wed, 12 Jan 2011 14:16:59 -0500
From: Bill Atwood <bill@cse.concordia.ca>
Organization: Concordia University, Department of Computer Science and Software Engineering
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: mboned@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2011/01/12 14:16:57 EST
Cc: Ali Salem <sale_ali@cse.concordia.ca>
Subject: [MBONED] draft-ietf-mboned-auto-multicast
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jan 2011 19:14:39 -0000

Hello,

My student and I are working on a project concerned with AMT, and he is
preparing a formal validation of the AMT message exchanges, using the
AVISPA tools.  The goal is to demonstrate the security of the AMT
exchanges.  We have a question about the security features of AMT, and
we hope that someone on the list will be able to respond to it.

In the latest IETF draft of "Automatic IP Multicast Without Explicit
Tunnels", version 10, under section 5.1.2 entitled "Spoofing
Considerations", the following is mentioned:

An attacker can "affect the group state in the relay or gateway by
spoofing the source address in the join or leave reports", where this
can lead to launching "reflection or denial of service attacks" on the
target. It is further stated that this can be mitigated by using a
"three way handshake between the gateway and the relay for each
multicast membership report or leave".

Given that the Gateway is going to send periodic AMT Membership Updates
in order to keep the state for (Sn,Gn) alive in the relay, how does
initiating the three-way handshake for each multicast membership report
or leave help in avoiding the attacks mentioned in the draft?

Any insight from the draft authors (or anyone else!) will be very much
appreciated.

  Bill Atwood
-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email: bill@cse.concordia.ca
1455 de Maisonneuve Blvd. West    http: //users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

From thomas.morin@orange-ftgroup.com  Thu Jan 13 00:47:23 2011
Return-Path: <thomas.morin@orange-ftgroup.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 447573A69AE for <mboned@core3.amsl.com>; Thu, 13 Jan 2011 00:47:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjEOdBzGGub6 for <mboned@core3.amsl.com>; Thu, 13 Jan 2011 00:47:22 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp11.smtpout.orange.fr [80.12.242.133]) by core3.amsl.com (Postfix) with ESMTP id 4BFCB3A6996 for <mboned@ietf.org>; Thu, 13 Jan 2011 00:47:21 -0800 (PST)
Received: from home.treizh.net ([83.195.245.43]) by mwinf5d21 with ME id uwpi1f00D0wuUWB03wpiNq; Thu, 13 Jan 2011 09:49:43 +0100
Received: from [127.0.0.1] (localhost [127.0.0.1]) by home.treizh.net (Postfix) with ESMTP id BB4C216A45A6 for <mboned@ietf.org>; Thu, 13 Jan 2011 09:49:41 +0100 (CET)
Message-ID: <4D2EBCA4.40400@orange-ftgroup.com>
Date: Thu, 13 Jan 2011 09:49:40 +0100
From: Thomas Morin <thomas.morin@orange-ftgroup.com>
Organization: France Telecom Orange
User-Agent: Mozilla/5.0 (X11; U; ; ; ) Gecko/2010 Thunderbird/3.1.x
MIME-Version: 1.0
To: mboned@ietf.org
References: <4D2DFE2B.7020809@cse.concordia.ca>
In-Reply-To: <4D2DFE2B.7020809@cse.concordia.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MBONED] draft-ietf-mboned-auto-multicast
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jan 2011 08:47:23 -0000

Hi Bill,

Bill Atwood a =C3=A9crit :
> An attacker can "affect the group state in the relay or gateway by
> spoofing the source address in the join or leave reports", where this
> can lead to launching "reflection or denial of service attacks" on the
> target. It is further stated that this can be mitigated by using a
> "three way handshake between the gateway and the relay for each
> multicast membership report or leave".
>
> Given that the Gateway is going to send periodic AMT Membership Updates=

> in order to keep the state for (Sn,Gn) alive in the relay, how does
> initiating the three-way handshake for each multicast membership report=

> or leave help in avoiding the attacks mentioned in the draft?

The periodic Membership Updates are subject to the three-way-handshake=20
as well, so they do not have to be seen as different from a security=20
standpoint, than the first and last, non-periodic, Membership=20
Updates.    (said differently, the "each report or leave" phrase=20
includes the periodic reports)

-Thomas


From lenny@juniper.net  Fri Jan 14 13:34:17 2011
Return-Path: <lenny@juniper.net>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80E783A6C52 for <mboned@core3.amsl.com>; Fri, 14 Jan 2011 13:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTQLF0uaJhgN for <mboned@core3.amsl.com>; Fri, 14 Jan 2011 13:34:16 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id AC7EF3A6BD0 for <mboned@ietf.org>; Fri, 14 Jan 2011 13:34:15 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTTDB6j5fCWMEdkMy3IW1mGhEeuCL4uxc@postini.com; Fri, 14 Jan 2011 13:36:42 PST
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 14 Jan 2011 13:33:45 -0800
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id p0ELXjU38252	for <mboned@ietf.org>; Fri, 14 Jan 2011 13:33:45 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: from zircon.juniper.net (localhost [127.0.0.1])	by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id p0ELXjHT037125	for <mboned@ietf.org>; Fri, 14 Jan 2011 13:33:45 -0800 (PST)	(envelope-from lenny@juniper.net)
Received: from localhost (lenny@localhost)	by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id p0ELXjLS037122	for <mboned@ietf.org>; Fri, 14 Jan 2011 13:33:45 -0800 (PST)
X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs
Date: Fri, 14 Jan 2011 13:33:45 -0800
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
In-Reply-To: <20101213121250.Y27080@zircon.juniper.net>
Message-ID: <20110114132820.U31096@zircon.juniper.net>
References: <20101213121250.Y27080@zircon.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: Re: [MBONED] Adoption of Multicast Performance Monitoring Requirement Draft
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2011 21:34:17 -0000

We have WG consensus to adopt 
draft-bipi-mboned-ip-multicast-pm-requirement as an MBONED WG document.

Can the authors please republish it as 
draft-ietf-mboned-ip-multicast-pm-requirement.


Thanks,
Lenny


On Mon, 13 Dec 2010, Leonard Giuliano wrote:

-) 
-) Draft-bipi-mboned-ip-multicast-pm-requirement was presented in Mboned in
-) Anaheim as well as Beijing.  There was some interest in the room to adopt
-) this draft, so we are taking this to the list.  Please respond here on the
-) list if you are for or against adopting
-) draft-bipi-mboned-ip-multicast-pm-requirement as a working group item in
-) Mboned.
-) 
-) Draft can be found at:
-) http://tools.ietf.org/html/draft-bipi-mboned-ip-multicast-pm-requirement-02
-) 
-) 

From ma697r@att.com  Tue Jan 18 12:34:18 2011
Return-Path: <ma697r@att.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E3813A7079 for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 12:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQF+BLcFjMep for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 12:34:17 -0800 (PST)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id EF90E3A7078 for <mboned@ietf.org>; Tue, 18 Jan 2011 12:34:16 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: ma697r@att.com
X-Msg-Ref: server-13.tower-121.messagelabs.com!1295383013!51976045!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 7429 invoked from network); 18 Jan 2011 20:36:53 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-13.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Jan 2011 20:36:53 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0IKa2wb003005 for <mboned@ietf.org>; Tue, 18 Jan 2011 15:36:03 -0500
Received: from misout7msgusr7c.ugd.att.com (misout7msgusr7c.ugd.att.com [144.155.43.105]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0IKa0Y8002962 for <mboned@ietf.org>; Tue, 18 Jan 2011 15:36:00 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Jan 2011 15:36:50 -0500
Message-ID: <3580159D7E3D824780C0B52AFC6D32E403264D23@misout7msgusr7c.ugd.att.com>
In-Reply-To: <3580159D7E3D824780C0B52AFC6D32E40326497A@misout7msgusr7c.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Proposal for authentication & authorization for multicast streams
Thread-Index: AcsLy9qw3M+Rd6L7TEuIg2YrkVuX0yrguZFQ
References: <3580159D7E3D824780C0B52AFC6D32E40326497A@misout7msgusr7c.ugd.att.com>
From: "ALTOM, MARK W (ATTSI)" <ma697r@att.com>
To: <mboned@ietf.org>
Subject: [MBONED] Proposal for authentication & authorization for multicast streams
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 20:34:18 -0000

On April 19, 2010 AT&T submitted an IETF Patent Disclosure=20
and Licensing Declaration with respect to this contribution=20
concerning the authentication and authorization of=20
end-users to receive multicast streams.

The following is a proposal for authentication and=20
authorization of end-users to receive multicast streams.
Mark Altom
AT&T Labs

=3D authentication & authorization proposal begins here =3D

Additional functionality for secure content delivery is=20
required for multicast over unicast because with unicast=20
content delivery, there is a one-to-one relationship=20
between the requesting end-point and a unicast stream=20
from a unicast media server. With multicast content=20
delivery, there is a one-to-many relationship between=20
the multicast stream and the requesting end-point=20
receivers.

The following outlines AT&T's solution to enforce
authentication and authorization of end-users for secure
delivery of multicast content where the content provider
and the network provider are separate entities.

The feature implementation requires an additional
service-related function at the network resource=20
(multicast enabled router or AMT Relay) that enables=20
the "join" for a multicast stream.  The additional=20
function includes the delivery by service intelligence=20
from the network provider of a secure (signed and=20
encrypted) secondary token to the end-user.  This=20
token is authenticated by the network resource that=20
implements the join by using a shared key that only=20
the network resource and multicast intelligence=20
infrastructure have available.

CP =3D Third-party Content Provider
EU =3D End User
SI =3D Service Intelligence from the network provider
NR =3D Network Resource (multicast enabled router, AMT Relay)

For the discussion presented here, communication between
the end-user and the network resource could take place
over IGMP v3.  The message types are:
MembRpt:  IGMP v3 Membership Report
MembQry:  Membership Query

When showing IGMP messages, a semicolon is used to set=20
off the new, nonstandard parameters.  For example, in=20
a Membership Report message, these parameters could be=20
carried in the Auxiliary Data Field associated with=20
each multicast group.  In a Membership Query message,=20
they could be carried as additional data outside of=20
the IGMP message itself. (Changes might be required=20
to RFC3376 and to the AMT Internet Draft to support=20
these enhancements.)  =20

For IPv6, similar MLD messages would be used.

The End User communicates with the Content Provider and
the Service Intelligence using Transport Layer Security
(TLS).  TLS-protected messages are prefixed with TLS_,
but the notation does not distinguish between different=20
TLS sessions.

The Content Provider (CP) has a secret/public key pair
for signing and digital-signature verification, denoted
SK_CP and VK_CP, respectively.  VK_CP is available to and
its authenticity verified by the other entities.

K_Enc and K_Auth are symmetric authorization keys=20
shared by service intelligence and the network resource.

For efficiency reasons, the Service Intelligence (SI)
communicates with the Network Resource (NR) through the=20
end user (EU).  This is done in a confidential and=20
authenticated way using keys that they share.

The following is a step-by-step description of the
proposed protocol.

SK_CP=3DSecret Key           Symmetric keys shared by SI & NR
VK_CP=3DPublic Key           K_Enc and K_Auth

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D                        =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
|         |                   (4a) |          |
|   CP    |                   (4b) |    SI    |
|         |                   (4c) |          |
|         |                   (4d) |          |
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D                   (4e) =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    ^ |(2)                           ^  |   |
    | |               (3)            |  |   |
(1) | | ------------------------------  |   |(9)
    | | |                               |   |
    | | |                               |   |
    | | |                   (4f)        |   |
    | | |      --------------------------   |
    | | |      |                            |
    | V |      |                            V
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D    |                   =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
|         |<----                   |          |
|         |            (5)         |          |
|         |----------------------->|          |
|   EU    |                 (6b)   |    NR    |
|         |<-----------------------|          |
|         |----------------------->|          |
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D          (7b)          =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    (7a)                             (6a)  (8)

(1) The end-user navigates to the content provider's Web
site and requests multicast content (e.g., live video).
The content provider's Web server determines whether or
not secure content delivery is required.  If secure=20
content delivery is required, the Web server sends a=20
request to the end-user for credentials (e.g., requests
a user ID and password or requests a credit card number).
The end-user supplies the requested credentials.  Combining
these possibly multiple steps, the end user sends to the
content provider a program request with an=20
identification (ID) of the end user and the=20
identification of the desired content
(ProgID):
EU=3D>CP
TLS_ProgReq(ID|ProgID)

(2) If the end-user's credentials are authenticated, the
content provider composes a secure token and
appends it to the streaming URL.  The content provider=20
may use any algorithm and tracking mechanism for these
secure tokens (e.g., unique for every request, time
based, etc.).  The content provider returns to the end-user
a token signed by the content provider's private key,
SK_CP, where TransID is a transaction ID:
CP=3D>EU
TLS_ProgAuth(TransID|ID|ProgID|Sig_{SK_CC}(TransID|ID|ProgID))

(3) The end-user requests multicast content=20
from the network provider's content delivery service
intelligence.  The request includes the signed token.
EU=3D>SI
TLS_GroupReq(<contents of TLS_ProgAuth message>)


(4) Content delivery service intelligence authenticates
the end user with the following steps.

(4a) The secure token is authenticated either at the=20
service intelligence or by forwarding the credentials
to the content provider's authentication server.
Note, that up to this point, secure content delivery=20
would be exactly the same for unicast and for multicast
content delivery.

(4b) Service intelligence maps the content request to a=20
Multicast source and group (for Source Specific Multicast),
here denoted as GroupID.

(4c) Service intelligence generates an authorization key,
K_MSK.

(4d) Service intelligence generates the end-user's=20
credentials for the multicast stream:
Cred =3D ID|GroupID|K_MSK|<period of validity>

(4e) Service intelligence encrypts and authenticates the
credentials (Cred) using the symmetric keys, K_Enc
and K_Auth:
Fwd_Cred =3D E_{K_Enc}(Cred)|MAC_{K_Auth}(E_{K_Enc}(Cred))

(4f) Service intelligence sends the credentials and=20
forwardable representation to the end-user:
SI=3D>EU
TLS_GroupAuth(Cred|Fwd_Cred)

(5) The end-user sends a join request to the network
resource:
EU=3D>NR
MembRpt(GroupID; ID | Fwd_Cred | N2)
where N2 is a nonce.

(6) The network resource verifies the authenticity and
extracts (decrypts) the credentials from Fwd_Cred.

(6a) If the credentials are valid, the network resource=20
caches the credentials.

(6b) The network resource sends to the end-user:
NR=3D>EU
MembQry(GroupID; ID | N3 | Auth1)
where, Auth1 =3D MAC_{K_MSK}(N2 | N3 | ID | GroupID)

(7) The end-user verifies AUTH1 using K_MSK.

(7a) The end-user uses its copy of the credentials to=20
compute:
AUTH2 =3D MAC_{K_MSK}(N3 | N2 | ID | GroupID)

(7b) The end-user sends a response to the network
resource's challenge:
EU=3D>NR
MembRpt(GroupID; ID | AUTH2)

(8) The network resource uses its copy of the
credentials to verify AUTH2 and adds the=20
end-user to the multicast group.

(9) Service intelligence periodically updates the
network resources with the shared keys:
SI=3D>NR
MPLS_KeyUpdate(K_Enc, K_Auth)


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DAAA proposal ends here =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

From pusateri@bangj.com  Tue Jan 18 13:09:25 2011
Return-Path: <pusateri@bangj.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DA273A6F58 for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 13:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Fgbe0UqbuL2 for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 13:09:24 -0800 (PST)
Received: from jj.bangj.com (jj.bangj.com [198.86.87.199]) by core3.amsl.com (Postfix) with ESMTP id 4ADE53A6F57 for <mboned@ietf.org>; Tue, 18 Jan 2011 13:09:23 -0800 (PST)
Received: from [172.16.10.11] (cpe-076-182-035-136.nc.res.rr.com [76.182.35.136]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by jj.bangj.com (Postfix) with ESMTPSA id 0984DDDD for <mboned@ietf.org>; Tue, 18 Jan 2011 16:11:59 -0500 (EST)
From: Tom Pusateri <pusateri@bangj.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Jan 2011 16:12:01 -0500
Message-Id: <15D68C76-95AE-401B-9136-EE1B30FA1546@bangj.com>
To: mboned@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [MBONED] AMT draft new editor?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 21:09:25 -0000

I'm finally coming to the realization that I don't have time to work on =
the AMT draft anymore and wondered if there was someone else who is =
willing to take it over. Ideally, it would be someone that has skin in =
the game (they are using it a deployment scenario or writing the code =
for it).

I can pass on the XML source of the last draft.

Thanks,
Tom=

From gjshep@gmail.com  Tue Jan 18 13:20:57 2011
Return-Path: <gjshep@gmail.com>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52ABC3A6E57 for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 13:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.378
X-Spam-Level: 
X-Spam-Status: No, score=-103.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWKu9qx68+8D for <mboned@core3.amsl.com>; Tue, 18 Jan 2011 13:20:54 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id AE4ED3A6BFC for <mboned@ietf.org>; Tue, 18 Jan 2011 13:20:53 -0800 (PST)
Received: by fxm9 with SMTP id 9so96683fxm.31 for <mboned@ietf.org>; Tue, 18 Jan 2011 13:23:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=f81wxaFYLB0CF4CSSTDWFuzb4SJ1QrJoHUD7z3pYY2E=; b=UScDz+P6/Y3+9eR3MEKR5NEp1U63L6Gc3vAhL+qcP4CNW/o3+gthT5Qe/vC0fT7Lso yADkwV7rZiU6vAhbv8Lr9czNI9cVlWsgjPeKXaMd0S8mCDjyykPflLUuEXSiHepvXvPD NcsiqaYlSUCS1Rd+qGlpNYpATU5ZgFobZx3Yg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=iQpKhMYw5fh4xv3QWC5dwkKMvspFCipj5X5X9rIDvXH+7zyhFhGvQ00KI7c2qfREez 7T1CeQbPtCQPPcQatAdrHjt/VFByvUAPtEerGwaJZxvL6Jl+7DRHfrB4+Ioox7uEdG8z 1ORB7U14PLQoJW/ujCyjzzummrhRwBlSFKfFw=
MIME-Version: 1.0
Received: by 10.223.83.16 with SMTP id d16mr1557921fal.148.1295385809203; Tue, 18 Jan 2011 13:23:29 -0800 (PST)
Received: by 10.223.71.13 with HTTP; Tue, 18 Jan 2011 13:23:29 -0800 (PST)
In-Reply-To: <15D68C76-95AE-401B-9136-EE1B30FA1546@bangj.com>
References: <15D68C76-95AE-401B-9136-EE1B30FA1546@bangj.com>
Date: Tue, 18 Jan 2011 13:23:29 -0800
Message-ID: <AANLkTim4bc7gru5rv0Oc0FNS8-8+eNv+5U3T_JV6iPWP@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: Tom Pusateri <pusateri@bangj.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: mboned@ietf.org
Subject: Re: [MBONED] AMT draft new editor?
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gjshep@gmail.com
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 21:20:57 -0000

Thanks for all your work Tom!

As co-chairs, Lenny and I will take the token from you and look for a
new editor.

Cheers,
Greg

On Tue, Jan 18, 2011 at 1:12 PM, Tom Pusateri <pusateri@bangj.com> wrote:
> I'm finally coming to the realization that I don't have time to work on t=
he AMT draft anymore and wondered if there was someone else who is willing =
to take it over. Ideally, it would be someone that has skin in the game (th=
ey are using it a deployment scenario or writing the code for it).
>
> I can pass on the XML source of the last draft.
>
> Thanks,
> Tom
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>

From Internet-Drafts@ietf.org  Thu Jan 20 14:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: mboned@core3.amsl.com
Delivered-To: mboned@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE6E83A6855; Thu, 20 Jan 2011 14:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeISgr19TWwK; Thu, 20 Jan 2011 14:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EDB23A6841; Thu, 20 Jan 2011 14:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110120221502.31827.55762.idtracker@localhost>
Date: Thu, 20 Jan 2011 14:15:02 -0800
Cc: mboned@ietf.org
Subject: [MBONED] I-D ACTION:draft-ietf-mboned-ip-multicast-pm-requirement-00.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jan 2011 22:15:02 -0000

--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		: Requirements for IP multicast performance monitoring
	Author(s)	: A. Bonda, G. Picciano, M. Chen, L. Zheng
	Filename	: draft-ietf-mboned-ip-multicast-pm-requirement-00.txt
	Pages		: 14
	Date		: 2011-1-20
	
This document describes the requirement for an IP multicast 
   performance monitoring system for service provider IP multicast 
   networks. This system enables efficient performance monitoring in 
   Service Providers' production networks and provides diagnostic 
   information in case of performance degradation or failure. 


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-ip-multicast-pm-requirement-00.txt

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

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: Message/External-body;
	name="draft-ietf-mboned-ip-multicast-pm-requirement-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--
