
From dromasca@avaya.com  Wed Jun  2 07:56:44 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3639D3A6826; Wed,  2 Jun 2010 07:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.817
X-Spam-Level: 
X-Spam-Status: No, score=-0.817 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_20=-0.74]
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 yqMbE6c4dHnk; Wed,  2 Jun 2010 07:56:43 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id F13383A6986; Wed,  2 Jun 2010 07:56:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200"; d="scan'208";a="18738694"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 02 Jun 2010 10:56:30 -0400
X-IronPort-AV: E=Sophos;i="4.53,347,1272859200"; d="scan'208";a="480260585"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Jun 2010 10:56:28 -0400
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: Wed, 2 Jun 2010 16:56:17 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: FEDAUTH BOF request
Thread-Index: AcsCY8D3YG4qrCIAT927dkDMQ1m8hw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>, "radext mailing list" <radiusext@ops.ietf.org>, <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2010 14:56:44 -0000

Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.=20

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

From tena@huawei.com  Wed Jun  2 21:03:06 2010
Return-Path: <tena@huawei.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95A9F3A672E; Wed,  2 Jun 2010 21:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.039
X-Spam-Level: 
X-Spam-Status: No, score=-99.039 tagged_above=-999 required=5 tests=[AWL=1.145, BAYES_40=-0.185, STOX_REPLY_TYPE=0.001, 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 nqWc5erV6bS1; Wed,  2 Jun 2010 21:03:02 -0700 (PDT)
Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id EC6D13A6835; Wed,  2 Jun 2010 21:03:00 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00F4Y78MOG@szxga02-in.huawei.com>; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F006CC78MOC@szxga02-in.huawei.com>; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00HS878LTS@szxml04-in.huawei.com>; Thu, 03 Jun 2010 12:02:46 +0800 (CST)
Date: Thu, 03 Jun 2010 12:02:46 +0800
From: Tina TSOU <tena@huawei.com>
To: aaa-doctors@ietf.org, radext mailing list <radiusext@ops.ietf.org>, dime@ietf.org, "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Message-id: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>
Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 04:03:06 -0000

Comments are below.
1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
solutions who provide Identity Management services
2. From protocol side, I think it may be more interesting for RADIUS as I 
doubt the suitability of Diameter for this.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
<aaa-doctors@ietf.org>
Sent: Wednesday, June 02, 2010 10:56 PM
Subject: FEDAUTH BOF request


Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>



From bernard_aboba@hotmail.com  Wed Jun  2 22:03:35 2010
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2E773A693B; Wed,  2 Jun 2010 22:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 MqeRuJmcNqea; Wed,  2 Jun 2010 22:03:34 -0700 (PDT)
Received: from blu0-omc2-s13.blu0.hotmail.com (blu0-omc2-s13.blu0.hotmail.com [65.55.111.88]) by core3.amsl.com (Postfix) with ESMTP id 423B63A6832; Wed,  2 Jun 2010 22:03:34 -0700 (PDT)
Received: from BLU137-W35 ([65.55.111.72]) by blu0-omc2-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Jun 2010 22:03:20 -0700
Message-ID: <BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_"
X-Originating-IP: [64.134.138.42]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Date: Wed, 2 Jun 2010 22:03:16 -0700
Importance: Normal
In-Reply-To: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2010 05:03:20.0939 (UTC) FILETIME=[163CA3B0:01CB02DA]
Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 05:03:36 -0000

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Tina said:=20

> Comments are below.
> 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of=
=20
> solutions who provide Identity Management services
> 2. From protocol side=2C I think it may be more interesting for RADIUS as=
 I  doubt the suitability of Diameter for this.

Not sure why RADIUS would be more suitable than Diameter for carrying large=
 payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not =
transport-specific -- that is=2C transporting the RADIUS payload over TCP d=
oes not solve the problem.=20

=20
> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Tina said: <br><br>&gt=3B Comments are below.<br>&gt=3B 1. This might be of=
 interest to ngHLR (Unified Subscriber Center) kind of <br>&gt=3B solutions=
 who provide Identity Management services<br>&gt=3B 2. From protocol side=
=2C I think it may be more interesting for RADIUS as I&nbsp=3B doubt the su=
itability of Diameter for this.<br><br>Not sure why RADIUS would be more su=
itable than Diameter for carrying large payloads such as SAML assertions.&n=
bsp=3B The 4096 octet RADIUS PDU limit is not transport-specific -- that is=
=2C transporting the RADIUS payload over TCP does not solve the problem. <b=
r><br>&nbsp=3B<br>&gt=3B ----- Original Message ----- <br>&gt=3B From: "Rom=
ascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com&gt=3B<br>&gt=3B To: &lt=3Bdim=
e@ietf.org&gt=3B=3B "radext mailing list" &lt=3Bradiusext@ops.ietf.org&gt=
=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=3B<br>&gt=3B Sent: Wednesda=
y=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject: FEDAUTH BOF request<br>&gt=
=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS experts should pay attention =
to the request to hold<br>&gt=3B a Federated Authentication (FEDAUTH) BOF w=
hich will be discussed this<br>&gt=3B morning by the IAB and the IESG.<br>&=
gt=3B <br>&gt=3B The Draft Charter is available at<br>&gt=3B http://www.pro=
ject-moonshot.org/bof/charter/=2C and more information about<br>&gt=3B this=
 BOF or other BOF requests can be examined  at<br>&gt=3B http://trac.tools.=
ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>&gt=3B <br>&gt=3B --<br>&gt=
=3B to unsubscribe send a message to radiusext-request@ops.ietf.org with<br=
>&gt=3B the word 'unsubscribe' in a single line as the message text body.<b=
r>&gt=3B archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br>&gt=3B <br=
>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to=
 radiusext-request@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a =
single line as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.c=
om/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_d7e3c6e9-fe8b-4f07-b2af-c6d5841ccbd2_--

From bernard_aboba@hotmail.com  Wed Jun  2 22:26:54 2010
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2314B3A67C1; Wed,  2 Jun 2010 22:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.036
X-Spam-Level: 
X-Spam-Status: No, score=-0.036 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 r+8+KNbr0T77; Wed,  2 Jun 2010 22:26:46 -0700 (PDT)
Received: from blu0-omc2-s35.blu0.hotmail.com (blu0-omc2-s35.blu0.hotmail.com [65.55.111.110]) by core3.amsl.com (Postfix) with ESMTP id EC7863A6926; Wed,  2 Jun 2010 22:26:39 -0700 (PDT)
Received: from BLU137-W24 ([65.55.111.72]) by blu0-omc2-s35.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Jun 2010 22:26:26 -0700
Message-ID: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
Content-Type: multipart/alternative; boundary="_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_"
X-Originating-IP: [64.134.138.42]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>, <dime@ietf.org>, "dromasca@avaya.com" <dromasca@avaya.com>
Date: Wed, 2 Jun 2010 22:26:26 -0700
Importance: Normal
In-Reply-To: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2010 05:26:26.0401 (UTC) FILETIME=[50095D10:01CB02DD]
Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 05:26:54 -0000

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Let me provide a bit of  context about what I think the problem is here.=20

As noted by Sam in a previous conversation=2C the basic use case is "cloud =
services"=2C where an education institution or enterprise is making use of =
hosted services.  In these situations=2C the institution may not just want =
the service provider to host an application=2C but may want to keep their c=
redentials local=2C rather than hosting this in the cloud as well.=20

In the original Moonshot investigation=2C Kerberos was considered as a pote=
ntial solution.  However=2C while Kerberos is well understood from a securi=
ty point of view=2C and could relatively easily be modified to support EAP-=
based pre-auth (numerous proposals for this have been advanced and in some =
cases implemented)  Kerberos federation has not been widely deployed.=20

One of the basic problems with putting a KDC on the Internet is that there =
is no easy way to protect it=2C since both clients and other KDCs may need =
to send packets to and from the KDC.  For this reason if there are roaming =
clients there is no easy way to filter traffic to/from the KDC.  In additio=
n=2C the Kerberos protocol is vulnerable to passive attacks in the absence =
of extensions such as PKINIT or Kerberos Hardening.=20

In contrast=2C the AAA roaming model has been widely deployed=2C in part be=
cause it is much easier to protect a AAA server.  AAA servers only talk to =
AAA clients=2C not to users directly.  This means that it is typically poss=
ible to filter traffic to the AAA server so that only packets originating f=
rom legitimate AAA clients can be sent to/from the AAA server.  =20

In addition to these basic security issues=2C the AAA delegation model is m=
uch simpler than Kerberos.  Obtaining a Kerberos TGT for a local realm invo=
lves first obtaining a TGT from a "home" realm and then requesting a TGT fo=
r the local realm.  This involves multiple exchanges=2C and as noted earlie=
r requires both the local KDC and the home KDC to be available over the Int=
ernet.  In contrast=2C a AAA client implicitly delegates authority to the A=
AA server for the Accept/Reject decision=2C so that explicit trust relation=
ships don't need to be configured.  As long as the AAA client can reach the=
 AAA server via a chain of proxies the trust relationship can succeed.=20

Given these basic characteristics of Kerberos and AAA delegation=2C the Moo=
nshot team has decided that a AAA-based approach to delegation is more like=
ly to be widely deployed than a Kerberos-based one.  My take on this is tha=
t this assessment is probably realistic.=20

Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.  As we saw with Digest authentication (RFC 5090)=2C it is possibl=
e to extend AAA to support application-layer authentication without use of =
EAP.  For example=2C using AAA to carry GSS-API payloads would not require =
much more than defining a GSS-Message attribute.  EAP has no unique propert=
ies that make it more suitable for use with AAA.  In fact=2C I would argue =
that the fit between EAP and AAA has always been tenuous at best -- witness=
 the issues encountered in federated EAP authentication that RADSEC has bee=
n needed to address. =20

In particular=2C the problems of EAP auth (e.g. multiple round-trips=2C gen=
eral fragility in federated uses) become highly toxic when applied to Realt=
ime applications such as XMPP and SIP.  As we have learned=2C Digest auth (=
RFC 5090) has not been widely deployed=2C in part because of concern about =
the additional latency added by a AAA exchange.  For users of real-time app=
lications=2C additional latency is a basic=2C non-negotiable goal.  If the =
relatively modest number of exchanges implied by RFC 5090 were intolerable =
in realtime applications=2C  how can we expect EAP exchanges (which can inv=
olve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The a=
nswer unfortunately=2C is that there is no chance at all. =20

So in summary=2C I believe that some aspects of the problem statement make =
sense=2C but that a solution has been chosen prematurely.  The right way to=
 move forward in a situation like this is to begin with a problem statement=
=2C which should include carefully validating the uses cases. =20
 =20

> ----- Original Message -----=20
> From: "Romascanu=2C Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>=3B "radext mailing list" <radiusext@ops.ietf.org>=3B=
=20
> <aaa-doctors@ietf.org>
> Sent: Wednesday=2C June 02=2C 2010 10:56 PM
> Subject: FEDAUTH BOF request
>=20
>=20
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
>=20
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/=2C and more information abou=
t
> this BOF or other BOF requests can be examined  at
> http://trac.tools.ietf.org/bof/trac/
>=20
> Dan
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
>=20
>=20
>=20
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
 		 	   		  =

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
--></style>
</head>
<body class=3D'hmmessage'>
Let me provide a bit of&nbsp=3B context about what I think the problem is h=
ere. <br><br>As noted by Sam in a previous conversation=2C the basic use ca=
se is "cloud services"=2C where an education institution or enterprise is m=
aking use of hosted services.&nbsp=3B In these situations=2C the institutio=
n may not just want the service provider to host an application=2C but may =
want to keep their credentials local=2C rather than hosting this in the clo=
ud as well. <br><br>In the original Moonshot investigation=2C Kerberos was =
considered as a potential solution.&nbsp=3B However=2C while Kerberos is we=
ll understood from a security point of view=2C and could relatively easily =
be modified to support EAP-based pre-auth (numerous proposals for this have=
 been advanced and in some cases implemented)&nbsp=3B Kerberos federation h=
as not been widely deployed. <br><br>One of the basic problems with putting=
 a KDC on the Internet is that there is no easy way to protect it=2C since =
both clients and other KDCs may need to send packets to and from the KDC.&n=
bsp=3B For this reason if there are roaming clients there is no easy way to=
 filter traffic to/from the KDC.&nbsp=3B In addition=2C the Kerberos protoc=
ol is vulnerable to passive attacks in the absence of extensions such as PK=
INIT or Kerberos Hardening. <br><br>In contrast=2C the AAA roaming model ha=
s been widely deployed=2C in part because it is much easier to protect a AA=
A server.&nbsp=3B AAA servers only talk to AAA clients=2C not to users dire=
ctly.&nbsp=3B This means that it is typically possible to filter traffic to=
 the AAA server so that only packets originating from legitimate AAA client=
s can be sent to/from the AAA server.&nbsp=3B&nbsp=3B <br><br>In addition t=
o these basic security issues=2C the AAA delegation model is much simpler t=
han Kerberos.&nbsp=3B Obtaining a Kerberos TGT for a local realm involves f=
irst obtaining a TGT from a "home" realm and then requesting a TGT for the =
local realm.&nbsp=3B This involves multiple exchanges=2C and as noted earli=
er requires both the local KDC and the home KDC to be available over the In=
ternet.&nbsp=3B In contrast=2C a AAA client implicitly delegates authority =
to the AAA server for the Accept/Reject decision=2C so that explicit trust =
relationships don't need to be configured.&nbsp=3B As long as the AAA clien=
t can reach the AAA server via a chain of proxies the trust relationship ca=
n succeed. <br><br>Given these basic characteristics of Kerberos and AAA de=
legation=2C the Moonshot team has decided that a AAA-based approach to dele=
gation is more likely to be widely deployed than a Kerberos-based one.&nbsp=
=3B My take on this is that this assessment is probably realistic. <br><br>=
Where I get lost is making the leap between the AAA delegation model and us=
e of EAP.&nbsp=3B As we saw with Digest authentication (RFC 5090)=2C it is =
possible to extend AAA to support application-layer authentication without =
use of EAP.&nbsp=3B For example=2C using AAA to carry GSS-API payloads woul=
d not require much more than defining a GSS-Message attribute.&nbsp=3B EAP =
has no unique properties that make it more suitable for use with AAA.&nbsp=
=3B In fact=2C I would argue that the fit between EAP and AAA has always be=
en tenuous at best -- witness the issues encountered in federated EAP authe=
ntication that RADSEC has been needed to address.&nbsp=3B <br><br>In partic=
ular=2C the problems of EAP auth (e.g. multiple round-trips=2C general frag=
ility in federated uses) become highly toxic when applied to Realtime appli=
cations such as XMPP and SIP.&nbsp=3B As we have learned=2C Digest auth (RF=
C 5090) has not been widely deployed=2C in part because of concern about th=
e additional latency added by a AAA exchange.&nbsp=3B For users of real-tim=
e applications=2C additional latency is a basic=2C non-negotiable goal.&nbs=
p=3B If the relatively modest number of exchanges implied by RFC 5090 were =
intolerable in realtime applications=2C&nbsp=3B how can we expect EAP excha=
nges (which can involve 4-5 times the number of roundtrips of RFC 5090) to =
be deployed?&nbsp=3B The answer unfortunately=2C is that there is no chance=
 at all.&nbsp=3B <br><br>So in summary=2C I believe that some aspects of th=
e problem statement make sense=2C but that a solution has been chosen prema=
turely.&nbsp=3B The right way to move forward in a situation like this is t=
o begin with a problem statement=2C which should include carefully validati=
ng the uses cases.&nbsp=3B <br>&nbsp=3B <br><br>&gt=3B ----- Original Messa=
ge ----- <br>&gt=3B From: "Romascanu=2C Dan (Dan)" &lt=3Bdromasca@avaya.com=
&gt=3B<br>&gt=3B To: &lt=3Bdime@ietf.org&gt=3B=3B "radext mailing list" &lt=
=3Bradiusext@ops.ietf.org&gt=3B=3B <br>&gt=3B &lt=3Baaa-doctors@ietf.org&gt=
=3B<br>&gt=3B Sent: Wednesday=2C June 02=2C 2010 10:56 PM<br>&gt=3B Subject=
: FEDAUTH BOF request<br>&gt=3B <br>&gt=3B <br>&gt=3B Diameter and RADIUS e=
xperts should pay attention to the request to hold<br>&gt=3B a Federated Au=
thentication (FEDAUTH) BOF which will be discussed this<br>&gt=3B morning b=
y the IAB and the IESG.<br>&gt=3B <br>&gt=3B The Draft Charter is available=
 at<br>&gt=3B http://www.project-moonshot.org/bof/charter/=2C and more info=
rmation about<br>&gt=3B this BOF or other BOF requests can be examined  at<=
br>&gt=3B http://trac.tools.ietf.org/bof/trac/<br>&gt=3B <br>&gt=3B Dan<br>=
&gt=3B <br>&gt=3B --<br>&gt=3B to unsubscribe send a message to radiusext-r=
equest@ops.ietf.org with<br>&gt=3B the word 'unsubscribe' in a single line =
as the message text body.<br>&gt=3B archive: &lt=3Bhttp://psg.com/lists/rad=
iusext/&gt=3B<br>&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B --<br>&gt=3B to un=
subscribe send a message to radiusext-request@ops.ietf.org with<br>&gt=3B t=
he word 'unsubscribe' in a single line as the message text body.<br>&gt=3B =
archive: &lt=3Bhttp://psg.com/lists/radiusext/&gt=3B<br> 		 	   		  </body>
</html>=

--_b105dacf-0e73-4ddb-9eaa-2a8bfde017a9_--

From hannes.tschofenig@nsn.com  Thu Jun  3 00:18:13 2010
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FA683A689B; Thu,  3 Jun 2010 00:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.269
X-Spam-Level: 
X-Spam-Status: No, score=-1.269 tagged_above=-999 required=5 tests=[AWL=1.330,  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 KujAOA5E7Tvk; Thu,  3 Jun 2010 00:18:12 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by core3.amsl.com (Postfix) with ESMTP id 389193A6850; Thu,  3 Jun 2010 00:18:12 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o537HoDM030181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 3 Jun 2010 09:17:51 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o537HoWH012859; Thu, 3 Jun 2010 09:17:50 +0200
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Jun 2010 09:17:50 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Jun 2010 10:18:00 +0300
Message-ID: <3D3C75174CB95F42AD6BCC56E5555B4502A8093D@FIESEXC015.nsn-intra.net>
In-Reply-To: <F30237DE0DEB964C89C4D3A3473B46E506EC37DB@S4DE9JSAAII.ost.t-com.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Dime] FEDAUTH BOF request
Thread-Index: AcsC0aidQ02izmSBSNyywMJWJZ76pQAGbcXgAABgRDA=
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com><F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <F30237DE0DEB964C89C4D3A3473B46E506EC37DB@S4DE9JSAAII.ost.t-com.de>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: <Wolfgang.Steigerwald@telekom.de>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
X-OriginalArrivalTime: 03 Jun 2010 07:17:50.0524 (UTC) FILETIME=[E01597C0:01CB02EC]
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 07:18:13 -0000

Looking forward to hear that answer as well :-)=20

>-----Original Message-----
>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On=20
>Behalf Of ext Wolfgang.Steigerwald@telekom.de
>Sent: 03 June, 2010 10:16
>To: tena@huawei.com; aaa-doctors@ietf.org;=20
>radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
>Subject: Re: [Dime] FEDAUTH BOF request
>
>Hello Tina,
>
>what assumption let you think RADIUS is more suitable then=20
>DIAMETER? DIAMETER is much more developed, is a peer to peer=20
>protocol, designed to transport also structured data, not as=20
>limited on payload and therefore much better suitable for the=20
>purpose of IdM.
>
>Best Regards
>
> Wolfgang
>
>-----Urspr=FCngliche Nachricht-----
>Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im=20
>Auftrag von Tina TSOU
>Gesendet: Donnerstag, 3. Juni 2010 06:03
>An: aaa-doctors@ietf.org; radext mailing list; dime@ietf.org;=20
>Romascanu, Dan (Dan)
>Betreff: Re: [Dime] FEDAUTH BOF request
>
>Comments are below.
>1. This might be of interest to ngHLR (Unified Subscriber=20
>Center) kind of solutions who provide Identity Management=20
>services 2. From protocol side, I think it may be more=20
>interesting for RADIUS as I doubt the suitability of Diameter for this.
>
>B. R.
>Tina
>http://tinatsou.weebly.com/contact.html
>
>----- Original Message -----
>From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>To: <dime@ietf.org>; "radext mailing list"=20
><radiusext@ops.ietf.org>; <aaa-doctors@ietf.org>
>Sent: Wednesday, June 02, 2010 10:56 PM
>Subject: FEDAUTH BOF request
>
>
>Diameter and RADIUS experts should pay attention to the=20
>request to hold a Federated Authentication (FEDAUTH) BOF which=20
>will be discussed this morning by the IAB and the IESG.
>
>The Draft Charter is available at
>http://www.project-moonshot.org/bof/charter/, and more=20
>information about this BOF or other BOF requests can be=20
>examined  at http://trac.tools.ietf.org/bof/trac/
>
>Dan
>
>--
>to unsubscribe send a message to=20
>radiusext-request@ops.ietf.org with the word 'unsubscribe' in=20
>a single line as the message text body.
>archive: <http://psg.com/lists/radiusext/>
>
>
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>

From Wolfgang.Steigerwald@telekom.de  Thu Jun  3 00:16:54 2010
Return-Path: <Wolfgang.Steigerwald@telekom.de>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00DCE3A6867; Thu,  3 Jun 2010 00:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.39
X-Spam-Level: 
X-Spam-Status: No, score=-1.39 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 tVYZbB-zivXe; Thu,  3 Jun 2010 00:16:52 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 121773A6850; Thu,  3 Jun 2010 00:16:51 -0700 (PDT)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail51.telekom.de with ESMTP; 03 Jun 2010 09:16:33 +0200
Received: from S4DE9JSAAII.ost.t-com.de ([10.125.177.194]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Jun 2010 09:16:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 3 Jun 2010 09:16:28 +0200
Message-ID: <F30237DE0DEB964C89C4D3A3473B46E506EC37DB@S4DE9JSAAII.ost.t-com.de>
In-Reply-To: <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Dime] FEDAUTH BOF request
Thread-Index: AcsC0aidQ02izmSBSNyywMJWJZ76pQAGbcXg
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com> <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>
From: <Wolfgang.Steigerwald@telekom.de>
To: <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
X-OriginalArrivalTime: 03 Jun 2010 07:16:33.0338 (UTC) FILETIME=[B213F1A0:01CB02EC]
X-Mailman-Approved-At: Thu, 03 Jun 2010 00:46:31 -0700
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 07:16:54 -0000

Hello Tina,

what assumption let you think RADIUS is more suitable then DIAMETER? =
DIAMETER is much more developed, is a peer to peer protocol, designed to =
transport also structured data, not as limited on payload and therefore =
much better suitable for the purpose of IdM.

Best Regards

 Wolfgang

-----Urspr=FCngliche Nachricht-----
Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im Auftrag von =
Tina TSOU
Gesendet: Donnerstag, 3. Juni 2010 06:03
An: aaa-doctors@ietf.org; radext mailing list; dime@ietf.org; Romascanu, =
Dan (Dan)
Betreff: Re: [Dime] FEDAUTH BOF request

Comments are below.
1. This might be of interest to ngHLR (Unified Subscriber Center) kind =
of=20
solutions who provide Identity Management services
2. From protocol side, I think it may be more interesting for RADIUS as =
I=20
doubt the suitability of Diameter for this.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message -----=20
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>;=20
<aaa-doctors@ietf.org>
Sent: Wednesday, June 02, 2010 10:56 PM
Subject: FEDAUTH BOF request


Diameter and RADIUS experts should pay attention to the request to hold
a Federated Authentication (FEDAUTH) BOF which will be discussed this
morning by the IAB and the IESG.

The Draft Charter is available at
http://www.project-moonshot.org/bof/charter/, and more information about
this BOF or other BOF requests can be examined  at
http://trac.tools.ietf.org/bof/trac/

Dan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>


_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

From tena@huawei.com  Thu Jun  3 06:54:57 2010
Return-Path: <tena@huawei.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C6273A67D4; Thu,  3 Jun 2010 06:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.009
X-Spam-Level: 
X-Spam-Status: No, score=-100.009 tagged_above=-999 required=5 tests=[AWL=0.485, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.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 XT2bo6gFiRCX; Thu,  3 Jun 2010 06:54:56 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id B483E3A67AD; Thu,  3 Jun 2010 06:54:55 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F001D1YMWQD@szxga05-in.huawei.com>; Thu, 03 Jun 2010 21:54:32 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F005QIYMV0K@szxga05-in.huawei.com>; Thu, 03 Jun 2010 21:54:31 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00F79YMVTB@szxml04-in.huawei.com>; Thu, 03 Jun 2010 21:54:31 +0800 (CST)
Date: Thu, 03 Jun 2010 21:54:28 +0800
From: Tina TSOU <tena@huawei.com>
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Bernard Aboba <bernard_aboba@hotmail.com>
Message-id: <A142425E33AB431C8F6FBF8C10E4594B@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: multipart/alternative; boundary="Boundary_(ID_6hv+ML6mj+wcKfSI/Z8TQg)"
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com> <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl>
Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 13:54:57 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_6hv+ML6mj+wcKfSI/Z8TQg)
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Hi Bernard,
Comments are in line.

B. R.
Tina
http://tinatsou.weebly.com/contact.html
  ----- Original Message ----- 
  From: Bernard Aboba 
  To: tena@huawei.com ; aaa-doctors@ietf.org ; radiusext@ops.ietf.org ; dime@ietf.org ; dromasca@avaya.com 
  Sent: Thursday, June 03, 2010 1:03 PM
  Subject: RE: FEDAUTH BOF request


  Tina said: 

  > Comments are below.
  > 1. This might be of interest to ngHLR (Unified Subscriber Center) kind of 
  > solutions who provide Identity Management services
  > 2. From protocol side, I think it may be more interesting for RADIUS as I  doubt the suitability of Diameter for this.

  Not sure why RADIUS would be more suitable than Diameter for carrying large payloads such as SAML assertions.  The 4096 octet RADIUS PDU limit is not transport-specific -- that is, transporting the RADIUS payload over TCP does not solve the problem. 

  [Tina: You are also right from the aspect you raised.
  Diameter roaming model is well established (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I fail to see what would be the benefits of using EAP or SAML with Diameter which the current roaming model does not already have.
  Everything has pros and cons, as you said in another email, let's begin with a problem statement, and then protocols.]


   
  > ----- Original Message ----- 
  > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
  > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
  > <aaa-doctors@ietf.org>
  > Sent: Wednesday, June 02, 2010 10:56 PM
  > Subject: FEDAUTH BOF request
  > 
  > 
  > Diameter and RADIUS experts should pay attention to the request to hold
  > a Federated Authentication (FEDAUTH) BOF which will be discussed this
  > morning by the IAB and the IESG.
  > 
  > The Draft Charter is available at
  > http://www.project-moonshot.org/bof/charter/, and more information about
  > this BOF or other BOF requests can be examined at
  > http://trac.tools.ietf.org/bof/trac/
  > 
  > Dan
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>
  > 
  > 
  > 
  > --
  > to unsubscribe send a message to radiusext-request@ops.ietf.org with
  > the word 'unsubscribe' in a single line as the message text body.
  > archive: <http://psg.com/lists/radiusext/>

--Boundary_(ID_6hv+ML6mj+wcKfSI/Z8TQg)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>

<META content="MSHTML 6.00.6000.17023" name=GENERATOR></HEAD>
<BODY class=hmmessage bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff>Hi Bernard,</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff>Comments are in line.</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff>B. R.<BR>Tina</FONT><BR><A 
href="http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.com/contact.html</A></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=bernard_aboba@hotmail.com 
  href="mailto:bernard_aboba@hotmail.com">Bernard Aboba</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">tena@huawei.com</A> ; <A 
  title=aaa-doctors@ietf.org 
  href="mailto:aaa-doctors@ietf.org">aaa-doctors@ietf.org</A> ; <A 
  title=radiusext@ops.ietf.org 
  href="mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</A> ; <A 
  title=dime@ietf.org href="mailto:dime@ietf.org">dime@ietf.org</A> ; <A 
  title=dromasca@avaya.com 
  href="mailto:dromasca@avaya.com">dromasca@avaya.com</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, June 03, 2010 1:03 
  PM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: FEDAUTH BOF request</DIV>
  <DIV><BR></DIV>
  <DIV>Tina said: <BR><BR>&gt; Comments are below.<BR>&gt; 1. This might be of 
  interest to ngHLR (Unified Subscriber Center) kind of <BR>&gt; solutions who 
  provide Identity Management services<BR>&gt; 2. From protocol side, I think it 
  may be more interesting for RADIUS as I&nbsp; doubt the suitability of 
  Diameter for this.<BR><BR>Not sure why RADIUS would be more suitable than 
  Diameter for carrying large payloads such as SAML assertions.&nbsp; The 4096 
  octet RADIUS PDU limit is not transport-specific -- that is, transporting the 
  RADIUS payload over TCP does not solve the problem.&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial color=#0000ff>[Tina: You are also right from the aspect 
  you&nbsp;raised.</FONT></DIV>
  <DIV><FONT face=Arial color=#0000ff>Diameter roaming model is well established 
  (in use cases like WLAN-3GPP interworking) without the use of EAP or SAML. I 
  fail to see what would be the benefits of using EAP or SAML with Diameter 
  which the current roaming model does not already have.</FONT></DIV>
  <DIV><FONT face=Arial><FONT color=#0000ff>Everything has pros and cons, as you 
  said in another email, let's begin with a problem statement, and then 
  protocols.]</FONT><BR></FONT><BR><BR>&nbsp;<BR>&gt; ----- Original Message 
  ----- <BR>&gt; From: "Romascanu, Dan (Dan)" &lt;dromasca@avaya.com&gt;<BR>&gt; 
  To: &lt;dime@ietf.org&gt;; "radext mailing list" 
  &lt;radiusext@ops.ietf.org&gt;; <BR>&gt; &lt;aaa-doctors@ietf.org&gt;<BR>&gt; 
  Sent: Wednesday, June 02, 2010 10:56 PM<BR>&gt; Subject: FEDAUTH BOF 
  request<BR>&gt; <BR>&gt; <BR>&gt; Diameter and RADIUS experts should pay 
  attention to the request to hold<BR>&gt; a Federated Authentication (FEDAUTH) 
  BOF which will be discussed this<BR>&gt; morning by the IAB and the 
  IESG.<BR>&gt; <BR>&gt; The Draft Charter is available at<BR>&gt; 
  http://www.project-moonshot.org/bof/charter/, and more information 
  about<BR>&gt; this BOF or other BOF requests can be examined at<BR>&gt; 
  http://trac.tools.ietf.org/bof/trac/<BR>&gt; <BR>&gt; Dan<BR>&gt; <BR>&gt; 
  --<BR>&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org 
  with<BR>&gt; the word 'unsubscribe' in a single line as the message text 
  body.<BR>&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<BR>&gt; 
  <BR>&gt; <BR>&gt; <BR>&gt; --<BR>&gt; to unsubscribe send a message to 
  radiusext-request@ops.ietf.org with<BR>&gt; the word 'unsubscribe' in a single 
  line as the message text body.<BR>&gt; archive: 
  &lt;http://psg.com/lists/radiusext/&gt;<BR></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_6hv+ML6mj+wcKfSI/Z8TQg)--

From tena@huawei.com  Thu Jun  3 06:58:24 2010
Return-Path: <tena@huawei.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEC6E3A67D4; Thu,  3 Jun 2010 06:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.203
X-Spam-Level: 
X-Spam-Status: No, score=-100.203 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, STOX_REPLY_TYPE=0.001, 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 jAG9DWL7aWLX; Thu,  3 Jun 2010 06:58:23 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id C1C783A67AD; Thu,  3 Jun 2010 06:58:23 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F004TIYSOWK@szxga01-in.huawei.com>; Thu, 03 Jun 2010 21:58:00 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3F00KOGYSOYD@szxga01-in.huawei.com>; Thu, 03 Jun 2010 21:58:00 +0800 (CST)
Received: from z00147053k ([10.70.39.52]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3F00FSMYSMTB@szxml04-in.huawei.com>; Thu, 03 Jun 2010 21:58:00 +0800 (CST)
Date: Thu, 03 Jun 2010 21:57:56 +0800
From: Tina TSOU <tena@huawei.com>
To: dromasca@avaya.com, dime@ietf.org, radiusext@ops.ietf.org, aaa-doctors@ietf.org, Wolfgang.Steigerwald@telekom.de, "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Message-id: <87BAC297AD614E1E8E885DA28CA60DD2@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; format=flowed; charset=ISO-8859-1; reply-type=original
Content-transfer-encoding: 8BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com> <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <F30237DE0DEB964C89C4D3A3473B46E506EC37DB@S4DE9JSAAII.ost.t-com.de> <3D3C75174CB95F42AD6BCC56E5555B4502A8093D@FIESEXC015.nsn-intra.net>
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 13:58:24 -0000

Hi Wolfgang and Hannes,
You are also right from the good nature of Diameter.
I just mentioned one possible interesting point in my previous email 
replying to Bernard et al.

B. R.
Tina
http://tinatsou.weebly.com/contact.html

----- Original Message ----- 
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: <Wolfgang.Steigerwald@telekom.de>; <tena@huawei.com>; 
<aaa-doctors@ietf.org>; <radiusext@ops.ietf.org>; <dime@ietf.org>; 
<dromasca@avaya.com>
Sent: Thursday, June 03, 2010 3:18 PM
Subject: RE: [Dime] FEDAUTH BOF request


Looking forward to hear that answer as well :-)

>-----Original Message-----
>From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On
>Behalf Of ext Wolfgang.Steigerwald@telekom.de
>Sent: 03 June, 2010 10:16
>To: tena@huawei.com; aaa-doctors@ietf.org;
>radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
>Subject: Re: [Dime] FEDAUTH BOF request
>
>Hello Tina,
>
>what assumption let you think RADIUS is more suitable then
>DIAMETER? DIAMETER is much more developed, is a peer to peer
>protocol, designed to transport also structured data, not as
>limited on payload and therefore much better suitable for the
>purpose of IdM.
>
>Best Regards
>
> Wolfgang
>
>-----Ursprüngliche Nachricht-----
>Von: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] Im
>Auftrag von Tina TSOU
>Gesendet: Donnerstag, 3. Juni 2010 06:03
>An: aaa-doctors@ietf.org; radext mailing list; dime@ietf.org;
>Romascanu, Dan (Dan)
>Betreff: Re: [Dime] FEDAUTH BOF request
>
>Comments are below.
>1. This might be of interest to ngHLR (Unified Subscriber
>Center) kind of solutions who provide Identity Management
>services 2. From protocol side, I think it may be more
>interesting for RADIUS as I doubt the suitability of Diameter for this.
>
>B. R.
>Tina
>http://tinatsou.weebly.com/contact.html
>
>----- Original Message -----
>From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>To: <dime@ietf.org>; "radext mailing list"
><radiusext@ops.ietf.org>; <aaa-doctors@ietf.org>
>Sent: Wednesday, June 02, 2010 10:56 PM
>Subject: FEDAUTH BOF request
>
>
>Diameter and RADIUS experts should pay attention to the
>request to hold a Federated Authentication (FEDAUTH) BOF which
>will be discussed this morning by the IAB and the IESG.
>
>The Draft Charter is available at
>http://www.project-moonshot.org/bof/charter/, and more
>information about this BOF or other BOF requests can be
>examined  at http://trac.tools.ietf.org/bof/trac/
>
>Dan
>
>--
>to unsubscribe send a message to
>radiusext-request@ops.ietf.org with the word 'unsubscribe' in
>a single line as the message text body.
>archive: <http://psg.com/lists/radiusext/>
>
>
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>_______________________________________________
>DiME mailing list
>DiME@ietf.org
>https://www.ietf.org/mailman/listinfo/dime
>



From hannes.tschofenig@nsn.com  Thu Jun  3 07:24:58 2010
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B35783A685A; Thu,  3 Jun 2010 07:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level: 
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[AWL=1.135,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 tR908b02uyqX; Thu,  3 Jun 2010 07:24:57 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 90C423A680E; Thu,  3 Jun 2010 07:24:56 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o53EOR0D022994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 3 Jun 2010 16:24:27 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o53EOOoo024469; Thu, 3 Jun 2010 16:24:27 +0200
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 3 Jun 2010 16:23:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB0328.59FB5FAD"
Date: Thu, 3 Jun 2010 17:23:48 +0300
Message-ID: <3D3C75174CB95F42AD6BCC56E5555B4502ABE0A5@FIESEXC015.nsn-intra.net>
In-Reply-To: <A142425E33AB431C8F6FBF8C10E4594B@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AAA-DOCTORS] FEDAUTH BOF request
Thread-Index: AcsDJFV6M+HC0wk3SHCL7LKaHUNzSAAA4e5g
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com><F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com><BLU137-W350A9D16B24A7A1F9D76F193D10@phx.gbl> <A142425E33AB431C8F6FBF8C10E4594B@china.huawei.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Tina TSOU" <tena@huawei.com>, <dromasca@avaya.com>, <dime@ietf.org>,  <radiusext@ops.ietf.org>, <aaa-doctors@ietf.org>, "Bernard Aboba" <bernard_aboba@hotmail.com>
X-OriginalArrivalTime: 03 Jun 2010 14:23:36.0044 (UTC) FILETIME=[5A669AC0:01CB0328]
Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 14:24:58 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB0328.59FB5FAD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The idea these folks have, if I understood it correctly, is to use SAML
assertion mainly as a container for the attributes inside it.=20
=20
In some sense one could argue that it is also not too complicated to
carry the actual attributes in Diameter itself (encoded in Diameter AVP
format instead of using an XML-based encoding).
=20
Ciao
Hannes
=20


________________________________

	From: aaa-doctors-bounces@ietf.org
[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of ext Tina TSOU
	Sent: 03 June, 2010 16:54
	To: dromasca@avaya.com; dime@ietf.org; radiusext@ops.ietf.org;
aaa-doctors@ietf.org; Bernard Aboba
	Subject: Re: [AAA-DOCTORS] FEDAUTH BOF request
=09
=09
	Hi Bernard,
	Comments are in line.
	=20
	B. R.
	Tina
	http://tinatsou.weebly.com/contact.html

		----- Original Message -----=20
		From: Bernard Aboba <mailto:bernard_aboba@hotmail.com> =20
		To: tena@huawei.com ; aaa-doctors@ietf.org ;
radiusext@ops.ietf.org ; dime@ietf.org ; dromasca@avaya.com=20
		Sent: Thursday, June 03, 2010 1:03 PM
		Subject: RE: FEDAUTH BOF request

		Tina said:=20
	=09
		> Comments are below.
		> 1. This might be of interest to ngHLR (Unified
Subscriber Center) kind of=20
		> solutions who provide Identity Management services
		> 2. From protocol side, I think it may be more
interesting for RADIUS as I  doubt the suitability of Diameter for this.
	=09
		Not sure why RADIUS would be more suitable than Diameter
for carrying large payloads such as SAML assertions.  The 4096 octet
RADIUS PDU limit is not transport-specific -- that is, transporting the
RADIUS payload over TCP does not solve the problem.=20
		=20
		[Tina: You are also right from the aspect you raised.
		Diameter roaming model is well established (in use cases
like WLAN-3GPP interworking) without the use of EAP or SAML. I fail to
see what would be the benefits of using EAP or SAML with Diameter which
the current roaming model does not already have.
		Everything has pros and cons, as you said in another
email, let's begin with a problem statement, and then protocols.]
	=09
	=09
		=20
		> ----- Original Message -----=20
		> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
		> To: <dime@ietf.org>; "radext mailing list"
<radiusext@ops.ietf.org>;=20
		> <aaa-doctors@ietf.org>
		> Sent: Wednesday, June 02, 2010 10:56 PM
		> Subject: FEDAUTH BOF request
		>=20
		>=20
		> Diameter and RADIUS experts should pay attention to
the request to hold
		> a Federated Authentication (FEDAUTH) BOF which will be
discussed this
		> morning by the IAB and the IESG.
		>=20
		> The Draft Charter is available at
		> http://www.project-moonshot.org/bof/charter/, and more
information about
		> this BOF or other BOF requests can be examined at
		> http://trac.tools.ietf.org/bof/trac/
		>=20
		> Dan
		>=20
		> --
		> to unsubscribe send a message to
radiusext-request@ops.ietf.org with
		> the word 'unsubscribe' in a single line as the message
text body.
		> archive: <http://psg.com/lists/radiusext/>
		>=20
		>=20
		>=20
		> --
		> to unsubscribe send a message to
radiusext-request@ops.ietf.org with
		> the word 'unsubscribe' in a single line as the message
text body.
		> archive: <http://psg.com/lists/radiusext/>
	=09


------_=_NextPart_001_01CB0328.59FB5FAD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: =
0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 10pt; FONT-FAMILY: Verdana
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D046062014-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D4>The idea these folks have, if I understood it =
correctly, is=20
to use SAML assertion mainly as a container for the attributes inside =
it.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D046062014-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D4></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D046062014-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D4>In some sense one could argue that it is also =
not too=20
complicated to carry the actual attributes in Diameter itself (encoded =
in=20
Diameter AVP format instead of using an XML-based =
encoding).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D046062014-03062010><FONT =
face=3DArial=20
color=3D#0000ff size=3D4></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D046062014-03062010><FONT face=3DArial color=3D#0000ff =

size=3D4>Ciao</FONT></SPAN></DIV>
<DIV><SPAN class=3D046062014-03062010><FONT face=3DArial color=3D#0000ff =

size=3D4>Hannes</FONT></SPAN></DIV>
<DIV><SPAN class=3D046062014-03062010></SPAN>&nbsp;</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> aaa-doctors-bounces@ietf.org =

  [mailto:aaa-doctors-bounces@ietf.org] <B>On Behalf Of </B>ext Tina=20
  TSOU<BR><B>Sent:</B> 03 June, 2010 16:54<BR><B>To:</B> =
dromasca@avaya.com;=20
  dime@ietf.org; radiusext@ops.ietf.org; aaa-doctors@ietf.org; Bernard=20
  Aboba<BR><B>Subject:</B> Re: [AAA-DOCTORS] FEDAUTH BOF=20
  request<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff>Hi Bernard,</FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff>Comments are in =
line.</FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff>B. R.<BR>Tina</FONT><BR><A=20
  =
href=3D"http://tinatsou.weebly.com/contact.html">http://tinatsou.weebly.c=
om/contact.html</A></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Dbernard_aboba@hotmail.com=20
    href=3D"mailto:bernard_aboba@hotmail.com">Bernard Aboba</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dtena@huawei.com=20
    href=3D"mailto:tena@huawei.com">tena@huawei.com</A> ; <A=20
    title=3Daaa-doctors@ietf.org=20
    href=3D"mailto:aaa-doctors@ietf.org">aaa-doctors@ietf.org</A> ; <A=20
    title=3Dradiusext@ops.ietf.org=20
    href=3D"mailto:radiusext@ops.ietf.org">radiusext@ops.ietf.org</A> ; =
<A=20
    title=3Ddime@ietf.org =
href=3D"mailto:dime@ietf.org">dime@ietf.org</A> ; <A=20
    title=3Ddromasca@avaya.com=20
    href=3D"mailto:dromasca@avaya.com">dromasca@avaya.com</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, June 03, 2010 =
1:03=20
    PM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: FEDAUTH BOF =
request</DIV>
    <DIV><BR></DIV>
    <DIV>Tina said: <BR><BR>&gt; Comments are below.<BR>&gt; 1. This =
might be of=20
    interest to ngHLR (Unified Subscriber Center) kind of <BR>&gt; =
solutions who=20
    provide Identity Management services<BR>&gt; 2. From protocol side, =
I think=20
    it may be more interesting for RADIUS as I&nbsp; doubt the =
suitability of=20
    Diameter for this.<BR><BR>Not sure why RADIUS would be more suitable =
than=20
    Diameter for carrying large payloads such as SAML assertions.&nbsp; =
The 4096=20
    octet RADIUS PDU limit is not transport-specific -- that is, =
transporting=20
    the RADIUS payload over TCP does not solve the problem.&nbsp;</DIV>
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff>[Tina: You are also right =
from the=20
    aspect you&nbsp;raised.</FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff>Diameter roaming model is =
well=20
    established (in use cases like WLAN-3GPP interworking) without the =
use of=20
    EAP or SAML. I fail to see what would be the benefits of using EAP =
or SAML=20
    with Diameter which the current roaming model does not already=20
    have.</FONT></DIV>
    <DIV><FONT face=3DArial><FONT color=3D#0000ff>Everything has pros =
and cons, as=20
    you said in another email, let's begin with a problem statement, and =
then=20
    protocols.]</FONT><BR></FONT><BR><BR>&nbsp;<BR>&gt; ----- Original =
Message=20
    ----- <BR>&gt; From: "Romascanu, Dan (Dan)"=20
    &lt;dromasca@avaya.com&gt;<BR>&gt; To: &lt;dime@ietf.org&gt;; =
"radext=20
    mailing list" &lt;radiusext@ops.ietf.org&gt;; <BR>&gt;=20
    &lt;aaa-doctors@ietf.org&gt;<BR>&gt; Sent: Wednesday, June 02, 2010 =
10:56=20
    PM<BR>&gt; Subject: FEDAUTH BOF request<BR>&gt; <BR>&gt; <BR>&gt; =
Diameter=20
    and RADIUS experts should pay attention to the request to =
hold<BR>&gt; a=20
    Federated Authentication (FEDAUTH) BOF which will be discussed =
this<BR>&gt;=20
    morning by the IAB and the IESG.<BR>&gt; <BR>&gt; The Draft Charter =
is=20
    available at<BR>&gt; http://www.project-moonshot.org/bof/charter/, =
and more=20
    information about<BR>&gt; this BOF or other BOF requests can be =
examined=20
    at<BR>&gt; http://trac.tools.ietf.org/bof/trac/<BR>&gt; <BR>&gt; =
Dan<BR>&gt;=20
    <BR>&gt; --<BR>&gt; to unsubscribe send a message to=20
    radiusext-request@ops.ietf.org with<BR>&gt; the word 'unsubscribe' =
in a=20
    single line as the message text body.<BR>&gt; archive:=20
    &lt;http://psg.com/lists/radiusext/&gt;<BR>&gt; <BR>&gt; <BR>&gt; =
<BR>&gt;=20
    --<BR>&gt; to unsubscribe send a message to =
radiusext-request@ops.ietf.org=20
    with<BR>&gt; the word 'unsubscribe' in a single line as the message =
text=20
    body.<BR>&gt; archive:=20
  =
&lt;http://psg.com/lists/radiusext/&gt;<BR></DIV></BLOCKQUOTE></BLOCKQUOT=
E></BODY></HTML>

------_=_NextPart_001_01CB0328.59FB5FAD--

From jsalowey@cisco.com  Fri Jun  4 10:11:43 2010
Return-Path: <jsalowey@cisco.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93F7A3A68F2; Fri,  4 Jun 2010 10:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.051
X-Spam-Level: 
X-Spam-Status: No, score=-9.051 tagged_above=-999 required=5 tests=[AWL=-1.052, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8]
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 tTcwQkkAWDSp; Fri,  4 Jun 2010 10:11:39 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 95A993A6874; Fri,  4 Jun 2010 10:11:37 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEfQCEyrRN+K/2dsb2JhbACeRnGlSJoRgl+COASDSYM5
X-IronPort-AV: E=Sophos;i="4.53,362,1272844800"; d="scan'208";a="139524287"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 04 Jun 2010 17:11:23 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o54HBN6O004272; Fri, 4 Jun 2010 17:11:23 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 4 Jun 2010 10:11:23 -0700
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: Fri, 4 Jun 2010 10:11:22 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE50A9EDD7D@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Dime] FEDAUTH BOF request
Thread-Index: AcsC3V6qlMZy6lk0TKacZwhNYrbcbgBJ7grw
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Bernard Aboba" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
X-OriginalArrivalTime: 04 Jun 2010 17:11:23.0825 (UTC) FILETIME=[F5ADD210:01CB0408]
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2010 17:11:43 -0000

I agree with a lot of what Bernard says below. For better or for worse
EAP is closely associated with AAA.  The fit may be odd in some cases,
but deployments have found success in making it work.  This is why it is
attractive.  I don't think that replacing EAP in AAA with some other
framework, such as GSSAPI, is going to lead to better results.  It is
true that along the way modifications, such as RADSEC, have been
deployed to make things work better.   It is risky to assume that AAA
and EAP can be successfully applied to any arbitrary scenario without a
firm grip on the use cases.  If at the end of the design you end up with
something that is called EAP and AAA, but actually is completely
different you will lose the perceived advantage of building on top of
existing AAA and EAP infrastructure

I'm not as convinced as Bernard that it can't work, but I think there
needs to be a firm understanding of the use cases to determine what is
required to deliver a solution and what changes may be necessary. =20



> -----Original Message-----
> From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf
Of
> Bernard Aboba
> Sent: Wednesday, June 02, 2010 10:26 PM
> To: tena@huawei.com; aaa-doctors@ietf.org; radiusext@ops.ietf.org;
> dime@ietf.org; dromasca@avaya.com
> Subject: Re: [Dime] FEDAUTH BOF request
>=20
> Let me provide a bit of  context about what I think the problem is
here.
>=20
> As noted by Sam in a previous conversation, the basic use case is
"cloud
> services", where an education institution or enterprise is making use
of
> hosted services.  In these situations, the institution may not just
want
> the service provider to host an application, but may want to keep
their
> credentials local, rather than hosting this in the cloud as well.
>=20
> In the original Moonshot investigation, Kerberos was considered as a
> potential solution.  However, while Kerberos is well understood from a
> security point of view, and could relatively easily be modified to
support
> EAP-based pre-auth (numerous proposals for this have been advanced and
in
> some cases implemented)  Kerberos federation has not been widely
deployed.
>=20
> One of the basic problems with putting a KDC on the Internet is that
there
> is no easy way to protect it, since both clients and other KDCs may
need
> to send packets to and from the KDC.  For this reason if there are
roaming
> clients there is no easy way to filter traffic to/from the KDC.  In
> addition, the Kerberos protocol is vulnerable to passive attacks in
the
> absence of extensions such as PKINIT or Kerberos Hardening.
>=20
> In contrast, the AAA roaming model has been widely deployed, in part
> because it is much easier to protect a AAA server.  AAA servers only
talk
> to AAA clients, not to users directly.  This means that it is
typically
> possible to filter traffic to the AAA server so that only packets
> originating from legitimate AAA clients can be sent to/from the AAA
> server.
>=20
> In addition to these basic security issues, the AAA delegation model
is
> much simpler than Kerberos.  Obtaining a Kerberos TGT for a local
realm
> involves first obtaining a TGT from a "home" realm and then requesting
a
> TGT for the local realm.  This involves multiple exchanges, and as
noted
> earlier requires both the local KDC and the home KDC to be available
over
> the Internet.  In contrast, a AAA client implicitly delegates
authority to
> the AAA server for the Accept/Reject decision, so that explicit trust
> relationships don't need to be configured.  As long as the AAA client
can
> reach the AAA server via a chain of proxies the trust relationship can
> succeed.
>=20
> Given these basic characteristics of Kerberos and AAA delegation, the
> Moonshot team has decided that a AAA-based approach to delegation is
more
> likely to be widely deployed than a Kerberos-based one.  My take on
this
> is that this assessment is probably realistic.
>=20
> Where I get lost is making the leap between the AAA delegation model
and
> use of EAP.  As we saw with Digest authentication (RFC 5090), it is
> possible to extend AAA to support application-layer authentication
without
> use of EAP.  For example, using AAA to carry GSS-API payloads would
not
> require much more than defining a GSS-Message attribute.  EAP has no
> unique properties that make it more suitable for use with AAA.  In
fact, I
> would argue that the fit between EAP and AAA has always been tenuous
at
> best -- witness the issues encountered in federated EAP authentication
> that RADSEC has been needed to address.
>=20
> In particular, the problems of EAP auth (e.g. multiple round-trips,
> general fragility in federated uses) become highly toxic when applied
to
> Realtime applications such as XMPP and SIP.  As we have learned,
Digest
> auth (RFC 5090) has not been widely deployed, in part because of
concern
> about the additional latency added by a AAA exchange.  For users of
real-
> time applications, additional latency is a basic, non-negotiable goal.
If
> the relatively modest number of exchanges implied by RFC 5090 were
> intolerable in realtime applications,  how can we expect EAP exchanges
> (which can involve 4-5 times the number of roundtrips of RFC 5090) to
be
> deployed?  The answer unfortunately, is that there is no chance at
all.
>=20
[Joe]=20
> So in summary, I believe that some aspects of the problem statement
make
> sense, but that a solution has been chosen prematurely.  The right way
to
> move forward in a situation like this is to begin with a problem
> statement, which should include carefully validating the uses cases.
>=20
>=20
> > ----- Original Message -----
> > From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> > To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>;
> > <aaa-doctors@ietf.org>
> > Sent: Wednesday, June 02, 2010 10:56 PM
> > Subject: FEDAUTH BOF request
> >
> >
> > Diameter and RADIUS experts should pay attention to the request to
> > hold a Federated Authentication (FEDAUTH) BOF which will be
discussed
> > this morning by the IAB and the IESG.
> >
> > The Draft Charter is available at
> > http://www.project-moonshot.org/bof/charter/, and more information
> > about this BOF or other BOF requests can be examined at
> > http://trac.tools.ietf.org/bof/trac/
> >
> > Dan
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>
> >
> >
> >
> > --
> > to unsubscribe send a message to radiusext-request@ops.ietf.org with
> > the word 'unsubscribe' in a single line as the message text body.
> > archive: <http://psg.com/lists/radiusext/>


From alper.yegin@yegin.org  Fri Jun  4 00:31:50 2010
Return-Path: <alper.yegin@yegin.org>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF2473A6A26; Fri,  4 Jun 2010 00:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.451
X-Spam-Level: *
X-Spam-Status: No, score=1.451 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449]
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 Aq6I6RsV8qsx; Fri,  4 Jun 2010 00:31:42 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 6352D3A6926; Fri,  4 Jun 2010 00:31:42 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MY7Qm-1OpI2f3O8u-00VID5; Fri, 04 Jun 2010 03:31:26 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Bernard Aboba'" <bernard_aboba@hotmail.com>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
In-Reply-To: <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl>
Date: Fri, 4 Jun 2010 10:30:58 +0300
Message-ID: <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A0_01CB03D1.0B8D02F0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhg
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX18y1cDDDbHwzc0rK+re1041lchS1Dg/3U9B3ek zrDOUvkjOhWErTfZBgfmWbJCOxwOu3DJT47CFQbCimRLqJVL6u OOecGjtXfoBXG9HHEBhW97gRdtYxZyP
X-Mailman-Approved-At: Sun, 06 Jun 2010 02:49:49 -0700
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2010 07:31:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  



 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_01A0_01CB03D1.0B8D02F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <br>
<br>
<span style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in =
&nbsp;180-degree
opposite direction, I&#8217;d say the community needs to be =
&#8220;unconvinced&#8221;
first. I&#8217;m not saying this is not doable, but something we need to =
go
through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_01A0_01CB03D1.0B8D02F0--



From bernard_aboba@hotmail.com  Mon Jun  7 08:38:11 2010
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAF1C3A6826; Mon,  7 Jun 2010 08:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001]
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 2Q2beLdh+7BT; Mon,  7 Jun 2010 08:37:37 -0700 (PDT)
Received: from blu0-omc2-s24.blu0.hotmail.com (blu0-omc2-s24.blu0.hotmail.com [65.55.111.99]) by core3.amsl.com (Postfix) with ESMTP id 81C753A86AD; Sun,  6 Jun 2010 09:13:18 -0700 (PDT)
Received: from BLU137-DS5 ([65.55.111.73]) by blu0-omc2-s24.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 6 Jun 2010 09:13:18 -0700
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Alper Yegin'" <alper.yegin@yegin.org>, <tena@huawei.com>, <aaa-doctors@ietf.org>, <radiusext@ops.ietf.org>, <dime@ietf.org>, <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com>	<BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl> <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
In-Reply-To: <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org>
Date: Sun, 6 Jun 2010 09:13:19 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CB0558.818885A0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcsC3Vu3xwQsiPtKT8+vfB1gbF+XiAA2UOhgAHbjbHA=
Content-Language: en-us
X-OriginalArrivalTime: 06 Jun 2010 16:13:18.0263 (UTC) FILETIME=[2CF2C470:01CB0593]
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 15:38:12 -0000

------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Previous tests have shown problems with use of RADIUS/EAP over UDP in
federated scenarios:

http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
network/

 

As noted in the above paper, once packet loss is introduced, completing the
multiple roundtrips of EAP authentication becomes increasingly difficult. 

 

RADIUS over TCP holds up much better until a threshold is reached, and then
authentication success fractions fall dramatically.   

 

Due to the transport issues and RADIUS packet size limitation of 4096 (which
may impact the ability to transport SAML assertions), it seems like Diameter
would be more suitable.  

 

 

 

 

From: aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] On
Behalf Of Alper Yegin
Sent: Friday, June 04, 2010 12:31 AM
To: 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request

 


In particular, the problems of EAP auth (e.g. multiple round-trips, general
fragility in federated uses) become highly toxic when applied to Realtime
applications such as XMPP and SIP.  As we have learned, Digest auth (RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.  For users of real-time
applications, additional latency is a basic, non-negotiable goal.  If the
relatively modest number of exchanges implied by RFC 5090 were intolerable
in realtime applications,  how can we expect EAP exchanges (which can
involve 4-5 times the number of roundtrips of RFC 5090) to be deployed?  The
answer unfortunately, is that there is no chance at all.  

So in summary, I believe that some aspects of the problem statement make
sense, but that a solution has been chosen prematurely.  The right way to
move forward in a situation like this is to begin with a problem statement,
which should include carefully validating the uses cases.  

 

 

Alper> I agree. 

 

Alper> Anyone who was around the ICOS BoF in IETF 62 would remember that the
community was convinced(!) that using EAP for anything other than network
access was a no-no. Now before we embark on marching in  180-degree opposite
direction, I'd say the community needs to be "unconvinced" first. I'm not
saying this is not doable, but something we need to go through first.

 

Alper

 

 

  

> ----- Original Message ----- 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: <dime@ietf.org>; "radext mailing list" <radiusext@ops.ietf.org>; 
> <aaa-doctors@ietf.org>
> Sent: Wednesday, June 02, 2010 10:56 PM
> Subject: FEDAUTH BOF request
> 
> 
> Diameter and RADIUS experts should pay attention to the request to hold
> a Federated Authentication (FEDAUTH) BOF which will be discussed this
> morning by the IAB and the IESG.
> 
> The Draft Charter is available at
> http://www.project-moonshot.org/bof/charter/, and more information about
> this BOF or other BOF requests can be examined at
> http://trac.tools.ietf.org/bof/trac/
> 
> Dan
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>
> 
> 
> 
> --
> to unsubscribe send a message to radiusext-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://psg.com/lists/radiusext/>


------=_NextPart_000_001C_01CB0558.818885A0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Previous tests have shown problems with use of RADIUS/EAP =
over
UDP in federated scenarios:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentic=
ation-over-jammed-network/<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As noted in the above paper, once packet loss is =
introduced, completing
the multiple roundtrips of EAP authentication becomes increasingly =
difficult. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>RADIUS over TCP holds up much better until a threshold is
reached, and then authentication success fractions fall dramatically. =
&nbsp;&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Due to the transport issues and RADIUS packet size =
limitation of
4096 (which may impact the ability to transport SAML assertions), it =
seems like
Diameter would be more suitable. &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
aaa-doctors-bounces@ietf.org [mailto:aaa-doctors-bounces@ietf.org] <b>On =
Behalf
Of </b>Alper Yegin<br>
<b>Sent:</b> Friday, June 04, 2010 12:31 AM<br>
<b>To:</b> 'Bernard Aboba'; tena@huawei.com; aaa-doctors@ietf.org;
radiusext@ops.ietf.org; dime@ietf.org; dromasca@avaya.com<br>
<b>Subject:</b> Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF =
request<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
In particular, the problems of EAP auth (e.g. multiple round-trips, =
general
fragility in federated uses) become highly toxic when applied to =
Realtime
applications such as XMPP and SIP.&nbsp; As we have learned, Digest auth =
(RFC
5090) has not been widely deployed, in part because of concern about the
additional latency added by a AAA exchange.&nbsp; For users of real-time
applications, additional latency is a basic, non-negotiable goal.&nbsp; =
If the
relatively modest number of exchanges implied by RFC 5090 were =
intolerable in
realtime applications,&nbsp; how can we expect EAP exchanges (which can =
involve
4-5 times the number of roundtrips of RFC 5090) to be deployed?&nbsp; =
The
answer unfortunately, is that there is no chance at all.&nbsp; <br>
<br>
So in summary, I believe that some aspects of the problem statement make =
sense,
but that a solution has been chosen prematurely.&nbsp; The right way to =
move
forward in a situation like this is to begin with a problem statement, =
which
should include carefully validating the uses cases.&nbsp; <span
style=3D'color:#1F497D'><o:p></o:p></span></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; I agree. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper&gt; Anyone who was around the ICOS BoF in IETF 62 =
would
remember that the community was convinced(!) that using EAP for anything =
other
than network access was a no-no. Now before we embark on marching in
&nbsp;180-degree opposite direction, I&#8217;d say the community needs =
to be
&#8220;unconvinced&#8221; first. I&#8217;m not saying this is not =
doable, but
something we need to go through first.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Alper<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif"'>&nbsp;
<br>
<br>
&gt; ----- Original Message ----- <br>
&gt; From: &quot;Romascanu, Dan (Dan)&quot; =
&lt;dromasca@avaya.com&gt;<br>
&gt; To: &lt;dime@ietf.org&gt;; &quot;radext mailing list&quot;
&lt;radiusext@ops.ietf.org&gt;; <br>
&gt; &lt;aaa-doctors@ietf.org&gt;<br>
&gt; Sent: Wednesday, June 02, 2010 10:56 PM<br>
&gt; Subject: FEDAUTH BOF request<br>
&gt; <br>
&gt; <br>
&gt; Diameter and RADIUS experts should pay attention to the request to =
hold<br>
&gt; a Federated Authentication (FEDAUTH) BOF which will be discussed =
this<br>
&gt; morning by the IAB and the IESG.<br>
&gt; <br>
&gt; The Draft Charter is available at<br>
&gt; http://www.project-moonshot.org/bof/charter/, and more information =
about<br>
&gt; this BOF or other BOF requests can be examined at<br>
&gt; http://trac.tools.ietf.org/bof/trac/<br>
&gt; <br>
&gt; Dan<br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: &lt;http://psg.com/lists/radiusext/&gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; --<br>
&gt; to unsubscribe send a message to radiusext-request@ops.ietf.org =
with<br>
&gt; the word 'unsubscribe' in a single line as the message text =
body.<br>
&gt; archive: =
&lt;http://psg.com/lists/radiusext/&gt;<o:p></o:p></span></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_001C_01CB0558.818885A0--

From peterd@iea-software.com  Mon Jun  7 09:58:42 2010
Return-Path: <peterd@iea-software.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF5E83A6817; Mon,  7 Jun 2010 09:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 u4yDDCTffqRq; Mon,  7 Jun 2010 09:58:41 -0700 (PDT)
Received: from aspen.internal.iea-software.com (remote.iea-software.com [70.89.142.196]) by core3.amsl.com (Postfix) with ESMTP id EA99B3A9029; Sun,  6 Jun 2010 14:04:42 -0700 (PDT)
Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005291726@aspen.internal.iea-software.com>;  Sun, 6 Jun 2010 14:04:42 -0700
Date: Sun, 6 Jun 2010 14:04:39 -0700 (Pacific Daylight Time)
From: Peter Deacon <peterd@iea-software.com>
To: Bernard Aboba <bernard_aboba@hotmail.com>
In-Reply-To: <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
Message-ID: <alpine.WNT.2.00.1006061319410.1732@SMURF>
References: <EDC652A26FB23C4EB6384A4584434A04022444EC@307622ANEX5.global.avaya.com>, <F3CA54ABFDD5489FAFE036ECB6EE0011@china.huawei.com> <BLU137-W24E56D43201C0B9EEB3A4A93D10@phx.gbl> <019f01cb03b7$e63fcaf0$b2bf60d0$@yegin@yegin.org> <BLU137-DS5162535EAE6642C60FB4893D40@phx.gbl>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Mon, 07 Jun 2010 10:16:34 -0700
Cc: aaa-doctors@ietf.org, 'Alper Yegin' <alper.yegin@yegin.org>, dime@ietf.org, radiusext@ops.ietf.org
Subject: Re: [AAA-DOCTORS] [Dime] FEDAUTH BOF request
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 16:58:42 -0000

On Sun, 6 Jun 2010, Bernard Aboba wrote:

> Previous tests have shown problems with use of RADIUS/EAP over UDP in
> federated scenarios:

> http://www.cesnet.cz/doc/techzpravy/2008/eduroam-authentication-over-jammed-
> network/

> As noted in the above paper, once packet loss is introduced, completing the
> multiple roundtrips of EAP authentication becomes increasingly difficult.

This paper has some crazy figures.. look at the data for packet loss.

40% packet loss (client to server) = 78% success rate for PEAP-MSCHAPv2
40% packet loss (server to client) = 20% success rate for PEAP-MSCHAPv2

There is a footnote on this issue "The more favorable results for 
client-to-server jamming are caused by the aggressive packet re-sending 
strategy of wpa_supplicant compared to the behavior of Radiator."

If the server did not receive client request or client did not receive 
server response the knowledge available and avenue for response by the 
client is the same in either case.  The figures appear to reflect a 
substantial implementation artifact in the servers tx side retransmit.

regards,
Peter

From dromasca@avaya.com  Fri Jun 11 00:47:43 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06AF03A6A0A; Fri, 11 Jun 2010 00:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.243
X-Spam-Level: 
X-Spam-Status: No, score=-0.243 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_50=0.001]
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 VNtJOwFamRSb; Fri, 11 Jun 2010 00:47:41 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id D87693A677D; Fri, 11 Jun 2010 00:47:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,402,1272859200"; d="scan'208";a="192947575"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Jun 2010 03:47:40 -0400
X-IronPort-AV: E=Sophos;i="4.53,402,1272859200"; d="scan'208";a="471541479"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 Jun 2010 03:47:39 -0400
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: Fri, 11 Jun 2010 09:47:16 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022831EE@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for the June 17, 2010 IESG Teleconference 
Thread-Index: AcsI6YTBDzPc89uDQoC2Yy7/rVs8vwAUGjXA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-dir@ietf.org>, <dns-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for the June 17, 2010 IESG Teleconference
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2010 07:47:43 -0000

Please find below the preliminary agenda of the IESG telechat scheduled
for 6/17. Please send me your comments, questions and concerns about the
documents brought up for approval before Wednesday 6/16 COB.=20

Thanks and Regards,

Dan

----------------------------------------------


2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items

  o draft-ietf-enum-3761bis-08
    The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation
    Discovery System (DDDS) Application (ENUM) (Proposed Standard)
    Note: Richard Shockey (richard@shockey.us) is the document
    shepherd.Cluster - draft-ietf-enum-3761bis-
    draft-ietf-enum-enumservices-guide-
    draft-ietf-enum-enumservices-transition
    Token: Gonzalo Camarillo

  o draft-ietf-enum-enumservices-guide-20
    IANA Registration of Enumservices: Guide, Template and IANA
    Considerations (Proposed Standard)
    Note: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> is shepherd
    fro this. Proto write up entered as IESG note on 2010-0225.
    Should cluster with- draft-ietf-enum-3761bis-
    draft-ietf-enum-enumservices-guide-
    draft-ietf-enum-enumservices-transition
    Token: Gonzalo Camarillo

  o draft-ietf-enum-enumservices-transition-05
    Update of legacy IANA Registrations of Enumservices (Proposed
    Standard)
    Note: Richard Shockey (richard@shockey.us) is the document
    shepherd.cluster with- draft-ietf-enum-3761bis-
    draft-ietf-enum-enumservices-guide-
    draft-ietf-enum-enumservices-transition
    Token: Gonzalo Camarillo

  o draft-ietf-netconf-monitoring-14
    YANG Module for NETCONF Monitoring (Proposed Standard)
    Note: Mehmet Ersue (mehmet.ersue@nsn.com) is the Document Shepard
    for this document.
    Token: Dan Romascanu

  o draft-ietf-mboned-ipv4-uni-based-mcast-06
    Unicast-Prefix-based IPv4 Multicast Addresses (Proposed Standard)
    Note: Lenny Giuliano (lenny@juniper.net) is the Document Shepherd.
    Token: Ron Bonica

  o draft-ietf-dnsext-dns-tcp-requirements-03
    DNS Transport over TCP - Implementation Requirements (Proposed
    Standard)
    Note: Olafur Gudmundsson (ogud@ogud.com) is the document shepherd.
    Token: Ralph Droms

  o draft-ietf-ipsecme-eap-mutual-03
    An Extension for EAP-Only Authentication in IKEv2 (Proposed
    Standard)
    Note: Paul Hoffman (paul.hoffman@vpnc.org) is the document shepherd.
    Token: Sean Turner

  o draft-ietf-mpls-tp-data-plane-03
    MPLS Transport Profile Data Plane Architecture (Proposed Standard)
    Note: Loa Andersson (loa@pi.nu) is the Document Shepherd.
    Token: Adrian Farrel

2.1.2 Returning Items

  o draft-freed-sieve-notary-09
    Sieve Email Filtering: Delivery Status Notifications and Deliver-By
    Extensions (Proposed Standard)
    Note: This is a Sieve WG document, despite the name. Cyrus Daboo is
    the document shepherd. Bringing this document for another IESG
    review after changes resulting from SecDir review.
    Token: Alexey Melnikov

2.2 Individual Submissions
2.2.1 New Items

  o draft-kucherawy-authres-header-b-02
    Authentication-Results Registration For Differentiating Among
    Cryptographic Results (Proposed Standard)
    Note: Barry Leiba <barryleiba@computer.org> is the document
    shepherd.The example would need to be fixed as per an IETF LC
    comment.
    Token: Alexey Melnikov

  o rfc4049
    BinaryTime: An alternate format for representing date and time in
    ASN.1 (Proposed)
    Token: Alexey Melnikov

2.2.2 Returning Items

  NONE

3. Document Actions
3.1 WG Submissions
3.1.1 New Items

  o draft-ietf-nsis-applicability-mobility-signaling-17
    NSIS Protocols operation in Mobile Environments (Informational)
    Note: The document shepherd is Martin Stiemerling
    (martin.stiemerling@neclab.eu).
    Token: Lars Eggert

  o draft-ietf-bmwg-protection-term-08
    Benchmarking Terminology for Protection Performance (Informational)
    Note: Al Morton (acmorton@att.com) is the shepherd.
    Token: Ron Bonica

  o draft-ietf-hip-via-01
    Host Identity Protocol (HIP) Multi-hop Routing Extension
    (Experimental)
    Note: David Ward (dward@juniper.net) is the document shepherd.
    Token: Ralph Droms

  o draft-ietf-hip-hiccups-02
    HIP (Host Identity Protocol) Immediate Carriage and Conveyance of
    Upper- layer Protocol Signaling (HICCUPS) (Experimental)
    Note: David Ward (dward@juniper.net) is the document shepherd.
    Token: Ralph Droms

  o draft-ietf-hip-bone-06
    HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking
    Environment (Experimental)
    Note: David Ward (dward@juniper.net) is the document shepherd.
    Token: Ralph Droms

  o rfc5652
    Cryptographic Message Syntax (CMS) (Standard)
    Token: Tim Polk

3.1.2 Returning Items

  NONE

3.2 Individual Submissions Via AD
3.2.1 New Items

  NONE

3.2.2 Returning Items

  NONE

3.3 Independent Submissions Via RFC Editor
3.3.1 New Items

  o draft-rosen-vpn-mcast-15
    Cisco Systems' Solution for Multicast in MPLS/BGP IP VPNs
    (Informational)
    Token: Adrian Farrel

3.3.2 Returning Items

  NONE

3.3.3 For Action

  o draft-keromytis-tls-authz-keynote-06
    Transport Layer Security (TLS) Authorization Using KeyNote
    (Informational)
    Token: Russ Housley

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review

  o Call Control UUI for SIP (cuss)
    Token: Gonzalo

  o Sip ALerting for User Devices (salud)
    Token: Gonzalo

  o DISaggregated Media Architecture for Network-enabled Transmissions
among Loosely-coupled End-devices (dismantle)
    Token: Gonzalo

4.1.2 Proposed for Approval

  NONE

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

  NONE

4.2.2 Proposed for Approval

  NONE

------------------------------------------------------------------------



From david@mitton.com  Fri Jun 18 09:45:35 2010
Return-Path: <david@mitton.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D0083A687E for <aaa-doctors@core3.amsl.com>; Fri, 18 Jun 2010 09:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.459
X-Spam-Level: *
X-Spam-Status: No, score=1.459 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
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 fD1TH3ZKtoyO for <aaa-doctors@core3.amsl.com>; Fri, 18 Jun 2010 09:45:34 -0700 (PDT)
Received: from smtprelay.hostedemail.com (smtprelay0098.hostedemail.com [216.40.44.98]) by core3.amsl.com (Postfix) with ESMTP id 577833A68EA for <aaa-doctors@ietf.org>; Fri, 18 Jun 2010 09:45:33 -0700 (PDT)
Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay02.hostedemail.com (Postfix) with SMTP id 19C409C3B1B for <aaa-doctors@ietf.org>; Fri, 18 Jun 2010 16:45:38 +0000 (UTC)
X-Panda: scanned!
X-Session-Marker: 6461766964406D6974746F6E2E636F6D
X-Filterd-Recvd-Size: 7557
Received: from webmail10 (imap-ext [216.40.42.5]) (Authenticated sender: david@mitton.com) by omf08.hostedemail.com (Postfix) with ESMTP for <aaa-doctors@ietf.org>; Fri, 18 Jun 2010 16:45:37 +0000 (UTC)
Received: from 128.221.197.57 ([128.221.197.57]) by webmail10 (Tucows Webmail) with HTTP; Fri, 18 Jun 2010 16:45:37 +0000 (GMT)
Date: Fri, 18 Jun 2010 16:45:37 +0000 (GMT)
From: David Mitton <david@mitton.com>
To: aaa-doctors@ietf.org
Message-ID: <385778386.11163.1276879537776.JavaMail.mail@webmail10>
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [128.221.197.57]
Subject: Re: [AAA-DOCTORS] draft-ietf-ipsecme-eap-mutual-03.txt
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: david@mitton.com
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2010 16:45:35 -0000

<html><HEAD><LINK rel=stylesheet type=text/css href="/webmail/static/deg/css/wysiwyg-3451203449.css" media=all>
<META name=GENERATOR content="MSHTML 8.00.6001.18928"></HEAD>
<BODY>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>Sorry, <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></SPAN></P>
<DIV style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri><SPAN style="mso-spacerun: yes">&nbsp; </SPAN>I know I'm past yesterday's telechat with this item, but I still wanted to air this issue to this group, FWIW.</FONT></FONT></SPAN></DIV>
<DIV style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>(first I had to find where I had sent it from and then move to&nbsp;the mailbox I'm subscribed from)</FONT></FONT></SPAN></DIV>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>Since I sent the email below, I got a couple comments, and EAP-POTP was added to the list in the current draft.<o:p></o:p></FONT></FONT></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>So my squeak got greased, but I still don't think this is the right way to go about this.<o:p></o:p></FONT></FONT></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>Thanks,<o:p></o:p></FONT></FONT></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><FONT size=3><FONT face=Calibri>Dave.<o:p></o:p></FONT></FONT></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">_____________________________________________<BR><B>From:</B> Mitton, Dave <BR><B>Sent:</B> Thursday, April 08, 2010 11:17 AM<BR><B>To:</B> pasi.eronen@nokia.com; Hannes.Tschofenig@gmx.net; yaronf@checkpoint.com<BR><B>Cc:</B> aland@deployingradius.com; jsalowey@cisco.com; David Mitton<BR><B>Subject:</B> RE: draft-ietf-ipsecme-eap-mutual-00.txt<o:p></o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>Pasi, Hannes, Yaron,</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT face=Calibri><FONT size=3><SPAN style="mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN>I'm looking at this draft you have authored, and am a bit dismayed by the table in section 4, "Allowed EAP Methods"</FONT></FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>with the sentence </FONT></P><PRE style="PAGE-BREAK-BEFORE: always"><o:p><FONT size=3>&nbsp;</FONT></o:p></PRE><PRE style="PAGE-BREAK-BEFORE: always"><FONT size=3>"</FONT><SPAN style="FONT-SIZE: 10pt; mso-ansi-language: EN" lang=EN>Methods not listed below (or in the IANA registry that extends this list) MUST NOT be used with the<o:p></o:p></SPAN></PRE>
<P style="PAGE-BREAK-BEFORE: always; MARGIN: 0in 0in 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN" lang=EN><SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>mechanism defined here."<o:p></o:p></SPAN></P>
<P style="PAGE-BREAK-BEFORE: always; MARGIN: 0in 0in 0pt; tab-stops: 45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt" class=MsoNormal><SPAN style="FONT-FAMILY: 'Courier New'; FONT-SIZE: 10pt; mso-ansi-language: EN" lang=EN><o:p>&nbsp;</o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>The method we support here at RSA Security, EAP-POTP (RFC 4793) I believe meets the criteria of this draft, and I'm not happy by be excluded without reason. </FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>It's not clear what criteria you used to generate this list, perhaps other than personal familiarity.</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>I would also pick a nit with your definition of "Allows Channel Binding".<SPAN style="mso-spacerun: yes">&nbsp;&nbsp; </SPAN>If you want to distinguish Identity protection, then re-label it.</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>EAP-POTP has several Channel Binding and Cryptographic bindings techniques in it, which don't relate to directly to the identity.</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>In general, I'm sure I don't like the idea of burying an obscure evaluation of other EAP methods in a document without review by a wider audience.</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>I would prefer to see a set of criteria and/or required security properties instead of a list generated from a small number of authors.</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3><FONT face=Calibri>This doesn't feel like something an open standard should be doing to other EAP developers.<SPAN style="mso-spacerun: yes">&nbsp;&nbsp;&nbsp; </SPAN></FONT></FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><FONT size=3 face=Calibri>&nbsp;</FONT></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>David Mitton</FONT></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><FONT size=3 face=Calibri>RSA Security Division of EMC, Inc.</FONT></P></BODY></html>

From dromasca@avaya.com  Wed Jun 23 03:05:37 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 884953A68AF; Wed, 23 Jun 2010 03:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.806
X-Spam-Level: 
X-Spam-Status: No, score=-1.806 tagged_above=-999 required=5 tests=[AWL=0.793,  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 qOnQhMxXzom2; Wed, 23 Jun 2010 03:05:36 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id D1D983A67F6; Wed, 23 Jun 2010 03:05:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="21954687"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 23 Jun 2010 06:05:34 -0400
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="475122964"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 Jun 2010 06:04:58 -0400
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: Wed, 23 Jun 2010 12:04:48 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022B997B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Call Control UUI for SIP (cuss) 
Thread-Index: AcsSLG1A83zuJOvPQq6o9Y1ihb30owAjr3kQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Call Control UUI for SIP (cuss)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 10:05:37 -0000

Please find below the proposed charter of the CUSS WG in RAI. Please
send your questions, comments and concerns before 6/29 COB.=20

Thanks and Regards,

Dan


-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Tuesday, June 22, 2010 8:00 PM
To: new-work@ietf.org
Subject: WG Review: Call Control UUI for SIP (cuss)=20

A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area.  The IESG has not made any determination as
yet.
The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, June 29, 2010. =20

Call Control UUI for SIP  (cuss)
--------------------------------------------------
Current Status: Proposed Working Group

Last modified: 2010-06-21

Chair(s):
  TBD

Real-time Applications and Infrastructure Area Director(s):
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
  Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>

Mailing Lists: TBD

Description of Working Group:

The Call Control UUI for SIP (CUSS) working group is chartered to define
a Session Initiation Protocol (SIP) mechanism for transporting
call-control related user-to-user information (UUI) between User Agents.
=20
The mechanism developed in this working group is applicable in the
following situations:

1. The information is generated and consumed by an application using
   SIP during session setup but the application is not necessarily
   even SIP aware.
2. The behavior of SIP entities that support it is not significantly
   changed (as discussed in Section 4 of RFC 5727).
3. Generally only the User Agent Client (UAC) and User Agent Server
   (UAS) are interested in the information.
4. The information is expected to survive retargeting, redirection,
   and transfers.
5. SIP elements may need to apply policy about passing and screening
   the information.
6. Multi-vendor interoperability is important.

This mechanism is not applicable in the following situations:

1. The behavior of SIP entities that support it is significantly
   changed (as discussed in Section 4 of RFC 5727).
2. The information is generated and consumed at the SIP layer by SIP
   elements.
3. SIP elements besides the UAC and UAS might be interested in
   consuming (beyond applying policy) the information.
4. There are specific privacy issues involved with the information
   being transported (e.g., geolocation or emergency-related
   information).

User data of the mechanism will be clearly marked with the application,
encoding, semantics, and content type, allowing policy to be applied by
UAs.  The working group will define the information that each
application must specify to utilize the mechanism. This type of
application-specific information will be specified in standards-track
documents.
=20
One important application of this mechanism is interworking with the
ISDN User to User Information Service.  This application defined by
ITU-T Q.931 is extensively deployed in the PSTN today supporting such
applications as contact centers, call centers, and automatic call
distributors (ACDs).  A major barrier to the movement of these
applications to SIP is the lack of a standard mechanism to transport
this information in SIP.  For interworking with ISDN, minimal
information about the content of the UUI is available to the PSTN-SIP
gateways.  In this case only, the content will just indicate ISDN UUI
Service 1 interworking rather than the actual content.
=20
Call control UUI is user information conveyed between user agents during
call control operations.  As a result, the information must be conveyed
with the INVITE transaction, and must survive proxy retargeting,
redirection, and transfers.  The mechanism must utilize a minimum of SIP
extensions since it will need to be supported by many simple SIP user
agents such as PSTN gateways.  The mechanism must interwork with the
existing ISDN service but should also be extensible for use by other
applications and non-ISDN protocols.

Even though interworking with the PSTN is an important requirement, call
control UUI can be exchanged between native SIP clients that do not have
any ISUP support. Therefore, existing SIP-T encapsulation-based
approaches defined in RFC3372 do not meet the requirements to transport
this type of information.

Mechanisms based on the SIP INFO method, RFC2976, will not be considered
by the working group since the UUI contents carry information that must
be conveyed during session setup at the user agent - the information
must be conveyed with the INVITE transaction.
The information must be passed with the session setup request (INVITE),
responses to that INVITE, or session termination requests.
As a result, it is not possible to use INFO in these cases.
=20
The group will produce:

- A problem statement and requirements document for implementing a SIP
call control UUI mechanism
=20
- A specification of the SIP extension to best meet those requirements.
=20
Goals and Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20
Sep 10 - Problem statement and requirements document to IESG
(Informational)
Mar 11 - SIP call control UUI specification to IESG (PS)

From dromasca@avaya.com  Wed Jun 23 03:06:03 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6771B3A67F6; Wed, 23 Jun 2010 03:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level: 
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[AWL=0.776,  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 v7+fEWpx7Usc; Wed, 23 Jun 2010 03:06:02 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 3DA7A3A68AF; Wed, 23 Jun 2010 03:06:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="194820593"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Jun 2010 06:06:07 -0400
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="475123469"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 23 Jun 2010 06:06:05 -0400
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: Wed, 23 Jun 2010 12:06:04 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022B997E@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Loosely-coupled SIP Devices (LSD) 
Thread-Index: AcsSMLLSU8ceL4aSQbaZDQnoTuL/HgAiuXEQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Loosely-coupled SIP Devices (LSD)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 10:06:03 -0000

=20
Please find below the proposed charter of the LSD WG in RAI. Please send
your questions, comments and concerns before 6/29 COB.=20

Thanks and Regards,

Dan

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Tuesday, June 22, 2010 8:30 PM
To: new-work@ietf.org
Subject: WG Review: Loosely-coupled SIP Devices (LSD)=20

A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area.  The IESG has not made any determination as
yet.
The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, June 29, 2010. =20

Loosely-coupled SIP Devices (LSD)
--------------------------------------------------
Current Status: Proposed Working Group

Last modified: 2010-06-21

Chair(s):
  TBD

Real-time Applications and Infrastructure Area Director(s):
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
  Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>

Mailing Lists: TBD

Description of Working Group:

Loosely-coupled SIP Devices (LSD)
--------------------------------------------

Disaggregated media refers to the ability for a user to create a
multimedia session combining different media streams coming from
different devices under his or her control so that they are treated by
the far end of the session as a single media session.=20

Generally, a given participant uses a single device to establish (or
participate in) a given multimedia session.  Consequently, the SIP
signaling to manage the multimedia session and the actual media streams
are typically co-located in the same device.  In scenarios involving
disaggregated media, a user wants to establish a single multimedia
session combining different media streams coming from different devices
under his or her control.  This creates a need to coordinate the
exchange of the those media streams within the multimedia session.

There are a number of existing mechanisms that can be used to coordinate
different devices under user's control and to involve them in the call
(e.g. Message Bus (Mbus) [RFC3259], Megaco [ITU-T H.248.1] and SIP 3pcc
[RFC3725]). However, these mechanisms are intended to be used in
"tightly coupled" scenarios. The use of all those mechanisms requires
the presence of a "master" device. That is, at least one among the
different devices under the control of the same user must support the
control mechanism and be able to become a controller for the other
devices in the call. Moreover, the "master" device is supposed to remain
involved in the user's session for its entire duration given that
performing a handover of the master role is typically cumbersome and
sometimes impossible.

The objective of this working group is to develop a framework for
disaggregated media in "loosely-coupled" scenarios, where no single
device needs to remain in the session for its entire duration and no
single device needs to act as a master. Coordination among devices in
this type of scenario is less tight than in the scenarios described
above since they do not assume central elements with complete knowledge
of the whole media session. While the framework may describe how to use
existing mechanisms (e.g., the SIP REFER method) to coordinate devices,
the working group will not develop new device coordination mechanisms.
The framework may identify the need for new
(non-device-coordination) mechanisms to enable the implementation of
loosely-coupled scenarios. In case the need for such new mechanisms is
identified, the working group will specify them.

Specifically, the proposed working group will develop the following
deliverables:

1. A framework document describing key considerations for the exchange
   of disaggregated media in SIP. The document will include use cases
   and examples. The document may indentify the need for new
   mechanisms or extensions to existing mechanisms.

2. Specifications of new mechanisms or extensions to existing
   mechanisms if the need is identified in the framework.

Goals and Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Feb 2011 - Framework document sent to the IESG (Informational)

From dromasca@avaya.com  Wed Jun 23 03:07:08 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F05B3A697B; Wed, 23 Jun 2010 03:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.838
X-Spam-Level: 
X-Spam-Status: No, score=-1.838 tagged_above=-999 required=5 tests=[AWL=0.761,  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 Lowty-y+6y4y; Wed, 23 Jun 2010 03:07:07 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id EDFDD3A6910; Wed, 23 Jun 2010 03:07:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="194820741"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 Jun 2010 06:07:11 -0400
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="485701327"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Jun 2010 06:07:10 -0400
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: Wed, 23 Jun 2010 12:06:53 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022B997F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Sip ALerting for User Devices (salud) 
Thread-Index: AcsSLou6FtIRcVsoR9aya0rxCpvz9gAjTDYA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Sip ALerting for User Devices (salud)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 10:07:08 -0000

 Please find below the proposed charter of the SALUD WG in RAI. Please
send your questions, comments and concerns before 6/29 COB.=20

Thanks and Regards,

Dan

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Tuesday, June 22, 2010 8:15 PM
To: ietf-announce@ietf.org
Subject: WG Review: Sip ALerting for User Devices (salud)=20

A new IETF working group has been proposed in the Real-time Applications
and Infrastructure Area.  The IESG has not made any determination as
yet.
The following draft charter was submitted, and is provided for
informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, June 29, 2010. =20

Sip ALerting for User Devices (salud)
--------------------------------------------------
Current Status: Proposed Working Group

Last modified: 2010-06-21

Chair(s):
  TBD

Real-time Applications and Infrastructure Area Director(s):
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
  Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
  Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>

Mailing Lists: TBD

Description of Working Group:

The SALUD (Sip ALerting for User Devices) working group is chartered to
define a new URN namespace that allows SIP to convey a particular alert
indication using a name instead of a referenced URI. The Alert-Info URN
namespace addresses issues encountered in current systems that use the
Alert-Info header field. It is expected that this group will collaborate
with the Applications area on the definition of the URN namespace.

RFC 3261 allows a user agent server to provide a specific ringing tone,
which can be played to the calling user, as a reference (e.g., an HTTP
URI) in the Alert-Info header. In some situations, the calling user may
not be able to understand the meaning of the ringing tone being played.
For example, a user from a given country may not be familiar with the
tone used to indicate call waiting in another country. Similarly, a
hearing impaired person may prefer to get a visual call waiting
indication instead of a call waiting tone.

RFC 3261 also allows a user agent client to provide a reference to a
specific alerting tone, which can be played to the called user (e.g.,
tones for emergency announcements sent over PBX systems or over the
local telephone network). As in the previous examples, in some
situations, the calling user may not be able to understand the meaning
of the alerting tone being played.

These issues can be resolved with a mechanism for user agents to
exchange this type of alerting information in a semantic way. In this
way, different user agents can use different renderings for the same
semantics. For example, a user agent client instructed to inform its
user about a call waiting service being provided can use the
personalized tones that were previously configured by the user.

Traditionally, SIP has used status codes to encode session state
information (e.g., 180 Ringing). Status codes are used by SIP entities
in an automatic fashion. The information this working group is concerned
with is related to rendering and may not represent the state of the
session. Additionally, the exchange of this information does not affect
the way SIP entities process the session. That is why status codes are
not an appropriate vehicle to encode this type of information. This
working group will work on encoding this information in URNs.

In addition to defining URNs that are associated to particular events
(e.g., a call waiting service is being applied), this working group will
also define URNs that describe the characteristics of the alerting to be
applied (e.g., play a short tone followed by a long tone).

There are a variety of non-interoperable URI conventions and proprietary
Alert-Info header field parameters to provide this type of information
today. A standardized set of Alert-Info URNs will increase SIP
interoperability for this header field by replacing proprietary
conventions.

The group will produce a specification that:

* describes the problem statement.

* describes requirements and  use cases.

* defines an Alert-Info URN-scheme which allows to resolve the
  interoperability problems described in the use cases.

* defines the specific Alert-Info URNs identifiers for some of the use
  cases above.

The Alert-Info URN namespace must be open, so that additional Alert-Info
URNs can be defined later if necessary.

Goals and Milestones
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Aug 2011 - Alert-Info URN specification to IESG (PS)

From mehmet.ersue@nsn.com  Wed Jun 23 06:22:19 2010
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 716763A68A4; Wed, 23 Jun 2010 06:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.235
X-Spam-Level: 
X-Spam-Status: No, score=-2.235 tagged_above=-999 required=5 tests=[AWL=0.364,  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 1Shq9XzZ7sFV; Wed, 23 Jun 2010 06:22:08 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id AC16C3A6A77; Wed, 23 Jun 2010 06:22:05 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o5NDM960028790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 23 Jun 2010 15:22:09 +0200
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o5NDM86K018780; Wed, 23 Jun 2010 15:22:09 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 23 Jun 2010 15:22:08 +0200
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: Wed, 23 Jun 2010 15:22:07 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A649EFEEE@DEMUEXC006.nsn-intra.net>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04022B997B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
Thread-Index: AcsSLG1A83zuJOvPQq6o9Y1ihb30owAjr3kQAABByQA=
References: <EDC652A26FB23C4EB6384A4584434A04022B997B@307622ANEX5.global.avaya.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Romascanu, Dan (Dan)" <dromasca@avaya.com>, <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
X-OriginalArrivalTime: 23 Jun 2010 13:22:08.0266 (UTC) FILETIME=[149356A0:01CB12D7]
Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 13:22:19 -0000

Hi,

> The group will produce:
> - A problem statement and requirements document for implementing a SIP
> call control UUI mechanism
> - A specification of the SIP extension to best meet those=20
> requirements.

It might be an old issue and already discussed earlier but=20
I still have some problems to understand why a workgroup is=20
necessary for such a (more or less) small issue?

I think a RAI area WG is still interesting for issues without=20
a home in existing RAI area workgroups.=20

Cheers,
Mehmet

=20

> -----Original Message-----
> From: ops-dir-bounces@ietf.org=20
> [mailto:ops-dir-bounces@ietf.org] On Behalf Of ext Romascanu,=20
> Dan (Dan)
> Sent: Wednesday, June 23, 2010 12:05 PM
> To: aaa-doctors@ietf.org; MIB Doctors (E-mail);=20
> dns-dir@ietf.org; ops-dir@ietf.org
> Subject: [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
>=20
> Please find below the proposed charter of the CUSS WG in RAI. Please
> send your questions, comments and concerns before 6/29 COB.=20
>=20
> Thanks and Regards,
>=20
> Dan
>=20
>=20
> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On=20
> Behalf Of
> IESG Secretary
> Sent: Tuesday, June 22, 2010 8:00 PM
> To: new-work@ietf.org
> Subject: WG Review: Call Control UUI for SIP (cuss)=20
>=20
> A new IETF working group has been proposed in the Real-time=20
> Applications
> and Infrastructure Area.  The IESG has not made any determination as
> yet.
> The following draft charter was submitted, and is provided for
> informational purposes only. Please send your comments to the IESG
> mailing list (iesg@ietf.org) by Tuesday, June 29, 2010. =20
>=20
> Call Control UUI for SIP  (cuss)
> --------------------------------------------------
> Current Status: Proposed Working Group
>=20
> Last modified: 2010-06-21
>=20
> Chair(s):
>   TBD
>=20
> Real-time Applications and Infrastructure Area Director(s):
>   Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
>   Robert Sparks <rjsparks@nostrum.com>
>=20
> Real-time Applications and Infrastructure Area Advisor:
>   Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
>=20
> Mailing Lists: TBD
>=20
> Description of Working Group:
>=20
> The Call Control UUI for SIP (CUSS) working group is=20
> chartered to define
> a Session Initiation Protocol (SIP) mechanism for transporting
> call-control related user-to-user information (UUI) between=20
> User Agents.
> =20
> The mechanism developed in this working group is applicable in the
> following situations:
>=20
> 1. The information is generated and consumed by an application using
>    SIP during session setup but the application is not necessarily
>    even SIP aware.
> 2. The behavior of SIP entities that support it is not significantly
>    changed (as discussed in Section 4 of RFC 5727).
> 3. Generally only the User Agent Client (UAC) and User Agent Server
>    (UAS) are interested in the information.
> 4. The information is expected to survive retargeting, redirection,
>    and transfers.
> 5. SIP elements may need to apply policy about passing and screening
>    the information.
> 6. Multi-vendor interoperability is important.
>=20
> This mechanism is not applicable in the following situations:
>=20
> 1. The behavior of SIP entities that support it is significantly
>    changed (as discussed in Section 4 of RFC 5727).
> 2. The information is generated and consumed at the SIP layer by SIP
>    elements.
> 3. SIP elements besides the UAC and UAS might be interested in
>    consuming (beyond applying policy) the information.
> 4. There are specific privacy issues involved with the information
>    being transported (e.g., geolocation or emergency-related
>    information).
>=20
> User data of the mechanism will be clearly marked with the=20
> application,
> encoding, semantics, and content type, allowing policy to be=20
> applied by
> UAs.  The working group will define the information that each
> application must specify to utilize the mechanism. This type of
> application-specific information will be specified in standards-track
> documents.
> =20
> One important application of this mechanism is interworking with the
> ISDN User to User Information Service.  This application defined by
> ITU-T Q.931 is extensively deployed in the PSTN today supporting such
> applications as contact centers, call centers, and automatic call
> distributors (ACDs).  A major barrier to the movement of these
> applications to SIP is the lack of a standard mechanism to transport
> this information in SIP.  For interworking with ISDN, minimal
> information about the content of the UUI is available to the PSTN-SIP
> gateways.  In this case only, the content will just indicate ISDN UUI
> Service 1 interworking rather than the actual content.
> =20
> Call control UUI is user information conveyed between user=20
> agents during
> call control operations.  As a result, the information must=20
> be conveyed
> with the INVITE transaction, and must survive proxy retargeting,
> redirection, and transfers.  The mechanism must utilize a=20
> minimum of SIP
> extensions since it will need to be supported by many simple SIP user
> agents such as PSTN gateways.  The mechanism must interwork with the
> existing ISDN service but should also be extensible for use by other
> applications and non-ISDN protocols.
>=20
> Even though interworking with the PSTN is an important=20
> requirement, call
> control UUI can be exchanged between native SIP clients that=20
> do not have
> any ISUP support. Therefore, existing SIP-T encapsulation-based
> approaches defined in RFC3372 do not meet the requirements to=20
> transport
> this type of information.
>=20
> Mechanisms based on the SIP INFO method, RFC2976, will not be=20
> considered
> by the working group since the UUI contents carry information=20
> that must
> be conveyed during session setup at the user agent - the information
> must be conveyed with the INVITE transaction.
> The information must be passed with the session setup request=20
> (INVITE),
> responses to that INVITE, or session termination requests.
> As a result, it is not possible to use INFO in these cases.
> =20
> The group will produce:
>=20
> - A problem statement and requirements document for implementing a SIP
> call control UUI mechanism
> =20
> - A specification of the SIP extension to best meet those=20
> requirements.
> =20
> Goals and Milestones
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> =20
> Sep 10 - Problem statement and requirements document to IESG
> (Informational)
> Mar 11 - SIP call control UUI specification to IESG (PS)
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir
>=20

From dromasca@avaya.com  Wed Jun 23 06:33:22 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A19E28C11F; Wed, 23 Jun 2010 06:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.882
X-Spam-Level: 
X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=0.717,  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 npwTKQDKMQ9e; Wed, 23 Jun 2010 06:33:20 -0700 (PDT)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 80E2A28C131; Wed, 23 Jun 2010 06:32:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="21987362"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 23 Jun 2010 09:32:49 -0400
X-IronPort-AV: E=Sophos;i="4.53,466,1272859200"; d="scan'208";a="485762311"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Jun 2010 09:32:48 -0400
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: Wed, 23 Jun 2010 15:32:46 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F3425@307622ANEX5.global.avaya.com>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A649EFEEE@DEMUEXC006.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
Thread-Index: AcsSLG1A83zuJOvPQq6o9Y1ihb30owAjr3kQAABByQAABurm4A==
References: <EDC652A26FB23C4EB6384A4584434A04022B997B@307622ANEX5.global.avaya.com> <80A0822C5E9A4440A5117C2F4CD36A649EFEEE@DEMUEXC006.nsn-intra.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>, <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jun 2010 13:33:22 -0000

This is the mode of work that is being used by RAI for the last year or
so, and this is the result of their previous experience with SIPPING,
which was running in parallel a large number of items and many of them
were going nowhere. Now they use DISPATCH to approve and charter new
items and they create WG's to solve defined sets of problems, in some
cases smaller than the typical WG goals.=20

Dan
=20

> -----Original Message-----
> From: Ersue, Mehmet (NSN - DE/Munich) [mailto:mehmet.ersue@nsn.com]=20
> Sent: Wednesday, June 23, 2010 4:22 PM
> To: Romascanu, Dan (Dan); aaa-doctors@ietf.org; MIB Doctors=20
> (E-mail); dns-dir@ietf.org; ops-dir@ietf.org
> Subject: RE: [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
>=20
>=20
> Hi,
>=20
> > The group will produce:
> > - A problem statement and requirements document for=20
> implementing a SIP=20
> > call control UUI mechanism
> > - A specification of the SIP extension to best meet those=20
> > requirements.
>=20
> It might be an old issue and already discussed earlier but I=20
> still have some problems to understand why a workgroup is=20
> necessary for such a (more or less) small issue?
>=20
> I think a RAI area WG is still interesting for issues without=20
> a home in existing RAI area workgroups.=20
>=20
> Cheers,
> Mehmet
>=20
> =20
>=20
> > -----Original Message-----
> > From: ops-dir-bounces@ietf.org
> > [mailto:ops-dir-bounces@ietf.org] On Behalf Of ext Romascanu, Dan=20
> > (Dan)
> > Sent: Wednesday, June 23, 2010 12:05 PM
> > To: aaa-doctors@ietf.org; MIB Doctors (E-mail); dns-dir@ietf.org;=20
> > ops-dir@ietf.org
> > Subject: [OPS-DIR] FW: WG Review: Call Control UUI for SIP (cuss)
> >=20
> > Please find below the proposed charter of the CUSS WG in=20
> RAI. Please=20
> > send your questions, comments and concerns before 6/29 COB.
> >=20
> > Thanks and Regards,
> >=20
> > Dan
> >=20
> >=20
> > -----Original Message-----
> > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]=20
> On Behalf=20
> > Of IESG Secretary
> > Sent: Tuesday, June 22, 2010 8:00 PM
> > To: new-work@ietf.org
> > Subject: WG Review: Call Control UUI for SIP (cuss)
> >=20
> > A new IETF working group has been proposed in the Real-time=20
> > Applications and Infrastructure Area.  The IESG has not made any=20
> > determination as yet.
> > The following draft charter was submitted, and is provided for=20
> > informational purposes only. Please send your comments to the IESG=20
> > mailing list (iesg@ietf.org) by Tuesday, June 29, 2010.
> >=20
> > Call Control UUI for SIP  (cuss)
> > --------------------------------------------------
> > Current Status: Proposed Working Group
> >=20
> > Last modified: 2010-06-21
> >=20
> > Chair(s):
> >   TBD
> >=20
> > Real-time Applications and Infrastructure Area Director(s):
> >   Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
> >   Robert Sparks <rjsparks@nostrum.com>
> >=20
> > Real-time Applications and Infrastructure Area Advisor:
> >   Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
> >=20
> > Mailing Lists: TBD
> >=20
> > Description of Working Group:
> >=20
> > The Call Control UUI for SIP (CUSS) working group is chartered to=20
> > define a Session Initiation Protocol (SIP) mechanism for=20
> transporting=20
> > call-control related user-to-user information (UUI) between User=20
> > Agents.
> > =20
> > The mechanism developed in this working group is applicable in the=20
> > following situations:
> >=20
> > 1. The information is generated and consumed by an application using
> >    SIP during session setup but the application is not necessarily
> >    even SIP aware.
> > 2. The behavior of SIP entities that support it is not significantly
> >    changed (as discussed in Section 4 of RFC 5727).
> > 3. Generally only the User Agent Client (UAC) and User Agent Server
> >    (UAS) are interested in the information.
> > 4. The information is expected to survive retargeting, redirection,
> >    and transfers.
> > 5. SIP elements may need to apply policy about passing and screening
> >    the information.
> > 6. Multi-vendor interoperability is important.
> >=20
> > This mechanism is not applicable in the following situations:
> >=20
> > 1. The behavior of SIP entities that support it is significantly
> >    changed (as discussed in Section 4 of RFC 5727).
> > 2. The information is generated and consumed at the SIP layer by SIP
> >    elements.
> > 3. SIP elements besides the UAC and UAS might be interested in
> >    consuming (beyond applying policy) the information.
> > 4. There are specific privacy issues involved with the information
> >    being transported (e.g., geolocation or emergency-related
> >    information).
> >=20
> > User data of the mechanism will be clearly marked with the=20
> > application, encoding, semantics, and content type,=20
> allowing policy to=20
> > be applied by UAs.  The working group will define the=20
> information that=20
> > each application must specify to utilize the mechanism.=20
> This type of=20
> > application-specific information will be specified in=20
> standards-track=20
> > documents.
> > =20
> > One important application of this mechanism is interworking=20
> with the=20
> > ISDN User to User Information Service.  This application defined by=20
> > ITU-T Q.931 is extensively deployed in the PSTN today=20
> supporting such=20
> > applications as contact centers, call centers, and automatic call=20
> > distributors (ACDs).  A major barrier to the movement of these=20
> > applications to SIP is the lack of a standard mechanism to=20
> transport=20
> > this information in SIP.  For interworking with ISDN, minimal=20
> > information about the content of the UUI is available to=20
> the PSTN-SIP=20
> > gateways.  In this case only, the content will just=20
> indicate ISDN UUI=20
> > Service 1 interworking rather than the actual content.
> > =20
> > Call control UUI is user information conveyed between user agents=20
> > during call control operations.  As a result, the=20
> information must be=20
> > conveyed with the INVITE transaction, and must survive proxy=20
> > retargeting, redirection, and transfers.  The mechanism=20
> must utilize a=20
> > minimum of SIP extensions since it will need to be=20
> supported by many=20
> > simple SIP user agents such as PSTN gateways.  The mechanism must=20
> > interwork with the existing ISDN service but should also be=20
> extensible=20
> > for use by other applications and non-ISDN protocols.
> >=20
> > Even though interworking with the PSTN is an important requirement,=20
> > call control UUI can be exchanged between native SIP=20
> clients that do=20
> > not have any ISUP support. Therefore, existing SIP-T=20
> > encapsulation-based approaches defined in RFC3372 do not meet the=20
> > requirements to transport this type of information.
> >=20
> > Mechanisms based on the SIP INFO method, RFC2976, will not be=20
> > considered by the working group since the UUI contents carry=20
> > information that must be conveyed during session setup at the user=20
> > agent - the information must be conveyed with the INVITE=20
> transaction.
> > The information must be passed with the session setup request=20
> > (INVITE), responses to that INVITE, or session termination requests.
> > As a result, it is not possible to use INFO in these cases.
> > =20
> > The group will produce:
> >=20
> > - A problem statement and requirements document for=20
> implementing a SIP=20
> > call control UUI mechanism
> > =20
> > - A specification of the SIP extension to best meet those=20
> > requirements.
> > =20
> > Goals and Milestones
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > =20
> > Sep 10 - Problem statement and requirements document to IESG
> > (Informational)
> > Mar 11 - SIP call control UUI specification to IESG (PS)=20
> > _______________________________________________
> > OPS-DIR mailing list
> > OPS-DIR@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-dir
> >=20
>=20

From dromasca@avaya.com  Fri Jun 25 00:47:30 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6DA3A6915; Fri, 25 Jun 2010 00:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.885
X-Spam-Level: 
X-Spam-Status: No, score=-1.885 tagged_above=-999 required=5 tests=[AWL=0.714,  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 elMabxsFyAUV; Fri, 25 Jun 2010 00:47:28 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id D698D3A68AD; Fri, 25 Jun 2010 00:47:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,480,1272859200"; d="scan'208";a="195173279"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jun 2010 03:47:34 -0400
X-IronPort-AV: E=Sophos;i="4.53,480,1272859200"; d="scan'208";a="475832338"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 25 Jun 2010 03:47:33 -0400
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: Fri, 25 Jun 2010 09:47:29 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F37C1@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for the July 1, 2010 IESG Teleconference 
Thread-Index: AcsT67sAyQuS/gNVTti7wXiIruURtwATpBBg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <dns-dir@ietf.org>, <ops-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for the July 1, 2010 IESG Teleconference
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jun 2010 07:47:30 -0000

=20
Please find below the preliminary agenda of the 7/1 IESG teleconference.
Please let me know if there are any questions, issues, or concerns
related to the documents and WG charters brought up for approval.=20

Thanks and Regards,

Dan


2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items

  o draft-ietf-behave-turn-ipv6-09
    Traversal Using Relays around NAT (TURN) Extension for IPv6
    (Proposed Standard)
    Note: Dan Wing (dwing@cisco.com) is the document shepherd.
    Token: David Harrington

  o draft-ietf-behave-turn-tcp-06
    Traversal Using Relays around NAT (TURN) Extensions for TCP
    Allocations (Proposed Standard)
    Note: Dan Wing, dwing@cisco.com is the document shepherd.
    Token: David Harrington

  o draft-ietf-sipcore-invfix-01
    Correct transaction handling for 2xx responses to Session Initiation
    Protocol (SIP) INVITE requests (Proposed Standard)
    Note: Adam Roach (adam@nostrum.com) is the document shepherd.
    Token: Gonzalo Camarillo

  o draft-ietf-6man-dns-options-bis-03
    IPv6 Router Advertisement Options for DNS Configuration RFC 5006-bis
    (Proposed Standard)
    Note: Bob Hinden (bob.hinden@gmail.com) is the document shepherd.
    Token: Jari Arkko

2.1.2 Returning Items

  o draft-ietf-avt-seed-srtp-14
    The SEED Cipher Algorithm and Its Use with the Secure Real-time
    Transport Protocol (SRTP) (Proposed Standard)
    Token: Robert Sparks

2.2 Individual Submissions
2.2.1 New Items

  NONE

2.2.2 Returning Items

  NONE

3. Document Actions
3.1 WG Submissions
3.1.1 New Items

  o draft-ietf-nsis-applicability-mobility-signaling-18
    NSIS Protocols operation in Mobile Environments (Informational)
    Note: The document shepherd is Martin Stiemerling
    (martin.stiemerling@neclab.eu).
    Token: Lars Eggert
    Was deferred by Tim Polk on 2010-06-15

  o draft-ietf-mpls-tp-survive-fwk-06
    Multiprotocol Label Switching Transport Profile Survivability
    Framework (Informational)
    Note: Loa Andersson (loa@pi.nu) is the Document Shepherd.
    Token: Stewart Bryant

  o draft-ietf-csi-proxy-send-04
    Secure Proxy ND Support for SEND (Experimental)
    Note: Marcelo Bagnulo (marcelo@it.uc3m.es) is the document shepherd.
    Token: Ralph Droms

  o draft-ietf-ipsecme-ipsec-ha-07
    IPsec Cluster Problem Statement (Informational)
    Note: Yaron Sheffer (yaronf.ietf@gmail.com) is the document
    shepherd.
    Token: Sean Turner

  o draft-ietf-nsis-tunnel-11
    NSIS Operation Over IP Tunnels (Experimental)
    Note: The document shepherd is Jukka Manner (jukka.manner@tkk.fi).
    Token: Lars Eggert

3.1.2 Returning Items

  NONE

3.2 Individual Submissions Via AD
3.2.1 New Items

  o draft-hoffman-tls-master-secret-input-01
    Additional Master Secret Inputs for TLS (Experimental)
    Note: There is no document shepherd.
    Token: Sean Turner

  o draft-c1222-transport-over-ip-03
    ANSI C12.22, IEEE 1703 and MC12.22 Transport Over IP (Informational)
    Note: Fred Baker <fred@cisco.com> is the Document Shepherd.
    Token: Ralph Droms

3.2.2 Returning Items

  NONE

3.3 Independent Submissions Via RFC Editor
3.3.1 New Items

  NONE

3.3.2 Returning Items

  o draft-keromytis-tls-authz-keynote-06
    Transport Layer Security (TLS) Authorization Using KeyNote
    (Informational)
    Token: Tim Polk

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review

  NONE

4.1.2 Proposed for Approval

  o Call Control UUI for SIP (cuss)
    Token: Gonzalo

  o Sip ALerting for User Devices (salud)
    Token: Gonzalo

  o Loosely-coupled SIP Devices (lsd)
    Token: Gonzalo

4.2 WG Rechartering
4.2.1 Under Evaluation for IETF Review

  NONE

4.2.2 Proposed for Approval

  NONE




From dromasca@avaya.com  Tue Jun 29 04:25:47 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 702E63A69B0 for <aaa-doctors@core3.amsl.com>; Tue, 29 Jun 2010 04:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level: 
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[AWL=0.644,  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 R1RAXoKln9an for <aaa-doctors@core3.amsl.com>; Tue, 29 Jun 2010 04:25:46 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id A91B03A68DA for <aaa-doctors@ietf.org>; Tue, 29 Jun 2010 04:25:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,503,1272859200"; d="scan'208";a="225434545"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 29 Jun 2010 07:25:57 -0400
X-IronPort-AV: E=Sophos;i="4.53,503,1272859200"; d="scan'208";a="476892381"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jun 2010 07:25:56 -0400
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, 29 Jun 2010 13:25:55 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04022F3E75@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AAA-Doctors lunch meeting in Maastricht
Thread-Index: AcsXfZcK4ZXQpry9QzWhLhK677XXDg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] AAA-Doctors lunch meeting in Maastricht
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2010 11:25:47 -0000

We plan for our regular Thursday lunch meeting to be hold in Maastricht
on Thursday July 29, from 11:30 to 13:00. Please book this slot on your
schedules and let me know about items that you would like to be included
in the agenda. The room is TBD and will be announced prior to the
meeting.=20

Thanks and Regards,

Dan


