
From dromasca@avaya.com  Fri Oct  2 01:36:21 2009
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 C714E3A68BB; Fri,  2 Oct 2009 01:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  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 DLulrQ3FbMOe; Fri,  2 Oct 2009 01:36:18 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 358223A67F2; Fri,  2 Oct 2009 01:36:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,493,1249272000"; d="scan'208";a="175397168"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 02 Oct 2009 04:37:43 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Oct 2009 04:37:42 -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, 2 Oct 2009 10:37:21 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401A85847@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for October 8, 2009 Telechat 
thread-index: AcpC41mdtryjRaDpS8y5xQrmgXJWmwAVwpDw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <dns-dir@ietf.org>, <aaa-doctors@ietf.org>, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for October 8, 2009 Telechat
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, 02 Oct 2009 08:36:21 -0000

 Please find below the preliminary agenda of the IESG telechat on 10/8.
Please send your comments, questions and concerns before 10/7 COB.=20

Thanks and Regards,

Dan


-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-ipsecme-ikev2-resumption-08.txt
    IKEv2 Session Resumption (Proposed Standard) - 1 of 7=20
    Note: Paul Hoffman (paul.hoffman@vpnc.org) is the document shepherd.

    Token: Pasi Eronen
  o draft-ietf-mipshop-pfmipv6-09.txt
    Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 2 of 7=20
    Note: Vijay Devarapalli (vijay@wichorus.com) is the document
shepherd.
=20
    Token: Jari Arkko
  o draft-ietf-pmol-sip-perf-metrics-04.txt
    SIP End-to-End Performance Metrics (Proposed Standard) - 3 of 7=20
    Note: Vijay Gurbani is the PROTO-shepherd=20
    Token: Dan Romascanu
  o draft-ietf-dime-diameter-cmd-iana-01.txt
    Updated IANA Considerations for Diameter Command Code Allocations
(Proposed=20
    Standard) - 4 of 7=20
    Note: Victor Fajardo (vfajardo@research.telcordia.com) is the
document
=20
    shepherd.=20
    Token: Ron Bonica
  o draft-ietf-yam-rfc1652bis-pre-evaluation-00.txt
    Preliminary Evaluation of RFC 1652 for Advancement to Full Standard=20
    (Standard) - 5 of 7=20
    Note: This draft contains the list of changes planned by the YAM WG
to
move=20
    RFC 1652 to Full Standard. There is no intention to publish this
document=20
    as an RFC, so IESG should vote on this document as if RFC 1652 is
advancing=20
    to Full Standard.. S Moonesamy <sm+ietf@elandsys.com> has agreed
to=20
    serve as the document shepherd, but note that there is no
shepherding

    write-up for this document.=20
    Token: Alexey Melnikov
  o draft-ietf-mpls-tp-oam-requirements-03.txt
    Requirements for OAM in MPLS Transport Networks (Proposed Standard)
-
6 of=20
    7=20
    Note: Loa Andersson (loa@pi.nu) is the document shepherd.. Note that
this=20
    document is a requirement document, for reasons that have. to do
with

    referencibility by ITU-T we have opted to put it on the standards
track.=20
    The same decision applies to all MPLS-TP requirement. documents.=20
    Token: Adrian Farrel
  o draft-ietf-mpls-tp-nm-req-05.txt
    MPLS TP Network Management Requirements (Proposed Standard) - 7 of 7

    Note: Loa Andersson (loa@pi.nu) is the Document Shepherd.. Note that
this=20
    document is a requirement document. For reasons that. have to do
with
how=20
    the ITU-T can reference RFCs we have opted to put. it on the
Standards
=20
    Track.=20
    Token: Adrian Farrel

2.1.2 Returning Item
  o draft-ietf-tcpm-tcpsecure-12.txt
    Improving TCP's Robustness to Blind In-Window Attacks (Proposed
Standard) -=20
    1 of 2=20
    Note: IESG: Please read the Document Shepherd Writeup, we need to
discuss=20
    the "Updates: 793" issue.=20
    Token: Lars Eggert
  o draft-ietf-mboned-lightweight-igmpv3-mldv2-05.txt
    Lightweight IGMPv3 and MLDv2 Protocols (BCP) - 2 of 2=20
    Token: Ron Bonica


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-simple-interdomain-scaling-analysis-08.txt
    Presence Interdomain Scaling Analysis for SIP/SIMPLE (Informational)
-
1 of=20
    10=20
    Note: Ben Campbell is document shepherd=20
    Token: Robert Sparks
  o draft-ietf-krb-wg-cross-problem-statement-04.txt
    Problem statement on the cross-realm operation of Kerberos
(Informational)=20
    - 2 of 10=20
    Token: Tim Polk
  o draft-ietf-speermint-requirements-07.txt
    SPEERMINT Requirements for SIP-based Session Peering (Informational)
-
3 of=20
    10=20
    Token: Cullen Jennings
  o draft-ietf-speermint-voip-consolidated-usecases-14.txt
    VoIP SIP Peering Use Cases (Informational) - 4 of 10=20
    Token: Cullen Jennings
  o draft-ietf-roll-home-routing-reqs-08.txt
    Home Automation Routing Requirements in Low Power and Lossy Networks

    (Informational) - 5 of 10=20
    Note: JP Vasseur (jvasseur@cisco.com) is the document shepherd=20
    Token: Adrian Farrel
  o draft-ietf-msec-tesla-for-alc-norm-08.txt
    Use of TESLA in the ALC and NORM Protocols (Experimental) - 6 of 10=20
    Token: Tim Polk
  o draft-ietf-rtgwg-lf-conv-frmwk-06.txt
    A Framework for Loop-free Convergence (Informational) - 7 of 10=20
    Token: Ross Callon
  o draft-ietf-rtgwg-ipfrr-framework-12.txt
    IP Fast Reroute Framework (Informational) - 8 of 10=20
    Token: Ross Callon
  o draft-ietf-ipsecme-ikev2-ipv6-config-02.txt
    IPv6 Configuration in IKEv2 (Experimental) - 9 of 10=20
    Note: Paul Hoffman (paul.hoffman@vpnc.org) is the document shepherd.

    Token: Tim Polk
  o draft-ietf-eai-downgraded-display-02.txt
    Displaying Downgraded Messages for Email Address
Internationalization

    (Experimental) - 10 of 10=20
    Note: Harald Alvestrand agreed to shepherd the document=20
    Token: Alexey Melnikov

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-harkins-emu-eap-pwd-08.txt
    EAP Authentication Using Only A Password (Informational) - 1 of 2=20
    Token: Russ Housley
  o draft-iana-ipv4-examples-02.txt
    IPv4 Address Blocks Reserved for Documentation (Informational) - 2
of
2=20
    Token: Russ Housley

3.2.2 Returning Item
NONE
3.3 Independent Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.

	The document shepherd must propose one of these responses in
	the Data Tracker note and supply complete text in the IESG
	Note portion of the write-up. The Area Director ballot positions
	indicate consensus with the response proposed by the
	document shepherd.

	Other matters may be recorded in comments, and the comments will
	be passed on to the RFC Editor as community review of the
document.


3.3.1 New Item
  o draft-keromytis-keynote-x509-02.txt
    X.509 Key and Signature Encoding for the KeyNote Trust Management
System=20
    (Informational) - 1 of 1=20
    Token: Tim Polk

3.3.2 Returning Item
  o draft-templin-ranger-07.txt
    Routing and Addressing in Next-Generation EnteRprises (RANGER)=20
    (Informational) - 1 of 2=20
    Token: Jari Arkko
  o draft-irtf-mobopts-mmcastv6-ps-08.txt
    Multicast Mobility in MIPv6: Problem Statement and Brief Survey=20
    (Informational) - 2 of 2=20
    Note: Rajeev Koodli (rajeev.koodli@gmail.com) is the document
shepherd.=20
    Token: Jari Arkko

3.3.3 For Action
  o draft-levy-sip-diversion-10.txt
    Diversion Indication in SIP (Historic) - 1 of 1=20
    Token: Robert Sparks

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o Multipath TCP (mptcp) - 1 of 1
    Token: Magnus Westerlund
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2
    Token: Magnus Westerlund
  o Access Node Control Protocol (ancp) - 2 of 2
    Token: Ralph Droms



From dromasca@avaya.com  Tue Oct 27 08:51:24 2009
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 00AB03A697E for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 08:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  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 X-vVmE6VjdkL for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 08:51:23 -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 B3A4828C1A7 for <aaa-doctors@ietf.org>; Tue, 27 Oct 2009 08:51:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,633,1249272000"; d="scan'208";a="161497050"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 27 Oct 2009 11:51:35 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 27 Oct 2009 11:51:34 -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, 27 Oct 2009 16:51:30 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AAA Doctors team meeting in Hiroshima? 
Thread-Index: AcpXHVmtoMPycYWLSYy3huOmS0fudA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
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, 27 Oct 2009 15:51:24 -0000

It looks like only a handful of the AAA-Doctors team will attend the
meeting in Hiroshima. I have booked the IESG breakout room for Tuesday
11/10 at lunch time but I need confirmation about how many participants
will be in Hiroshima before we decide to hold the meeting.=20

Thanks and Regards,

Dan

From lionel.morand@orange-ftgroup.com  Tue Oct 27 08:53:25 2009
Return-Path: <lionel.morand@orange-ftgroup.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 8FC703A67CF for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 08:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 JxTK5mcD-W51 for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 08:53:24 -0700 (PDT)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 71B6D3A6822 for <aaa-doctors@ietf.org>; Tue, 27 Oct 2009 08:53:24 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 27 Oct 2009 16:53:36 +0100
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: Tue, 27 Oct 2009 16:53:36 +0100
Message-ID: <D109C8C97C15294495117745780657AE0C0CE324@ftrdmel1>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
Thread-Index: AcpXHVmtoMPycYWLSYy3huOmS0fudAAAB1Mw
References: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
From: <lionel.morand@orange-ftgroup.com>
To: <dromasca@avaya.com>, <aaa-doctors@ietf.org>
X-OriginalArrivalTime: 27 Oct 2009 15:53:36.0868 (UTC) FILETIME=[A513B240:01CA571D]
Subject: Re: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
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, 27 Oct 2009 15:53:25 -0000

Hi Dan,

Unfortunately, I will not be present this time, as the 3GPP CT meeting =
is the same week.

BR,

Lionel =20

> -----Message d'origine-----
> De : aaa-doctors-bounces@ietf.org=20
> [mailto:aaa-doctors-bounces@ietf.org] De la part de=20
> Romascanu, Dan (Dan)
> Envoy=E9 : mardi 27 octobre 2009 16:52
> =C0 : aaa-doctors@ietf.org
> Objet : [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
>=20
> It looks like only a handful of the AAA-Doctors team will=20
> attend the meeting in Hiroshima. I have booked the IESG=20
> breakout room for Tuesday 11/10 at lunch time but I need=20
> confirmation about how many participants will be in Hiroshima=20
> before we decide to hold the meeting.=20
>=20
> Thanks and Regards,
>=20
> Dan
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors
>=20

From jouni.nospam@gmail.com  Tue Oct 27 09:09:47 2009
Return-Path: <jouni.nospam@gmail.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 88C653A6839 for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 09:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPNIEZzOVP5Q for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 09:09:46 -0700 (PDT)
Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by core3.amsl.com (Postfix) with ESMTP id B3A883A6A32 for <aaa-doctors@ietf.org>; Tue, 27 Oct 2009 09:09:27 -0700 (PDT)
Received: from a88-114-70-12.elisa-laajakaista.fi (a88-114-70-12.elisa-laajakaista.fi [88.114.70.12]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 1DFA2139597; Tue, 27 Oct 2009 18:09:37 +0200 (EET)
References: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Message-Id: <AF96D431-F2EB-432A-8652-72B0458E5FE7@gmail.com>
Content-Transfer-Encoding: 7bit
From: jouni <jouni.nospam@gmail.com>
Date: Tue, 27 Oct 2009 18:09:37 +0200
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1076)
Cc: aaa-doctors@ietf.org
Subject: Re: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
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, 27 Oct 2009 16:09:47 -0000

I'll show up.

Cheers,	
	Jouni

On Oct 27, 2009, at 5:51 PM, Romascanu, Dan (Dan) wrote:

> It looks like only a handful of the AAA-Doctors team will attend the
> meeting in Hiroshima. I have booked the IESG breakout room for Tuesday
> 11/10 at lunch time but I need confirmation about how many  
> participants
> will be in Hiroshima before we decide to hold the meeting.
>
> Thanks and Regards,
>
> Dan
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors


From aland@freeradius.org  Tue Oct 27 13:19:06 2009
Return-Path: <aland@freeradius.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 E9B2028C175 for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 13:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619]
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 B67acZORZXLN for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 13:19:06 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id EE49128C14C for <aaa-doctors@ietf.org>; Tue, 27 Oct 2009 13:19:05 -0700 (PDT)
Received: from Thor.local (unknown [74.198.12.3]) by liberty.deployingradius.com (Postfix) with ESMTPSA id D0BD5123432F;  Tue, 27 Oct 2009 21:19:18 +0100 (CET)
Message-ID: <4AE755C3.8060702@freeradius.org>
Date: Tue, 27 Oct 2009 16:19:15 -0400
From: Alan T DeKok <aland@freeradius.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: aaa-doctors@ietf.org
Subject: Re: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: aland@freeradius.org
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, 27 Oct 2009 20:19:07 -0000

Romascanu, Dan (Dan) wrote:
> It looks like only a handful of the AAA-Doctors team will attend the
> meeting in Hiroshima. I have booked the IESG breakout room for Tuesday
> 11/10 at lunch time but I need confirmation about how many participants
> will be in Hiroshima before we decide to hold the meeting. 

  I will not attend.

  Alan DeKok.


From glenzorn@comcast.net  Tue Oct 27 17:48:11 2009
Return-Path: <glenzorn@comcast.net>
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 E761B28C173 for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 17:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level: 
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[AWL=0.695,  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 m9NW65E6ISl0 for <aaa-doctors@core3.amsl.com>; Tue, 27 Oct 2009 17:48:11 -0700 (PDT)
Received: from QMTA14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by core3.amsl.com (Postfix) with ESMTP id 4754228C168 for <aaa-doctors@ietf.org>; Tue, 27 Oct 2009 17:48:11 -0700 (PDT)
Received: from OMTA07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by QMTA14.emeryville.ca.mail.comcast.net with comcast id xrDN1c0011GXsucAE0oQXm; Wed, 28 Oct 2009 00:48:24 +0000
Received: from gwzPC ([124.120.224.88]) by OMTA07.emeryville.ca.mail.comcast.net with comcast id y0oA1c00K1v3G5G8T0oEGK; Wed, 28 Oct 2009 00:48:22 +0000
From: "Glen Zorn" <glenzorn@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401B4C795@307622ANEX5.global.avaya.com>
Date: Wed, 28 Oct 2009 07:48:05 +0700
Message-ID: <00b401ca5768$5731d7a0$059586e0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcpXHVmtoMPycYWLSYy3huOmS0fudAASoFlg
Content-Language: en-us
Cc: aaa-doctors@ietf.org
Subject: Re: [AAA-DOCTORS] AAA Doctors team meeting in Hiroshima?
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, 28 Oct 2009 00:48:12 -0000

Dan Romascanu [mailto://dromasca@avaya.com] writes:

> It looks like only a handful of the AAA-Doctors team will attend the
> meeting in Hiroshima. I have booked the IESG breakout room for Tuesday
> 11/10 at lunch time but I need confirmation about how many participants
> will be in Hiroshima before we decide to hold the meeting.

Tuesday conflicts with the Security Area lunch.

> 
> Thanks and Regards,
> 
> Dan
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors


From dromasca@avaya.com  Wed Oct 28 03:23:53 2009
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 763883A67B6; Wed, 28 Oct 2009 03:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level: 
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[AWL=0.168,  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 TuSfkD9T546d; Wed, 28 Oct 2009 03:23:52 -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 51E893A67E4; Wed, 28 Oct 2009 03:23:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,639,1249272000"; d="scan'208";a="188387272"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Oct 2009 06:24:02 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 28 Oct 2009 06:24:02 -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, 28 Oct 2009 11:24:02 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401B4C994@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Internet Area Working Group (intarea) 
Thread-Index: AcpXQCyqEqEa1DuBTXyoIcEMmOi3eQAeIoPw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <dns-dir@ietf.org>, <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Internet Area Working Group (intarea)
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, 28 Oct 2009 10:23:53 -0000

=20

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Tuesday, October 27, 2009 10:00 PM
To: new-work@ietf.org
Subject: WG Review: Internet Area Working Group (intarea)=20

A new IETF working group has been proposed in the Internet 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,
November 3, 2009.

Internet Area Working Group (intarea)
---------------------------------------------------
Current Status: Proposed Working Group
Last modified: 2009-10-22

Chairs:
TBD

Internet Area (int) Directors:
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms@cisco.com>

Mailing Lists:
General Discussion: int-area@ietf.org
Subscribe online at: https://www.ietf.org/mailman/listinfo/int-area

Description of Working Group:

The Internet Area Working Group (INTAREA WG) acts primarily as a forum
for  discussing far-ranging topics that affect the entire area. Such
topics include, for instance, address space issues, basic IP layer
functionality, and architectural questions. The group also serves as a
forum to distribute information about ongoing activities in the area,
create a shared understanding of the challenges and goals for the area,
and to enable coordination.

The Internet Area receives occasional proposals for the development and
publication of RFCs that are not in scope of an existing working group
and do not justify the formation of a new working group. The INTAREA WG
has a secondary role to serve as the forum for developing such work
items in the IETF. The working group milestones are updated as needed to
reflect the current work items and their associated milestones.

New  work must satisfy the following conditions:

 (1) WG consensus on the relevance for the Internet at large.

 (2) WG consensus on the suitability and projected quality of the
      proposed work item.

 (3) A core group of WG participants with sufficient energy and
      expertise to advance the work item according to the proposed
      schedule.

 (4) Commitment from the WG as a whole to provide sufficient
      and timely review of the proposed work item.

 (5) Agreement by the ADs, who, depending on the scope of the proposed
      work item, may decide that an IESG review is needed first.

Milestones:

Dec 2009  Submission of IPID document to the IESG as PS Mar 2010
Submission of tunneling issues document to the IESG as Info

From dromasca@avaya.com  Wed Oct 28 03:25:15 2009
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 80B1D3A6889; Wed, 28 Oct 2009 03:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level: 
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165,  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 vf3KtvHBoKGO; Wed, 28 Oct 2009 03:25:14 -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 2CBEA3A6875; Wed, 28 Oct 2009 03:25:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,639,1249272000"; d="scan'208";a="161579895"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 28 Oct 2009 06:25:12 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 28 Oct 2009 06:25: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, 28 Oct 2009 11:24:54 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401B4C995@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of Handover Keying (hokey) 
Thread-Index: AcpXSI4gdwuwlXVZRzCWaWO5/ULIAgAcD0kQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, <dns-dir@ietf.org>, <aaa-doctors@ietf.org>, <mib-doctors@ietf.org>, <dime@ietf.org>, <radiusext@ops.ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Recharter of Handover Keying (hokey)
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, 28 Oct 2009 10:25:15 -0000

=20

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary
Sent: Tuesday, October 27, 2009 11:00 PM
To: new-work@ietf.org
Subject: WG Review: Recharter of Handover Keying (hokey)=20

A modified charter has been submitted for the Handover Keying (hokey)
working group in the Security Area of the IETF.  The IESG has not made
any determination as yet.  The modified charter is provided below for
informational purposes only.  Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, November 3, 2009.

Handover Keying (hokey)
------------------------
Last Modified: 2009-10-19

Chair(s):

Glen Zorn <gwz@net-zen.net>
Tina Tsou (Ting ZOU) <tena@huawei.com>=20

Security Area Director(s):

Tim Polk <tim.polk@nist.gov>
Pasi Eronen <pasi.eronen@nokia.com>=20

Security Area Advisor:

Tim Polk <tim.polk@nist.gov>=20

Mailing Lists:

General Discussion: hokey@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/hokey
Archive:
http://www.ietf.org/mail-archive/web/hokey/current/maillist.html

Description of Working Group:

A mobile device has to re-authenticate each time it changes its point of
attachment to the network. When it goes through the full procedure of
authentication it creates a series of ruptures, during which the medium
cannot flow. This results in a poor user experience during handover.
However, it is possible to shorten the time it takes to re-authenticate
by reusing the key information developed during the initial
authentication.

The Handover Keying Working Group is concerned with developing
procedures for key reuse and delivery, while respecting good security
practice. The Handover Keying Working Group has already done work on
this subject, but it has not yet developed the complete set of
procedures, protocols, and changes needed for different security
environment scenarios and situations.

The solutions specified by the HOKEY WG fall into several categories,
based on timing and mechanism. The authentication and key management may
occur before handoff, when latency is much less critical. Alternatively,
authentication and key management can occur as part of the handoff,
where latency is critical. Solutions should reduce or eliminate the
number of referrals to AAA servers, and solutions should avoid
re-executing lengthy EAP method exchanges. This may be accomplished by
providing new mechanisms for cryptographic keying material in
combination with a protocol for the timely delivery of appropriate keys
to the appropriate entities. Solutions are expected to include "handover
keying," "low-latency re-authentication,"
and "pre-authentication" or "early authentication".

All solution categories are useful, each supporting different scenarios.
The HOKEY WG may provide multiple solutions, each addressing a different
scenario.

Solutions specified by the HOKEY WG must:

1) Be responsive to handover and re-authentication latency performance
objectives within a mobile wireless access network.

2) Fulfill the requirements in RFC 4962 and RFC 5247.

3) Be independent of the access-technology. Any key hierarchy topology
or protocol defined must be independent of EAP lower layers. The
protocols may require additional support from the EAP lower layers that
use it.

4) Accommodate inter-technology heterogeneous handover and roaming.

5) Not require changes to EAP methods. Any extensions defined to EAP
must not cause changes to existing EAP methods.

In specifying an access-technology-independent solution, media
independent guidelines for SDOs may also be needed to explain how the
keying material and signaling can be employed in a specific access
technology.

HOKEY WG Deliverables
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

1) A specification of Local Domain Name Discovery for ERP. Currently the
use of DHCP mechanisms to request the local domain name is unspecified.
There are other useful scenarios that need to be addressed. Lower layer
announcement for local domain name is unspecified. Ambiguity with using
initial full EAP exchange for re-authentication needs to be clarified.
Additional re-authentication scenarios, for which there is interest,
need to be addressed.

2) A specification of Early Authentication solutions. These include use
of EAP to pre-establish authenticated keying material on a target
authenticator prior to arrival of the peer.

3) A specification for a Hokey architecture Document. It includes
deployment of ERP and EAP early authentication protocol in the mobile
environment.
There are various useful scenarios that need to be addressed. This
specification and the revision of RFC5296 should be conducted in
parallel.

4) Assistance to the 802.21a group in specifying the integration of EAP
pre-authentication with IEEE 802.21a. The Hokey Working Group shall
perform tasks that are complementary to and do not duplicate work being
done in IEEE 802.21a.

6) A specification for NAS-Authenticator interaction. NAS interaction
can be used to release resources in the old NAS and achieve faster
initiation of authentication. Related work in external SDOs on
authenticator/NAS interaction for re-authentication may be taken into
consideration.

7) A revision of RFC 5296 to eliminate unnecessary references to the
home server.

8) Assistance to the radext and dime Working Groups in developing AAA
support for handoff keying.

Goals and Milestones:
Nov 2009 First draft on Local Domain Name Discovery for ERP Nov 2009
First draft on Early Authentication solutions Mar 2010 First draft on
Hokey architecture Mar 2010 First draft on NAS-Authenticator Interaction
Jul 2010 First draft on revision of RFC 5296 Mar 2011 Submit the Local
Domain Name Discovery for ERP draft to IESG Mar 2011 Submit the Early
Authentication solutions draft to IESG Jul 2011 Submit the
NAS-Authenticator Interaction draft to IESG Nov 2011 Submit the Hokey
architecture draft to IESG Nov 2011 Submit the revision of RFC 5296 to
IESG Mar 2012 Re-charter or shut down WG
