From aaa-doctors-bounces@ietf.org  Fri May  2 01:56:11 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 116873A6C03;
	Fri,  2 May 2008 01:56:11 -0700 (PDT)
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 561EF3A6C03;
	Fri,  2 May 2008 01:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.408
X-Spam-Level: 
X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=0.191, 
	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 2yarbSpOG9kY; Fri,  2 May 2008 01:56:09 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id C7C7C3A6A56;
	Fri,  2 May 2008 01:56:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,426,1204520400"; d="scan'208";a="124681863"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 02 May 2008 04:56:10 -0400
X-IronPort-AV: E=Sophos;i="4.27,426,1204520400"; d="scan'208";a="189447136"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	02 May 2008 04:56:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 10:56:07 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BBBB5E@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for May 8, 2008 Telechat 
Thread-Index: Acir3Ih6RhKjb8AOTWC3cAOQwoLLdgAVQ/tw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, "dns directorate" <dns-dir@ops.ietf.org>,
	<aaa-doctors@ietf.org>, "MIB Doctors" <mib-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for May 8,
	2008 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

Please find below the list of documents for approval by the IESG as they
show up in the preliminary agenda of the 5/8 telechat. Please let me
know if there are any comments or concerns until Tuesday 5/6 the latest.
(this is one day earlier than usual, the reason being that I will be out
of office for the second part of the next week)

Thanks and Regards,

Dan


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-iptel-tel-reg-05.txt
    The Internet Assigned Number Authority (IANA) tel Uniform Resource 
    Identifier (URI) Parameter Registry (Proposed Standard) - 1 of 11 
    Note: Jonathan Rosenberg is Proto Shepherd 
    Token: Jon Peterson
  o draft-ietf-simple-imdn-07.txt
    Instant Message Disposition Notification (Proposed Standard) - 2 of
11
 
    Token: Jon Peterson
  o draft-ietf-pim-bsr-mib-05.txt
    PIM Bootstrap Router MIB (Proposed Standard) - 3 of 11 
    Token: David Ward
  o draft-ietf-l1vpn-basic-mode-04.txt
    Layer 1 VPN Basic Mode (Proposed Standard) - 4 of 11 
    Token: David Ward
  o draft-ietf-mpls-upstream-label-05.txt
    MPLS Upstream Label Assignment and Context-Specific Label Space
(Proposed 
    Standard) - 5 of 11 
    Token: Ross Callon
  o draft-ietf-mpls-multicast-encaps-09.txt
    MPLS Multicast Encapsulations (Proposed Standard) - 6 of 11 
    Token: Ross Callon
  o draft-ietf-l1vpn-ospf-auto-discovery-05.txt
    OSPF Based Layer 1 VPN Auto-Discovery (Proposed Standard) - 7 of 11 
    Token: David Ward
  o draft-ietf-l1vpn-bgp-auto-discovery-04.txt
    BGP-based Auto-Discovery for Layer-1 VPNs (Proposed Standard) - 8 of
11 
    Token: David Ward
  o draft-ietf-mpls-ldp-interarea-03.txt
    LDP extension for Inter-Area LSP (Proposed Standard) - 9 of 11 
    Token: Ross Callon
  o draft-ietf-lemonade-convert-18.txt
    IMAP CONVERT extension (Proposed Standard) - 10 of 11 
    Note: Eric Burger is the document shepherd 
    Token: Chris Newman
  o draft-ietf-tsvwg-rsvp-user-error-spec-07.txt
    User-Defined Errors for RSVP (Proposed Standard) - 11 of 11 
    Token: Magnus Westerlund

2.1.2 Returning Item
  o draft-ietf-ospf-ospfv3-update-21.txt
    OSPF for IPv6 (Proposed Standard) - 1 of 1 
    Token: David Ward


2.2 Individual Submissions
2.2.1 New Item
  o draft-klensin-rfc2821bis-10.txt
    Simple Mail Transfer Protocol (Draft Standard) - 1 of 1 
    Token: Lisa Dusseault

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-ipfix-testing-05.txt
    Guidelines for IP Flow Information eXport (IPFIX) Testing
(Informational) - 
    1 of 2 
    Note: Nevil Brownlee is the PROTO shepherd 
    Token: Dan Romascanu
  o draft-ietf-v6ops-addcon-07.txt
    IPv6 Unicast Address Assignment Considerations (Informational) - 2
of
2 
    Token: Ron Bonica

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-vanelburg-sipping-served-user-05.txt
    The Session Initiation Protocol (SIP) P-Served-User Private-Header 
    (P-Header) (Informational) - 1 of 2 
    Token: Jon Peterson
  o draft-iijima-netconf-soap-implementation-07.txt
    Experience of implementing NETCONF over SOAP (Informational) - 2 of
2

    Token: Dan Romascanu

3.2.2 Returning Item
  o draft-wu-sava-testbed-experience-04.txt
    SAVA Testbed and Experiences to Date (Experimental) - 1 of 1 
    Token: Jari Arkko

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 Three-document ballot:  - 1 of 1
     - draft-irtf-dtnrg-ltp-09.txt
       Licklider Transmission Protocol - Specification (Experimental) 
       Note: Recommend RFC 3932 response #1: The IESG has not found any.

       conflict between this document and IETF work. 
     - draft-irtf-dtnrg-ltp-extensions-07.txt
       Licklider Transmission Protocol - Security Extensions
(Experimental) 
       Note: Recommend RFC 3932 response #1: The IESG has not found any.

       conflict between this document and IETF work. 
     - draft-irtf-dtnrg-ltp-motivation-06.txt
       Licklider Transmission Protocol - Motivation (Informational) 
       Note: Recommend RFC 3932 response #1: The IESG has not found any.

       conflict between this document and IETF work. 
    Token: Russ Housley

3.3.2 Returning Item
NONE

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Source Address Validation Improvements (savi) - 1 of 2
    Token: Jari Arkko
  o Data for Reachability of Inter/tra-NetworK SIP (drinks) - 2 of 2
    Token: Jon Peterson
4.1.2 Proposed for Approval
    NONE
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o RADIUS EXTensions (radext) - 1 of 1
    Token: Dan Romascanu
4.2.2 Proposed for Approval
    NONE

_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Sun May  4 23:38:46 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C8683A6FD0;
	Sun,  4 May 2008 23:38:46 -0700 (PDT)
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 13B193A6FC7
	for <aaa-doctors@core3.amsl.com>; Sun,  4 May 2008 23:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.399
X-Spam-Level: 
X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5
	tests=[AWL=-0.019, BAYES_00=-2.599, TVD_SPACE_RATIO=2.219]
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 zo9lRC5I+IqE for <aaa-doctors@core3.amsl.com>;
	Sun,  4 May 2008 23:38:44 -0700 (PDT)
Received: from mail.arubanetworks.com (mail.arubanetworks.com [216.31.249.253])
	by core3.amsl.com (Postfix) with SMTP id 7ABA83A6FD0
	for <aaa-doctors@ietf.org>; Sun,  4 May 2008 23:38:44 -0700 (PDT)
Received: from aruba-mx1.arubanetworks.com ([10.1.1.17]) by
	mail.arubanetworks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Sun, 4 May 2008 23:38:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 4 May 2008 23:38:40 -0700
Message-ID: <A3DA4C2546E1614D8ACC896746CDCF29012D90DE@aruba-mx1.arubanetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: test
Thread-Index: AciueqetJ0miqwFTThupi2wMh0I0kw==
From: "Glen Zorn" <gzorn@arubanetworks.com>
To: <aaa-doctors@ietf.org>
X-OriginalArrivalTime: 05 May 2008 06:38:44.0225 (UTC)
	FILETIME=[AA0C8710:01C8AE7A]
Subject: [AAA-DOCTORS] test
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org


_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Tue May 13 12:08:02 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F8F13A6952;
	Tue, 13 May 2008 12:08:02 -0700 (PDT)
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 44A553A693F;
	Tue, 13 May 2008 12:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level: 
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.103, 
	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 COMeHceft6BO; Tue, 13 May 2008 12:07:57 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id EBA3A3A6995;
	Tue, 13 May 2008 12:07:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,480,1204520400"; d="scan'208";a="126423977"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 13 May 2008 15:06:05 -0400
X-IronPort-AV: E=Sophos;i="4.27,480,1204520400"; d="scan'208";a="194577830"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	13 May 2008 15:06:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 13 May 2008 21:06:12 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BF9BA1@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Source Address Validation Improvements (SAVI) 
Thread-Index: Aci1K8dW4yxk8BkwTqKv2NazjaEkKwAAIUrA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>, "opsec wg mailing list" <opsec@ietf.org>,
	"dns directorate" <dns-dir@ops.ietf.org>, <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Source Address Validation Improvements
	(SAVI)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

 

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of IESG Secretary
Sent: Tuesday, May 13, 2008 10:00 PM
To: ietf-announce@ietf.org
Cc: sava@nrc.tsinghua.edu.cn
Subject: WG Review: Source Address Validation Improvements (SAVI) 

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 May 20,
2008.

Source Address Validation Improvements (SAVI)
---------------------------------------------------
Current Status: Proposed Working Group

Last modified: 2008-05-09

Co-chairs
TBD

Internet Area Directors:
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
General Discussion: sava@nrc.tsinghua.edu.cn To Subscribe:
http://mail.nrc.tsinghua.edu.cn/cgi-bin/mailman/listinfo/sava
Mailing List Archive: http://mail.nrc.tsinghua.edu.cn/pipermail/sava/

While ingress filtering [RFC 2827, BCP 38] provides a way to validate IP
source addresses at an aggregated level, there is not yet a standardized
mechanism for IP source address validation at a finer granularity.
Having a finer granularity would be helpful in a number of situations,
including filtering traffic from customer interfaces implemented as
ports in a layer 3 aware bridge or a router, general improvements in
filtering accuracy in enterprise networks, etc.
Depending on the situation, there may be a requirement for blocking
spoofed packets or merely logging packets that appear to be spoofed.

Partial solutions exist to prevent nodes from spoofing the IP source
address of another node in the same IP link (e.g., the "IP source
guard"), but are proprietary. The purpose of the proposed "Source
Address Validation Improvements" working group is to standardize
mechanisms that prevent nodes attached to the same IP link from spoofing
each other's IP addresses.

The scope of the WG is as follows:

- The working group considers only solutions implemented on systems
located on the same IP link as a to-be-verified node. The goal of the
working group is the LAN environment and solutions running in routers or
layer 3 aware Ethernet bridges.

- Both IPv4 and IPv6 need to be covered.

- The first goal of the working group is on unicast traffic, but using
the same mechanisms to police multicast traffic is also within the
scope.

- All address assignment mechanisms need to be supported, including
stateless, stateful, and manual configuration; as well as privacy and
cryptographically generated addresses.

- Solutions are preferably based on observing user traffic, or on
observing or using existing signaling protocols. Examples of protocols
that can be useful to observe/use are ARP, Neighbor Discovery, DHCP, and
DHCP Prefix Delegation protocols. Observing addresses in IP headers can
also be useful. The gathered information is used to determine what IP
source addresses in packets are appropriate. Where automatic operation
is impossible or would lead to sub-optimal validation results, solutions
may require manual configuration.

- Interdomain scenarios (across Autonomous Systems) that require
information from routing protocols like BGP are out of scope.
Nevertheless, solution may observe routing protocol signaling to detect
that a device is a router.

- Tracking other protocols is not within the scope of the WG.

- No changes to hosts are allowed.

- The WG is prohibited from creating its own protocols or
extensions/modifications of current protocols.

These limitations in the scope may be relaxed through later
rechartering. For instance, solutions tailored for PPP links and
specific environments such as DSL may be added later, or solutions
involving co-operation of the nodes on the link may be developed once
the baseline solutions have been completed.

In order to reach a result that is widely usable and unlikely to disturb
existing network practices, the working group needs to take into account

- nodes that use static addresses,
- nodes with multiple IP addresses on the same interface,
- nodes that use multiple link-layer addresses on the same interface,
- nodes that have multiple interfaces to the same link,
- attachment of another bridge at a bridge port,
- presence of routers, NATs, and other similar devices on the same link,
including their distinction from hosts with multiple interfaces or hosts
with multiple IP addresses on a single interface,
- use of SEcure Neighbor Discovery in some networks,
- nodes that move to another port on the same link, and
- hosts with anycast addresses.

However, should such wide applicability turn out to be impossible, the
working group will document the limitations of the solutions in due
manner. In particular, it is likely that anycast addressing and nodes
that employ multiple interfaces for load balancing at link layer are
indistinguishable from an actual spoofing attack.
There may also be a difference in the applicability between blocking and
merely logging spoofed packets. In any case, the solutions may require
to be explicitly turned on for each network or interface where they are
applicable.

For background information, the working group will also develop a
threats analysis document that describes what threats the solutions from
the WG protect against. This document also contrasts SAVI to existing
solutions.

Milestones:

Jun 08 WG approval
Jul 08 First WG draft on threats document Oct 08 First WG draft on IPv4
solution Oct 08 First WG draft on IPv6 solution Oct 08 Submit document
on threats to IESG for Informational RFC Mar 09 Submit IPv4 solution to
IESG for Proposed Standard May 09 Submit IPv6 solution to IESG for
Proposed Standard _______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Wed May 14 04:58:08 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E80383A697E;
	Wed, 14 May 2008 04:58:08 -0700 (PDT)
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 47E353A6867;
	Wed, 14 May 2008 04:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091, 
	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 1+lf7ypen4Y9; Wed, 14 May 2008 04:58:02 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 0B6D83A67CC;
	Wed, 14 May 2008 04:58:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,486,1204520400"; d="scan'208";a="126524634"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 14 May 2008 07:54:41 -0400
X-IronPort-AV: E=Sophos;i="4.27,486,1204520400"; d="scan'208";a="201772032"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	14 May 2008 07:54:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 14 May 2008 13:54:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BF9D85@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of RADIUS Extensions Working Group (radext)
Thread-Index: Aci1RLkjOAWzy9LnQUytN2wYUiVWLQAdIFGg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <radiusext@ops.ietf.org>, <ops-dir@ietf.org>, <aaa-doctors@ietf.org>,
	<ops-area@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Recharter of RADIUS Extensions Working
	Group (radext)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

 

-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IESG Secretary
Sent: Wednesday, May 14, 2008 1:00 AM
To: ietf-announce@ietf.org
Cc: Bernard_Aboba@hotmail.com; d.b.nelson@comcast.net;
radiusext@ops.ietf.org
Subject: WG Review: Recharter of RADIUS Extensions Working Group
(radext) 

A modified charter has been submitted for the RADIUS Extensions Working
Group in the Operations and Management 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 May 20, 2008.


RADIUS Extensions Working Group (radext)
----------------------------------------
Last Modified: 2008-04-30

Current Status: Active Working Group

Chair(s):
*  Bernard Aboba <Bernard_Aboba@hotmail.com>
*  David Nelson <d.b.nelson@comcast.net> 


Operations and Management Area Director(s):
*  Dan Romascanu <dromasca@avaya.com> 
*  Ronald Bonica <rbonica@juniper.net> 


Operations and Management Area Advisor:
*  Dan Romascanu <dromasca@avaya.com> 


Technical Advisor(s):
*  Paul Congdon <paul.congdon@hp.com> 


Mailing Lists:
General Discussion: radiusext@ops.ietf.org
To Subscribe: radiusext-request@ops.ietf.org
In Body: In Body: subscribe
Archive: https://ops.ietf.org/lists/radiusext


Description of Working Group: 

The RADIUS Extensions Working Group will focus on extensions to the
RADIUS protocol required to define extensions to the standard
attribute space as well as to address cryptographic algorithm
agility and use over new transports. In addition, RADEXT will
work on RADIUS Design Guidelines and define new attributes for 
particular applications of authentication, authorization and 
accounting such as NAS management and local area network (LAN) usage. 

In order to enable interoperation of heterogeneous RADIUS/Diameter
deployments, all RADEXT WG work items MUST contain a Diameter
compatibility section, outlining how interoperability with
Diameter will be maintained.

Furthermore, to ensure backward compatibility with existing RADIUS
implementations, as well as compatibility between RADIUS and Diameter,
the following restrictions are imposed on extensions considered by the
RADEXT WG:

- All documents produced MUST specify means of interoperation with
legacy RADIUS implementations and, if possible, be backward 
compatible with existing RADIUS RFCs, including RFCs 2865-2869, 
3162, 3575, 3579, 3580, 4668-4673,4675, 5080, 5090 and 5176.
Transport profiles should, if possible, be compatible with RFC 3539. 

- All RADIUS work MUST be compatible with equivalent facilities in
Diameter. Where possible, new attributes should be defined so that
the same attribute can be used in both RADIUS and Diameter without
translation. In other cases a translation considerations
section should be included in the specification.


Work Items

The immediate goals of the RADEXT working group are to address the
following issues:

- RADIUS design guidelines. This document will provide guidelines for
design of RADIUS attributes. It will specifically consider how
complex data types may be introduced in a robust manner, maintaining
backwards compatibility with existing RADIUS RFCs, across all the
classes of attributes: Standard, Vendor-Specific and SDO-Specific.
In addition, it will review RADIUS data types and associated
backwards compatibility issues.

- RADIUS Management authorization. This document will define the
use of RADIUS for NAS management over IP. 

-RADIUS attribute space extension. The standard RADIUS attribute
space is currently being depleted. This document will provide
additional standard attribute space, while maintaining backward
compatibility with existing attributes.

-RADIUS Cryptographic Algorithm Agility. RADIUS has traditionally 
relied on MD5 for both per-packet integrity and authentication as well
as attribute confidentiality. Given the increasingly successful
attacks being mounted against MD5, the ability to support
alternative algorithms is required. This work item will
include documentation of RADIUS crypto-agility requirements,
as well as development of one or more Experimental RFCs providing
support for negotiation of alternative cryptographic algorithms
to protect RADIUS.

- IEEE 802 attributes. New attributes have been proposed to
support IEEE 802 standards for wired and wireless LANs. This
work item will support authentication, authorization and
accounting attributes needed by IEEE 802 groups including
IEEE 802.1, IEEE 802.11 and IEEE 802.16.

- New RADIUS transports. A reliable transport profile for
RADIUS will be developed, as well as specifications for 
Secure transports, including TCP/TLS (RADSEC) and UDP/DTLS.

- Documentation of Status-Server usage. A document
describing usage of the Status-Server facility will be
developed.

Goals and Milestones:

Jun 2008 RADIUS Design Guidelines submitted as a Best Current Practice
RFC
Jun 2008 RADIUS Management Authorization I-D submitted as a Proposed
Standard RFC
Sep 2008 RADIUS Crypto-agility Requirements submitted as an
Informational
RFC
Sep 2008 Extended Attributes I-D submitted as a Proposed Standard RFC
Dec 2008 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC
Jan 2009 Reliable Transport Profile for RADIUS I-D submitted as a
Proposed
Standard RFC
Mar 2009 Status-Server I-D submitted as a Proposed Standard RFC
Mar 2009 RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental
RFC
June 2009 RADIUS over DTLS I-D submitted as an Experimental RFC
June 2009 RADIUS Cryptographic Algorithm Agility I-D submitted as an
Experimental RFC
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Fri May 16 03:35:47 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E7EA28C181;
	Fri, 16 May 2008 03:35:47 -0700 (PDT)
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 4927228C16F;
	Fri, 16 May 2008 03:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=0.199,
	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 Kg54sAXK4W+V; Fri, 16 May 2008 03:35:44 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 34C1D3A6883;
	Fri, 16 May 2008 03:35:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,497,1204520400"; d="scan'208";a="126943808"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 16 May 2008 06:35:35 -0400
X-IronPort-AV: E=Sophos;i="4.27,497,1204520400"; d="scan'208";a="202940745"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	16 May 2008 06:35:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 May 2008 12:35:32 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BFA2CC@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for May 22, 2008 Telechat 
Thread-Index: Aci23bwliGHkonPdQwCgkT8p+j4YGgAYnvVA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<ops-dir@ietf.org>, "dns directorate" <dns-dir@ops.ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for May 22,
	2008 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

Please see below the preliminary agenda of the May 22 IESG telechat.

Please let me know if there are any comments or concerns related to the
documents submitted for approval until May 21 COB the latest. 

Thanks and Regards,

Dan


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



2.1 WG Submissions
2.1.1 New Item
  o Two-document ballot:  - 1 of 8
     - draft-ietf-ipr-3978-incoming-09.txt
       Rights Contributors provide to the IETF Trust (BCP) 
     - draft-ietf-ipr-outbound-rights-06.txt
       Advice to the Trustees of the IETF Trust on Rights to be Granted
in
IETF 
       Documents (Informational) 
    Token: Russ Housley
  o draft-ietf-smime-multisig-05.txt
    Multiple Signatures in S/MIME (Proposed Standard) - 2 of 8 
    Token: Tim Polk
  o draft-ietf-mpls-multicast-encaps-09.txt
    MPLS Multicast Encapsulations (Proposed Standard) - 3 of 8 
    Token: Ross Callon
  o draft-ietf-hokey-emsk-hierarchy-05.txt
    Specification for the Derivation of Root Keys from an Extended
Master

    Session Key (EMSK) (Proposed Standard) - 4 of 8 
    Note: proto shepherd is Charles Clancy 
    Token: Tim Polk
  o draft-ietf-pce-pcep-12.txt
    Path Computation Element (PCE) Communication Protocol (PCEP)
(Proposed
 
    Standard) - 5 of 8 
    Token: Ross Callon
  o draft-ietf-mpls-ldp-interarea-03.txt
    LDP extension for Inter-Area LSP (Proposed Standard) - 6 of 8 
    Token: Ross Callon
  o draft-ietf-pce-brpc-09.txt
    A Backward Recursive PCE-based Computation (BRPC) Procedure To
Compute
 
    Shortest Constrained Inter-domain Traffic Engineering Label Switched
Paths 
    (Proposed Standard) - 7 of 8 
    Token: Ross Callon
  o draft-ietf-tsvwg-emergency-rsvp-08.txt
    Resource ReSerVation Protovol (RSVP) Extensions for Emergency
Services
 
    (Proposed Standard) - 8 of 8 
    Token: Magnus Westerlund

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-resnick-2822upd-06.txt
    Internet Message Format (Draft Standard) - 1 of 1 
    Token: Lisa Dusseault

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-v6ops-addcon-07.txt
    IPv6 Unicast Address Assignment Considerations (Informational) - 1
of
1 
    Token: Ron Bonica

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-snell-atompub-bidi-06.txt
    Atom Bidirectional Attribute (Experimental) - 1 of 1 
    Token: Lisa Dusseault

3.2.2 Returning Item
  o draft-wu-sava-testbed-experience-05.txt
    SAVA Testbed and Experiences to Date (Experimental) - 1 of 1 
    Token: Jari Arkko


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o Source Address Validation Improvements (savi) - 1 of 2
    Token: Jari Arkko
  o Data for Reachability of Inter/tra-NetworK SIP (drinks) - 2 of 2
    Token: Jon Peterson
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o EAP Method Update (emu) - 1 of 1
    Token: Pasi Eronen
4.2.2 Proposed for Approval
  o RADIUS EXTensions (radext) - 1 of 2
    Token: Dan Romascanu
  o Mobility EXTensions for IPv6 (mext) - 2 of 2
    Token: Jari Arkko



_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Mon May 19 04:46:06 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD48C28C5EF;
	Mon, 19 May 2008 04:46:06 -0700 (PDT)
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 4BE3228C5EF
	for <aaa-doctors@core3.amsl.com>; Mon, 19 May 2008 04:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.117
X-Spam-Level: 
X-Spam-Status: No, score=-0.117 tagged_above=-999 required=5
	tests=[AWL=-1.182, BAYES_50=0.001, J_CHICKENPOX_44=0.6,
	SARE_UNSUB31=0.464]
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 DGotOpE4igEj for <aaa-doctors@core3.amsl.com>;
	Mon, 19 May 2008 04:46: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 EEF7F28C524
	for <aaa-doctors@ietf.org>; Mon, 19 May 2008 04:46:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,508,1204520400"; d="scan'208";a="107940718"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	19 May 2008 07:46:00 -0400
X-IronPort-AV: E=Sophos;i="4.27,508,1204520400"; d="scan'208";a="197153709"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	19 May 2008 07:45:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 19 May 2008 13:45:57 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C32BAE@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: next step in aaa-doctors team re-organization
Thread-Index: Aci5pectPSj8l2tsRLmbayMDDnvMSA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] next step in aaa-doctors team re-organization
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

Hi, 

We are proceeding to the next phase of the re-organization of the
aaa-doctors review team. 

A few weeks ago I sent a query to all folks on the aaa-doctors list and
a query to the dime and radext wg lists asking for folks interested to
take an active part in the team to volunteer. 

Here is the list of the folks who answered this call. No particular
order. Thanks to all for volunteering. The dime and radext chairs and
secretary are automatically members of the team, although some
volunteered anyway. 

Jari Arkko [jari.arkko@piuha.net]
David B. Nelson [d.b.nelson@comcast.net]
Bernard Aboba [bernard_aboba@hotmail.com]
Jong-Hyouk Lee [jonghyouk@gmail.com]
Glen Zorn [gzorn@arubanetworks.com]
Ahmad Muhanna [amuhanna@nortel.com]
Jouni Korhonen [jouni.korhonen@iki.fi]
John.zhao [john.zhao@huawei.com]
Joseph Salowey (jsalowey) [jsalowey@cisco.com]
Hannes Tschofenig [hannes.tschofenig@gnx.net]
David Frascone <dave@frascone.com> 
Victor Fajardo <vfajardo@tari.toshiba.com> 

The following individuals expressed their desire to stay on the list as
observers but do not have currently the time budget to be active
participants. 

David Mitton [david@mitton.com]
Greg Weber [gdweber@gmail.com]

Thanks to all former members of aaa-doctors for their contributions in
the past. Unless I will receive any message asking for the contrary I
will un-subscribe all other current members from the aaa-doctors list
one week from now leaving only active members and observers on the list.


Next step is a call for one volunteer to be the secretary of the team.
The principal job of the secretary will be to scan the documents
announced for IETF Last Call for any AAA relevant content and to assign
the relevant ones for review to the members of the team using some
trivial algorithm. We may also create a wiki page of the team to
follow-up the status of the work. Volunteers are welcome!

Thanks and Regards,

Dan
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Wed May 28 10:12:38 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9AE7B3A691C;
	Wed, 28 May 2008 10:12:38 -0700 (PDT)
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 2752B3A690E
	for <aaa-doctors@core3.amsl.com>; Wed, 28 May 2008 10:12:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138, 
	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 bT-3aeEikV9U for <aaa-doctors@core3.amsl.com>;
	Wed, 28 May 2008 10:12:33 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id A0A6D28C160
	for <aaa-doctors@ietf.org>; Wed, 28 May 2008 10:06:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,556,1204520400"; d="scan'208";a="128831304"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 28 May 2008 13:07:01 -0400
X-IronPort-AV: E=Sophos;i="4.27,556,1204520400"; d="scan'208";a="208897380"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	28 May 2008 13:07:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 28 May 2008 19:06:59 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C7196B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of EAP Method Update (emu) 
Thread-Index: AcjA5LKIxOSOtzVcQoK8p0E3zA8YjgAAENfQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: WG Review: Recharter of EAP Method Update (emu)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

AAA Doctors,

I suggest that you review this proposed charter and in case there are
any concerns or comments send them to iesg@ietf.org copy to aaa-doctors
list. 

Bernard, it would be useful to forward this also to IEEE 802.11. 

Dan


-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IESG Secretary
Sent: Wednesday, May 28, 2008 8:00 PM
To: new-work@ietf.org
Subject: WG Review: Recharter of EAP Method Update (emu) 

A modified charter has been submitted for the EAP Method Update 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 Wednesday, June 4, 2008.

EAP Method Update (emu)
========================

Last Modified: 2008-05-22

Current Status: Active Working Group

Chair(s):
Joseph Salowey (jsalowey@cisco.com)
Alan DeKok (aland@deployingradius.com)

Security Area Director(s):
Tim Polk (tim.polk@nist.gov)
Pasi Eronen (pasi.eronen@nokia.com)


Security Area Advisor:
Pasi Eronen (pasi.eronen@nokia.com)


Mailing Lists:
General Discussion: emu@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/emu
Archive: http://www.ietf.org/mail-archive/web/emu/current/index.html

Description of Working Group:

The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
access authentication framework used in the PPP, 802.11, 802.16, VPN,
PANA, and in some functions in 3G networks. EAP itself is a simple
protocol and actual authentication happens in EAP methods.

Over 40 different EAP methods exist. Most of these methods are
proprietary methods, but some are documented in informational RFCs. In
the past the lack of documented, open specifications has been a
deployment and interoperability problem. There are currently only two
EAP methods in the standards track that implement features such as key
derivation that are required for many modern applications.
Authentication types and credentials continue to evolve as do
requirements for EAP methods.

This group is chartered to work on the following types of mechanisms to
meet requirements relevant to EAP methods in RFC 3748, RFC 4017, RFC
4962 and EAP Keying:

- A mechanism based on strong shared secrets. This mechanism should
strive to be simple and compact for implementation in resource
constrained environments.

- A document that defines EAP channel bindings and provides guidance for
establishing EAP channel bindings within EAP methods.

- Enable TLS-based EAP methods to support channel bindings. This item
will not generate a new method; rather, it will focus on adding support
for EAP channel bindings to the tunneled method (described below), and
if possible, other TLS-based EAP methods. Potential mechanisms for
adding channel binding support will be investigated, including tunneling
of channel binding parameters, or a TLS extension, or other standard TLS
mechanism

- A mechanism to support extensible communication within a TLS protected
tunnel. This mechanism will support meeting the requirements of an
enhanced TLS mechanism, a password based authentication mechanism, and
additional inner authentication mechanisms. It will also support channel
bindings (as described above) in order to meet RFC 4962 requirements.

- A mechanism that makes use of existing password databases such as AAA
databases. This item will be based on the above tunnel method.

Goals and Milestones:

Jun 2008 Submit Tunnel and Password Method requirements first Draft Sep
2008 Submit EAP Channel Bindings First Draft Sep 2008 Submit Tunnel
Method first draft Oct 2008 Submit TLS based method channel binding
first draft Oct 2008 Submit Password Method first draft Jan 2009 Send
EAP Channel Bindings to IESG Mar 2009 Send Tunnel Method to IESG Apr
2009 Send TLS based method channel binding to IESG Apr 2009 Send
Password based method to IESG
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Wed May 28 12:16:36 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F1BC3A6A6D;
	Wed, 28 May 2008 12:16:36 -0700 (PDT)
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 C72F93A6A6D
	for <aaa-doctors@core3.amsl.com>; Wed, 28 May 2008 12:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094, 
	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 h+x1D1AiYsKG for <aaa-doctors@core3.amsl.com>;
	Wed, 28 May 2008 12:16:32 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130])
	by core3.amsl.com (Postfix) with ESMTP id B11283A6CC3
	for <aaa-doctors@ietf.org>; Wed, 28 May 2008 12:16:13 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1])
	by smtp.piuha.net (Postfix) with ESMTP id 0B72F198759;
	Wed, 28 May 2008 22:16:22 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130])
	by smtp.piuha.net (Postfix) with ESMTP id B08AF198719;
	Wed, 28 May 2008 22:16:19 +0300 (EEST)
Message-ID: <483DAF7E.5070208@piuha.net>
Date: Wed, 28 May 2008 15:16:14 -0400
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.14ubu (X11/20080502)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04C7196B@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04C7196B@307622ANEX5.global.avaya.com>
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: aaa-doctors@ietf.org
Subject: Re: [AAA-DOCTORS] FW: WG Review: Recharter of EAP Method Update
	(emu)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

Looks good to me. (Or some nits were earlier communicated to the
relevant people, but I'm in general happy with this going forward.)

Jari

Romascanu, Dan (Dan) kirjoitti:
> AAA Doctors,
>
> I suggest that you review this proposed charter and in case there are
> any concerns or comments send them to iesg@ietf.org copy to aaa-doctors
> list. 
>
> Bernard, it would be useful to forward this also to IEEE 802.11. 
>
> Dan
>
>
> -----Original Message-----
> From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
> IESG Secretary
> Sent: Wednesday, May 28, 2008 8:00 PM
> To: new-work@ietf.org
> Subject: WG Review: Recharter of EAP Method Update (emu) 
>
> A modified charter has been submitted for the EAP Method Update 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 Wednesday, June 4, 2008.
>
> EAP Method Update (emu)
> ========================
>
> Last Modified: 2008-05-22
>
> Current Status: Active Working Group
>
> Chair(s):
> Joseph Salowey (jsalowey@cisco.com)
> Alan DeKok (aland@deployingradius.com)
>
> Security Area Director(s):
> Tim Polk (tim.polk@nist.gov)
> Pasi Eronen (pasi.eronen@nokia.com)
>
>
> Security Area Advisor:
> Pasi Eronen (pasi.eronen@nokia.com)
>
>
> Mailing Lists:
> General Discussion: emu@ietf.org
> To Subscribe: https://www1.ietf.org/mailman/listinfo/emu
> Archive: http://www.ietf.org/mail-archive/web/emu/current/index.html
>
> Description of Working Group:
>
> The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
> access authentication framework used in the PPP, 802.11, 802.16, VPN,
> PANA, and in some functions in 3G networks. EAP itself is a simple
> protocol and actual authentication happens in EAP methods.
>
> Over 40 different EAP methods exist. Most of these methods are
> proprietary methods, but some are documented in informational RFCs. In
> the past the lack of documented, open specifications has been a
> deployment and interoperability problem. There are currently only two
> EAP methods in the standards track that implement features such as key
> derivation that are required for many modern applications.
> Authentication types and credentials continue to evolve as do
> requirements for EAP methods.
>
> This group is chartered to work on the following types of mechanisms to
> meet requirements relevant to EAP methods in RFC 3748, RFC 4017, RFC
> 4962 and EAP Keying:
>
> - A mechanism based on strong shared secrets. This mechanism should
> strive to be simple and compact for implementation in resource
> constrained environments.
>
> - A document that defines EAP channel bindings and provides guidance for
> establishing EAP channel bindings within EAP methods.
>
> - Enable TLS-based EAP methods to support channel bindings. This item
> will not generate a new method; rather, it will focus on adding support
> for EAP channel bindings to the tunneled method (described below), and
> if possible, other TLS-based EAP methods. Potential mechanisms for
> adding channel binding support will be investigated, including tunneling
> of channel binding parameters, or a TLS extension, or other standard TLS
> mechanism
>
> - A mechanism to support extensible communication within a TLS protected
> tunnel. This mechanism will support meeting the requirements of an
> enhanced TLS mechanism, a password based authentication mechanism, and
> additional inner authentication mechanisms. It will also support channel
> bindings (as described above) in order to meet RFC 4962 requirements.
>
> - A mechanism that makes use of existing password databases such as AAA
> databases. This item will be based on the above tunnel method.
>
> Goals and Milestones:
>
> Jun 2008 Submit Tunnel and Password Method requirements first Draft Sep
> 2008 Submit EAP Channel Bindings First Draft Sep 2008 Submit Tunnel
> Method first draft Oct 2008 Submit TLS based method channel binding
> first draft Oct 2008 Submit Password Method first draft Jan 2009 Send
> EAP Channel Bindings to IESG Mar 2009 Send Tunnel Method to IESG Apr
> 2009 Send TLS based method channel binding to IESG Apr 2009 Send
> Password based method to IESG
> _______________________________________________
> AAA-DOCTORS mailing list
> AAA-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/aaa-doctors
>
>
>   

_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Fri May 30 09:41:21 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35F923A69F9;
	Fri, 30 May 2008 09:41:21 -0700 (PDT)
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 029813A6915;
	Fri, 30 May 2008 09:41:20 -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 4C9SE+cUgET0; Fri, 30 May 2008 09:41:19 -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 2C22E3A67DD;
	Fri, 30 May 2008 09:41:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,567,1204520400"; d="scan'208";a="109437451"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	30 May 2008 12:41:12 -0400
X-IronPort-AV: E=Sophos;i="4.27,567,1204520400"; d="scan'208";a="203241009"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	30 May 2008 12:41:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 30 May 2008 18:41:09 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C71CA9@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for June 5, 2008 Telechat 
Thread-Index: AcjB4hsAqE1ACTQrQaGzEalOQtrhSQAkQ5fg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors" <mib-doctors@ietf.org>,
	<ops-dir@ietf.org>, "dns directorate" <dns-dir@ops.ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for June 5,
	2008 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

Please find below the preliminary agenda of the IESG telechat on 6/5.
Please send to me any comments or concerns until 6/4 COB the latest. 

Thanks and Regards,

Dan


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


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-ospf-ospfv3-traffic-11.txt
    Traffic Engineering Extensions to OSPF version 3 (Proposed Standard)
-
1 of 
    12 
    Token: David Ward
  o Two-document ballot:  - 2 of 12
     - draft-ietf-idr-route-filter-16.txt
       Outbound Route Filtering Capability for BGP-4 (Proposed Standard)

     - draft-ietf-idr-bgp-prefix-orf-04.txt
       Address Prefix Based Outbound Route Filter for BGP-4 (Proposed
Standard) 
    Token: David Ward
  o draft-ietf-pim-join-attributes-03.txt
    Format for using TLVs in PIM messages (Proposed Standard) - 3 of 12 
    Token: David Ward
  o draft-ietf-syslog-tc-mib-08.txt
    Textual Conventions for Syslog Management (Proposed Standard) - 4 of
12 
    Token: Pasi Eronen
  o Two-document ballot:  - 5 of 12
     - draft-ietf-ipr-3978-incoming-09.txt
       Rights Contributors provide to the IETF Trust (BCP) 
     - draft-ietf-ipr-outbound-rights-06.txt
       Advice to the Trustees of the IETF Trust on Rights to be Granted
in
IETF 
       Documents (Informational) 
    Token: Russ Housley
  o draft-ietf-rtgwg-ipfrr-spec-base-12.txt
    Basic Specification for IP Fast-Reroute: Loop-free Alternates
(Proposed 
    Standard) - 6 of 12 
    Token: David Ward
  o draft-ietf-bfd-base-08.txt
    Bidirectional Forwarding Detection (Proposed Standard) - 7 of 12 
    Token: Ross Callon
  o draft-ietf-bfd-multihop-06.txt
    BFD for Multihop Paths (Proposed Standard) - 8 of 12 
    Token: Ross Callon
  o draft-ietf-bfd-v4v6-1hop-08.txt
    BFD for IPv4 and IPv6 (Single Hop) (Proposed Standard) - 9 of 12 
    Token: Ross Callon
  o draft-ietf-bfd-generic-04.txt
    Generic Application of BFD (Proposed Standard) - 10 of 12 
    Token: Ross Callon
  o draft-ietf-bfd-mpls-05.txt
    BFD For MPLS LSPs (Proposed Standard) - 11 of 12 
    Token: Ross Callon
  o draft-ietf-tsvwg-emergency-rsvp-08.txt
    Resource ReSerVation Protovol (RSVP) Extensions for Emergency
Services
 
    (Proposed Standard) - 12 of 12 
    Token: Magnus Westerlund

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-cridland-imap-context-05.txt
    Contexts for IMAP4 (Proposed Standard) - 1 of 1 
    Note: Alexey Melnikov <alexey.melnikov@isode.com> is the
document 
    shepherd 
    Token: Chris Newman

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-pim-lasthop-threats-04.txt
    Host Threats to Protocol Independent Multicast (PIM) (Informational)
-
1 of 
    2 
    Token: David Ward
  o draft-zhu-pkinit-ecc-04.txt
    ECC Support for PKINIT (Informational) - 2 of 2 
    Token: Tim Polk

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-snell-atompub-bidi-06.txt
    Atom Bidirectional Attribute (Experimental) - 1 of 2 
    Token: Lisa Dusseault
  o draft-monrad-sipping-3gpp-urn-namespace-02.txt
    A Uniform Resource Name (URN) Namespace for the 3rd Generation
Partnership 
    Project (3GPP) (Informational) - 2 of 2 
    Token: Lisa Dusseault



_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


From aaa-doctors-bounces@ietf.org  Fri May 30 11:52:59 2008
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 537EC3A6B11;
	Fri, 30 May 2008 11:52:59 -0700 (PDT)
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 63D4C3A6A57;
	Fri, 30 May 2008 11:52:58 -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=[AWL=0.000, 
	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 8HOidFE-sXcY; Fri, 30 May 2008 11:52:57 -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 B85B03A690A;
	Fri, 30 May 2008 11:52:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,568,1204520400"; d="scan'208";a="109455570"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	30 May 2008 14:52:54 -0400
X-IronPort-AV: E=Sophos;i="4.27,568,1204520400"; d="scan'208";a="203294571"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	30 May 2008 14:52:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 30 May 2008 20:52:52 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C71CAD@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Guidelines for authors and reviewers
Thread-Index: AcjB2DC5xUjveQLNQNmaQMe9N0FScQArgwxg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <aaa-doctors@ietf.org>, "MIB Doctors" <mib-doctors@ietf.org>,
	"dns directorate" <dns-dir@ops.ietf.org>, <ops-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: Guidelines for authors and reviewers
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org

 It would be interesting for you to read this document and provide
comments from the perspective of the experience of your teams. 

Dan


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Suresh Krishnan
Sent: Friday, May 30, 2008 1:05 AM
To: IETF Discussion
Subject: Guidelines for authors and reviewers

Hi Folks,
   We have written a draft describing some guidelines for authors and
reviewers of internet drafts. We would really appreciate it if you can
spend some time to go over it and provide comments and/or suggestions
for improvement.

Thanks
Suresh, Pasi and Eric

-------- Original Message --------
Subject: I-D Action:draft-krishnan-review-process-00.txt
Date: Wed, 28 May 2008 11:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
Reply-To: internet-drafts@ietf.org
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

	Title           : Guidelines to authors and reviewers regarding
the 
IETF review process
	Author(s)       : S. Krishnan, et al.
	Filename        : draft-krishnan-review-process-00.txt
	Pages           : 10
	Date            : 2008-05-28

This document describes the IETF review process and provides guidelines
to draft authors and reviewers on how to effectively participate in it.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-krishnan-review-process-00.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors


