From aaa-doctors-bounces@ietf.org Thu Jan 1 04:03:02 2009 Return-Path: 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 0E61028C143; Thu, 1 Jan 2009 04:03:02 -0800 (PST) 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 BEF1D28C13E; Thu, 1 Jan 2009 04:03:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.456 X-Spam-Level: X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.143, 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 0XRB3Ht9dA18; Thu, 1 Jan 2009 04:02:59 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 5CCE428C13B; Thu, 1 Jan 2009 04:02:59 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,313,1228107600"; d="scan'208";a="147266324" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 01 Jan 2009 07:02:47 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jan 2009 07:01:48 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 1 Jan 2009 13:01:46 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-dasgupta-ccamp-path-comp-analysis-02.txt to Informational RFC Thread-Index: AclqwSesuh8x4yJJT/aVd6YRTTc31wBR4PAw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-dasgupta-ccamp-path-comp-analysis-02.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-dasgupta-ccamp-path-comp-analy sis-02.txt Technical Summary This document presents a performance comparison between the per- domain path computation method and the Path Computation Element (PCE) Architecture based Backward Recursive Path Computation (BRPC) procedure. Metrics to capture the significant performance aspects are identified and detailed simulations are carried out on realistic scenarios. A performance analysis for each of the path computation methods is then undertaken. This may be thought of as *a* comparison that tried to capture some metrics. There is no attempt to draw a hard conclusion on which method to use Working Group Summary This purely informational document is an individual submission with AD sponsorship since it is not in the charter of either of the two most closely related WGs (CCAMP and PCE). However, the CCAMP and PCE working groups have been asked for comments, the document was updated based on comments received in CCAMP, and the IETF last call was forwarded to the CCAMP and PCE WGs to solicit their comments. Document Quality This document does not specify anything that would be implemented. The approaches that it is comparing are implemented and at least the MPLS-TE approach is widely deployed. Personnel Ross Callon is the AD sponsoring this individual submission. RFC Editor Note The section "Requirements Language" that introduces the standard key words ("MUST", "MUST NOT", and so on) can be dropped, since the document does not use these key words. Spelling "virutal" in section 2 should be "virtual"; "Eventhough" in section 4 should be "Even though". IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 00:21:07 2009 Return-Path: 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 A02DD28B56A; Sun, 4 Jan 2009 00:21:07 -0800 (PST) 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 C13233A6897; Sun, 4 Jan 2009 00:21:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.457 X-Spam-Level: X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 cDKJ72zhPmGZ; Sun, 4 Jan 2009 00:21:04 -0800 (PST) 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 530113A690B; Sun, 4 Jan 2009 00:21:04 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,324,1228107600"; d="scan'208";a="156564253" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 04 Jan 2009 03:20:51 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Jan 2009 03:20:50 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 4 Jan 2009 09:20:48 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for January 8, 2009 Telechat Thread-Index: Acls/3fkWSY+fmb4Q3mGo5xPppPqgABQqpBQ From: "Romascanu, Dan (Dan)" To: "IETF DNS Directorate" , , , "MIB Doctors (E-mail)" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for January 8, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 1/8 IESG telechat. Please send me comments or questions about the relevant documents until Wednesday 1/7 COB. Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary S 2.1 WG Submissions 2.1.1 New Item o draft-ietf-isis-wg-extlsp-05.txt Simplified Extension of LSP Space for IS-IS (Proposed Standard) - 1 of 3 Token: Ross Callon o draft-ietf-sip-session-policy-framework-05.txt A Framework for Session Initiation Protocol (SIP) Session Policies (Proposed Standard) - 2 of 3 Token: Cullen Jennings o draft-ietf-idr-rfc3392bis-03.txt Capabilities Advertisement with BGP-4 (Proposed Standard) - 3 of 3 Token: David Ward 2.1.2 Returning Item o draft-ietf-smime-3851bis-08.txt Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification (Proposed Standard) - 1 of 2 Token: Tim Polk o draft-ietf-smime-3850bis-08.txt Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling (Proposed Standard) - 2 of 2 Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item o draft-housley-iesg-rfc3932bis-06.txt IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1 Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html Token: Jari Arkko 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-tls-des-idea-02.txt DES and IDEA Cipher Suites for Transport Layer Security (TLS) (Informational) - 1 of 2 Token: Tim Polk o draft-ietf-ippm-delay-var-as-01.txt Packet Delay Variation Applicability Statement (Informational) - 2 of 2 Token: Lars Eggert 3.1.2 Returning Item o draft-ietf-pim-rpf-vector-06.txt The RPF Vector TLV (Informational) - 1 of 1 Token: David Ward 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-dasgupta-ccamp-path-comp-analysis-02.txt Performance Analysis of Inter-Domain Path Computation Methodologies (Informational) - 1 of 3 Token: Ross Callon o draft-raj-dhc-tftp-addr-option-04.txt VoIP Configuration Server Address Option (Informational) - 2 of 3 Token: Jari Arkko o draft-korhonen-mip4-service-07.txt Service Selection for Mobile IPv4 (Informational) - 3 of 3 Token: Jari Arkko 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 NONE 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o Message Organization (morg) - 1 of 1 Token: Chris Newman 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o Network Configuration (netconf) - 1 of 2 Token: Dan Romascanu o IP Performance Metrics (ippm) - 2 of 2 Token: Lars Eggert _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 00:23:40 2009 Return-Path: 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 C17113A690B; Sun, 4 Jan 2009 00:23:40 -0800 (PST) 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 775C93A690B; Sun, 4 Jan 2009 00:23:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.459 X-Spam-Level: X-Spam-Status: No, score=-2.459 tagged_above=-999 required=5 tests=[AWL=0.140, 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 qSd2xEP5yfJp; Sun, 4 Jan 2009 00:23:38 -0800 (PST) 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 9066F3A6844; Sun, 4 Jan 2009 00:23:37 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,324,1228107600"; d="scan'208";a="133021794" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Jan 2009 03:23:23 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Jan 2009 03:23:22 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 4 Jan 2009 09:23:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-sip-session-policy-framework-05.txt toProposed Standard Thread-Index: Aclsih7dHL4qBj55Q4S7bK/8fUL4ZQBu3ljw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-sip-session-policy-framework-05.txt toProposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-session-policy-framew ork-05.txt Technical summary. Proxy servers play a central role as an intermediary in the Session Initiation Protocol (SIP) as they define and impact policies on call routing, rendezvous, and other call features. This document specifies a framework for SIP session policies that provides a standard mechanism by which a proxy can define or influence policies on sessions, such as the codecs or media types to be used. It defines a model, an overall architecture and new protocol mechanisms for session policies. Working group summary. There is consensus in the working group to publish this document. The early stimulus for this work came from discussions at the joint IETF/3GPP workshop held in San Francisco in January 2003. Document Quality There has been no indication of implementation. Personnel The document shepherd for this document is Keith Drage. The responsible Area Director is Cullen Jennings. RFC Editor Note TBD IRTF Note None IESG Note None IANA Note None _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 00:26:56 2009 Return-Path: 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 06D1E3A6806; Sun, 4 Jan 2009 00:26:56 -0800 (PST) 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 13B213A6806; Sun, 4 Jan 2009 00:26:55 -0800 (PST) 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 wl3cRdwTms6K; Sun, 4 Jan 2009 00:26:54 -0800 (PST) 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 3234C3A67E2; Sun, 4 Jan 2009 00:26:54 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,324,1228107600"; d="scan'208";a="156564401" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 04 Jan 2009 03:26:41 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Jan 2009 03:26:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 4 Jan 2009 09:26:39 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-korhonen-mip4-service-07.txt to Informational RFC Thread-Index: Aclt3U+zt4eXanQ8Sva5G2u+oaXsnQAaHMMQ From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" Subject: [AAA-DOCTORS] FW: Evaluation: draft-korhonen-mip4-service-07.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-korhonen-mip4-service-05.txt Technical Summary This document describes a Service Selection extension for both conventional Mobile IPv4 and Proxy Mobile IPv4 that is intended to assist home agents to make a specific service selection for the mobility service subscription during the binding update procedure. The service selection may affect home agent routing decisions, Qos and policy treatment of service related IP flows in the home agent and also Home Address assignment policies. Working Group Summary This document is an individual submission. The document was presented in MIP4 WG meetings. The document was proposed to be a WG work item. However, the decision of adoption as a WG work item got postponed due time schedule challenges with the current MIP4 WG charter and dependencies with external Standardization Development Organizations. Document Quality There are no publicly known implementations yet. There is certain level of interest from 3GPP Release-8 Evolved Packet Core work. The document has been used in 3GPP TS 24.304 as a part of their MIP4 based trusted non-3GPP access interworking solution. Personnel The responsible Area Director is Jari Arkko. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 09:23:38 2009 Return-Path: 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 36FAC3A6982; Sun, 4 Jan 2009 09:23:38 -0800 (PST) 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 DF9A928C0F6 for ; Sun, 4 Jan 2009 05:59:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.576 X-Spam-Level: X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 PeaY6EeFA2fS for ; Sun, 4 Jan 2009 05:59:52 -0800 (PST) Received: from QMTA03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by core3.amsl.com (Postfix) with ESMTP id 76A0528C0E4 for ; Sun, 4 Jan 2009 05:59:52 -0800 (PST) Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA03.emeryville.ca.mail.comcast.net with comcast id zRpu1a00516AWCUA3Rzg0J; Sun, 04 Jan 2009 13:59:40 +0000 Received: from [10.36.0.45] ([76.119.58.152]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id zRzc1a0023H3vh08SRzd0Y; Sun, 04 Jan 2009 13:59:40 +0000 Message-Id: From: Margaret Wasserman To: "Romascanu, Dan (Dan)" In-Reply-To: Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 4 Jan 2009 08:59:33 -0500 References: X-Mailer: Apple Mail (2.929.2) X-Mailman-Approved-At: Sun, 04 Jan 2009 09:23:36 -0800 Cc: aaa-doctors@ietf.org, "MIB Doctors \(E-mail\)" , ops-dir@ietf.org, IETF DNS Directorate Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: PRELIMINARY Agenda and Package for January 8, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Sender: aaa-doctors-bounces@ietf.org Errors-To: aaa-doctors-bounces@ietf.org Hi Dan, Is it possible to send us the proposed charter text for netconf and ippm? I don't have any particular concerns about rechartering these groups, but I would be willing to look over the text. Margaret On Jan 4, 2009, at 3:20 AM, Romascanu, Dan (Dan) wrote: > Please find below the preliminary agenda of the 1/8 IESG telechat. > Please send me comments or questions about the relevant documents > until > Wednesday 1/7 COB. > > Thanks and Regards, > > Dan > > > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf > Of > IESG Secretary > S > > 2.1 WG Submissions > 2.1.1 New Item > o draft-ietf-isis-wg-extlsp-05.txt > Simplified Extension of LSP Space for IS-IS (Proposed Standard) - 1 > of > 3 > Token: Ross Callon > o draft-ietf-sip-session-policy-framework-05.txt > A Framework for Session Initiation Protocol (SIP) Session Policies > (Proposed Standard) - 2 of 3 > Token: Cullen Jennings > o draft-ietf-idr-rfc3392bis-03.txt > Capabilities Advertisement with BGP-4 (Proposed Standard) - 3 of 3 > Token: David Ward > > 2.1.2 Returning Item > o draft-ietf-smime-3851bis-08.txt > Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 > Message > Specification (Proposed Standard) - 1 of 2 > Token: Tim Polk > o draft-ietf-smime-3850bis-08.txt > Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 > Certificate Handling (Proposed Standard) - 2 of 2 > Token: Tim Polk > > > 2.2 Individual Submissions > 2.2.1 New Item > NONE > 2.2.2 Returning Item > o draft-housley-iesg-rfc3932bis-06.txt > IESG Procedures for Handling of Independent and IRTF Stream > Submissions > (BCP) - 1 of 1 > Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html > Token: Jari Arkko > > > 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-tls-des-idea-02.txt > DES and IDEA Cipher Suites for Transport Layer Security (TLS) > (Informational) - 1 of 2 > Token: Tim Polk > o draft-ietf-ippm-delay-var-as-01.txt > Packet Delay Variation Applicability Statement (Informational) - 2 > of > 2 > Token: Lars Eggert > > 3.1.2 Returning Item > o draft-ietf-pim-rpf-vector-06.txt > The RPF Vector TLV (Informational) - 1 of 1 > Token: David Ward > > > 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-dasgupta-ccamp-path-comp-analysis-02.txt > Performance Analysis of Inter-Domain Path Computation Methodologies > (Informational) - 1 of 3 > Token: Ross Callon > o draft-raj-dhc-tftp-addr-option-04.txt > VoIP Configuration Server Address Option (Informational) - 2 of 3 > Token: Jari Arkko > o draft-korhonen-mip4-service-07.txt > Service Selection for Mobile IPv4 (Informational) - 3 of 3 > Token: Jari Arkko > > 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 > , but this does not prevent publishing; 3) The IESG thinks > that publication is harmful to work in WG and recommends > not publishing at this time; 4) The IESG thinks that this > document violates the IETF procedures for 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 > NONE > 3.3.2 Returning Item > NONE > > 4. Working Group Actions > 4.1 WG Creation > 4.1.1 Proposed for IETF Review > NONE > 4.1.2 Proposed for Approval > o Message Organization (morg) - 1 of 1 > Token: Chris Newman > 4.2 WG Rechartering > 4.2.1 Under evaluation for IETF Review > o Network Configuration (netconf) - 1 of 2 > Token: Dan Romascanu > o IP Performance Metrics (ippm) - 2 of 2 > Token: Lars Eggert > > > _______________________________________________ > OPS-DIR mailing list > OPS-DIR@ietf.org > https://www.ietf.org/mailman/listinfo/ops-dir _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 09:26:38 2009 Return-Path: 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 57DB33A687C; Sun, 4 Jan 2009 09:26:38 -0800 (PST) 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 27DBC3A687C; Sun, 4 Jan 2009 09:26:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.464 X-Spam-Level: X-Spam-Status: No, score=-2.464 tagged_above=-999 required=5 tests=[AWL=0.135, 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 ZK2zqe8DPscl; Sun, 4 Jan 2009 09:26:36 -0800 (PST) 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 BC32E3A67A8; Sun, 4 Jan 2009 09:26:33 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,328,1228107600"; d="scan'208";a="133033464" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 04 Jan 2009 12:26:18 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 04 Jan 2009 12:26:17 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 4 Jan 2009 18:26:14 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-DIR] FW: PRELIMINARY Agenda and Package for January 8, 2009 Telechat Thread-Index: AcludLPmlwiUNodgR/W2/HwppEVifgAAEhuA References: From: "Romascanu, Dan (Dan)" To: "Margaret Wasserman" Cc: aaa-doctors@ietf.org, "MIB Doctors \(E-mail\)" , ops-dir@ietf.org, IETF DNS Directorate Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: PRELIMINARY Agenda and Package for January 8, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Margaret Wasserman [mailto:mrw@lilacglade.org] > Sent: Sunday, January 04, 2009 4:00 PM > To: Romascanu, Dan (Dan) > Cc: IETF DNS Directorate; ops-dir@ietf.org; > aaa-doctors@ietf.org; MIB Doctors (E-mail) > Subject: Re: [OPS-DIR] FW: PRELIMINARY Agenda and Package for > January 8, 2009 Telechat > > > Hi Dan, > > Is it possible to send us the proposed charter text for > netconf and ippm? I don't have any particular concerns about > rechartering these groups, but I would be willing to look > over the text. > > Margaret > Here you go: -------------- Message ORGanization (morg) ------------------------------------------ Last Modified: 2008-12-11 Current Status: Proposed Working Group Chair(s): Randall Gellens (co-chair TBD) Applications Area Directors: Chris Newman Lisa Dusseault Application Area Advisor: Chris Newman Mailing Lists: General Discussion: morg@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/morg Archive: http://www.ietf.org/mail-archive/web/morg/current/maillist.html Description: The IETF Message Organization extensions Working Group will work on IMAP extensions that improve clients' ability to find messages or groups of messages in an IMAP mailstore. As a secondary goal, the WG will design its extensions so as to minimize client/server round trips and bandwidth overhead. In particular the Working Group is chartered to finalize and publish the following IMAP extensions as proposed standards: (a) A SORT extension specifying new sort criteria for header fields containing email addresses. This extension will be based on draft-karp-morg-sortdisplay-00.txt. (b) A SEARCH extension specifying new search criteria for header fields containing email addresses. (c) A LIST extension for returning STATUS information in LIST responses. This extension will be based on draft-melnikov-imapext-status-in-list-00.txt. (d) An extension that formalizes a way to return message counters by message context using STATUS and SEARCH commands. (e) An extension that specifies Internet-search-engine-like searching. Such searches would be more flexible (and less formally defined) than substring-based searches, and may return their results in a significant order. They may include "relevance" scores or similar information that could be useful to the user. (f) New collation algorithms such as "ignore whitespace" and "numeric, ignoring punctuation". The WG group will determine which collations are needed, taking into consideration the needs of the protocols that use the collation framework. (g) An extension that allows searching for messages within a message thread. This extension will be based on draft-gulbrandsen-imap-inthread-03.txt. (h) An extension that allows searching of multiple mailboxes at the same time (based on draft-melnikov-imapext-multimailbox-search-03.txt), or of multiple mailbox views. The WG will determine which approach (mailboxes or views) is more suitable as part of its work. Additional documents may be added this list, but only via a charter revision. There must also be demonstrable willingness in the IMAP development community to actually implement a given extension before it can be added to this charter. Revising or replacing the base IMAP4rev1 specification (RFC 3501) is out of the scope of this WG. This WG will ensure that all extensions it proposes take into account any existing problems in the base specification of IMAP, and do not make them worse nor make the problems harder to address in the future. ==== --------------------------------- Network Configuration (netconf) ================================ Last Modified: 2008-12-16 Additional information is available at tools.ietf.org/wg/netconf Chair(s): Bert Wijnen Mehmet Ersue Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Technical Advisor(s): Charlie Kaufman Mailing Lists: General Discussion: netconf@ietf.org To Subscribe: netconf-request@ietf.org In Body: in msg body: subscribe Archive: http://www.ietf.org/mail-archive/web/netconf/ Description of Working Group: Charlie Kaufman is Technical Advisor for Security Matters Configuration of networks of devices has become a critical requirement for operators in today's highly interoperable networks. Operators from large to small have developed their own mechanisms or used vendor specific mechanisms to transfer configuration data to and from a device, and for examining device state information which may impact the configuration. Each of these mechanisms may be different in various aspects, such as session establishment, user authentication, configuration data exchange, and error responses. The NETCONF Working Group is chartered to produce a protocol suitable for network configuration, with the following characteristics: - Provides retrieval mechanisms which can differentiate between configuration data and non-configuration data - Is extensible enough so that vendors will provide access to all configuration data on the device using a single protocol - Has a programmatic interface (avoids screen scraping and formatting-related changes between releases) - Uses a textual data representation, that can be easily manipulated using non-specialized text manipulation tools. - Supports integration with existing user authentication methods - Supports integration with existing configuration database systems - Supports network wide configuration transactions (with features such as locking and rollback capability) - Is as transport-independent as possible - Provides support for asynchronous notifications. The NETCONF protocol is using XML for data encoding purposes, because XML is a widely deployed standard which is supported by a large number of applications. The NETCONF protocol should be independent of the data definition language and data models used to describe configuration and state data. However, the authorization model used in the protocol is dependent on the data model. Although these issues must be fully addressed to develop standard data models, only a small part of this work will be initially addressed. This group will specify requirements for standard data models in order to fully support the NETCONF protocol, such as: - identification of principals, such as user names or distinguished names - mechanism to distinguish configuration from non-configuration data - XML namespace conventions - XML usage guidelines The initial work started in 2003 and has already been completed and was restricted to following items: a) NETCONF Protocol Specification, which defines the operational model, protocol operations, transaction model, data model requirements, security requirements, and transport layer requirements. b) NETCONF over SSH Specification: Implementation Mandatory, c) NETCONF over BEEP Specification: Implementation Optional, d) NETCONF over SOAP Specification: Implementation Optional. These documents define how the NETCONF protocol is used with each transport protocol selected by the working group, and how it meets the security and transport layer requirements of the NETCONF Protocol Specification. e) NETCONF Notification Specification, which defines mechanisms that provide an asynchronous message notification delivery service for the NETCONF protocol. NETCONF Notification is an optional capability built on top of the base NETCONF definition and provides the capabilities and operations necessary to support this service. The NETCONF notification specification has been finished now as well. In the current phase of the incremental development of NETCONF the workgroup will focus on following items: 1. Fine-grain locking: The base NETCONF protocol only provides a lock for the entire configuration datastore, which is not deemed to meet important operational and security requirements. The NETCONF working group will produce a standards-track RFC specifying a mechanism for fine-grain locking of the NETCONF configuration datastore. 2. NETCONF monitoring: It is considered best practice for IETF working groups to include management of their protocols within the scope of the solution they are providing. The NETCONF working group will produce a standards-track RFC with mechanisms allowing NETCONF itself to be used to monitor some aspects of NETCONF operation. 3. Schema advertisement: Currently the NETCONF protocol is able to advertise which protocol features are supported on a particular netconf-capable device. However, there is currently no way to discover which XML Schema are supported on the device. The NETCONF working group will produce a standards-track RFC with mechanisms making this discovery possible (this item may be merged with "NETCONF monitoring" into a single document). Note: The schema-advertisement material has been merged into the NETCONF monitoring document based on WG consensus. 4. NETCONF over TLS: Based on implementation experience there is a need for a standards track document to define NETCONF over TLS as an optional transport for the NETCONF protocol. 5. NETCONF default handling: NETCONF today does not define whether default values should be returned by the server in replies to requests for reading configuration and state data. Different clients have different needs to receive or not to receive default data. The NETCONF working group will produce a standards-track RFC defining a mechanism that allows NETCONF clients to control whether default data is returned by the netconf server. 6. NETCONF implementations have shown that the specification in RFC4741 is not 100% clear and has lead to different interpretations and implementations. Also some errors have been uncovered. So the WG will do an rfc4741bis with following constraints: - bug fixes are to be done - clarifications can be done - extensions can be done only when needed to fix bugs or inconsistencies (i.e. we are not doing a NETCONF V2) - The work can be started based on the discussion in IETF #73 (see http://www.ietf.org/proceedings/08nov/slides/netconf-3.pdf). Note: A technical errata has been posted on rfc4742. If the work on rfc4741bis uncovers any additional fixes/clarifications that need to be made to rfc4742, the WG may consider to also do a rfc4742bis as part of this work-item. The following items have been identified as important but are currently not considered in scope for re-chartering and may be candidates for work when there is community consensus to take them on: - NETCONF Notification content - Access Control requirements - NETCONF access to SMI-based MIB data Goals and Milestones: Done Working Group formed Done Submit initial Netconf Protocol draft Done Submit initial Netconf over (transport-TBD) draft Done Begin Working Group Last Call for the Netconf Protocol draft Done Begin Working Group Last Call for the Netconf over (transport-TBD) draft Done Submit final version of the Netconf Protocol draft to the IESG Done Submit final version of the Netconf over SOAP draft to the IESG Done Submit final version of the Netconf over BEEP draft to the IESG Done Submit final version of the Netconf over SSH draft to the IESG Done Update charter Done Submit first version of NETCONF Notifications document Done Begin WGLC of NETCONF Notifications document Done Submit final version of NETCONF Notifications document to IESG for consideration as Proposed Standard Done -00 draft for fine Grain Locking Done -00 draft for NETCONF over TLS Done -00 draft for NETCONF Monitoring Done -00 draft for Schema Advertisement Done Early Review of client authentication approach (for NETCONF over TLS) with the security community at IETF 71 N.A. WG Last Call on Schema Advertisement after IETF72 Schema Advertisement has been merged into Monitoring Done WG Last Call on NETCONF over TLS after IETF72 Done Netconf over TLS to IESG for consideration as Proposed Standards Dec 2008 WG Last Call on Fine Grain Locking after IETF73 Dec 2008 Send Partial Locking to IESG for consideration as Proposed Standards Jan 2009 Initial WG draft for with-defaults capability Feb 2009 Initial WG draft for rfc4741bis Mar 2009 WG Last Call on NETCONF Monitoring after IETF73 Apr 2009 WG Last Call on rfc4741bis Apr 2009 WG Last Call on with-defaults Jun 2009 rfc4741bis to IESG for considerations as Proposed Standard Jun 2009 with-defaults capability to IESG for considerations as Proposed Standard ------------------------------- IP Performance Metrics (ippm) -------------------------------------------- Last Modified: 2008-12-19 Status: Active Working Group Additional information is available at tools.ietf.org/wg/ippm Chair(s): Matthew Zekauskas [matt@internet2.edu] Henk Uijterwaal [henk@ripe.net] Transport Area Director(s): Magnus Westerlund magnus.westerlund@ericsson.com] Lars Eggert [lars.eggert@nokia.com] Transport Area Advisor: Lars Eggert [lars.eggert@nokia.com] Mailing Lists: General Discussion: ippm@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/ippm In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/ippm/index.html Description of Working Group: The IPPM WG has developed a set of standard metrics that can be applied to the quality, performance, and reliability of Internet data delivery services. These metrics are designed such that they can be performed by network operators, end users, or independent testing groups. It is important that the metrics not represent a value judgment (i.e. define "good" and "bad"), but rather provide unbiased quantitative measures of performance. Functions peripheral to Internet data delivery services, such as NOC/NIC services, are beyond the scope of this working group. The IPPM WG has produced documents that define specific metrics and procedures for accurately measuring and documenting these metrics. This is the current list of fundamental metrics and the existing set of derived metrics. - connectivity - one-way delay and loss - round-trip delay. - delay variation - loss patterns - packet reordering - bulk transport capacity - link bandwidth capacity - packet duplication The working group will advance these metrics along the standards track within the IETF. It will be guided by applicable IESG documents in this area. Additionally, the WG will produce Proposed Standard AS documents, comparable to applicability statements in RFC 2026, that will focus on procedures for measuring the individual metrics and how these metrics characterize features that are important to different service classes, such as bulk transport, periodic streams, packet bursts or multimedia streams. Each AS document will discuss the performance characteristics that are pertinent to a specified service class; clearly identify the set of metrics that aid in the description of those characteristics; specify the methodologies required to collect said metrics; and lastly, present the requirements for the common, unambiguous reporting of testing results. The AS documents can also discuss the use of the metrics to verify performance expectations, such as SLA's, report results to specific user groups or investigate network problems. The focus is, again, to define how this should be done, not to define a value judgment. The WG may define additional statistics for its metrics if needed. Specific topics of these AS documents must be approved by the Area Directors as charter additions. The WG will work on documents describing how to compose and decompose the results of its metrics over time or space. The WG has produced protocols to enable communication among test equipment that implements the one- and two-way metrics (OWAMP and TWAMP respectively). OWAMP and TWAMP will be advanced along the standards track. Further development of these protocols will also be done inside the WG. The metrics developed by the WG were developed inside an active measurement context, that is, the devices used to measure the metrics produce their own traffic. However, most metrics can be used inside a passive context as well. No work is planned is this area though, this may be changed with AD approval. The intent of the WG is to cooperate with other appropriate standards bodies and forums (such as ATIS IIF, ITU-T SG 12, 13 and 15, MEF) to promote consistent approaches and metrics. Within the IETF process, IPPM metrics definitions will be subject to as rigorous a scrutiny for usefulness, clarity, and accuracy as other protocol standards. The IPPM WG will interact with other areas of IETF activity whose scope intersect with the requirement of these specific metrics. The WG will, on request, provide input to other IETF WG on the use of these metrics. ------------------------ _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 4 12:14:38 2009 Return-Path: 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 09D0F3A6A8A; Sun, 4 Jan 2009 12:14:38 -0800 (PST) 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 134F13A6A8A for ; Sun, 4 Jan 2009 12:14:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.203 X-Spam-Level: X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[AWL=0.396, 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 FSr3adTTj8US for ; Sun, 4 Jan 2009 12:14:36 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id CE6523A689C for ; Sun, 4 Jan 2009 12:14:34 -0800 (PST) Received: (qmail invoked by alias); 04 Jan 2009 20:14:20 -0000 Received: from a91-154-105-43.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.105.43] by mail.gmx.net (mp064) with SMTP; 04 Jan 2009 21:14:20 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1/p1vAHKx7p2oLbxp102V0q1vv/xE2twJEKfKEx0/ lPcvuEZDONAmBW From: "Hannes Tschofenig" To: Date: Sun, 4 Jan 2009 22:14:49 +0200 Message-ID: <009b01c96ea9$18b7d900$0201a8c0@nsnintra.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acluo+D6K8UH3xGqQcuqhiSzW5v0mAABSF2Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.86 Subject: [AAA-DOCTORS] FW: Review of "Software Hub and Spoke Framework"? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Bernard ran into this document. I guess that this would be something to review for us as well. Who volunteers? ________________________________ From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba Sent: 04 January, 2009 21:36 To: radiusext@ops.ietf.org Subject: Review of "Software Hub and Spoke Framework"? The document "'Softwire Hub & Spoke Deployment Framework with L2TPv2" has gone to IETF last call: http://www.ietf.org/mail-archive/web/ietf-announce/current/msg05459.html Has anyone taken a look at this document? It is available here: http://tools.ietf.org/html/draft-ietf-softwire-hs-framework-l2tpv2 The document does seem to deal with a number of AAA-related issues, including limitations in RADIUS accounting. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 6 02:07:28 2009 Return-Path: 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 946B728C10F; Tue, 6 Jan 2009 02:07:28 -0800 (PST) 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 9558028C10A; Tue, 6 Jan 2009 02:07:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.472 X-Spam-Level: X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 VQmlOJIhhq1H; Tue, 6 Jan 2009 02:07:26 -0800 (PST) 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 39C8128C108; Tue, 6 Jan 2009 02:07:25 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,337,1228107600"; d="scan'208";a="133192920" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jan 2009 05:07:11 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jan 2009 05:07:10 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Jan 2009 11:07:08 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-hoffman-dac-vbr-05.txt to Proposed Standard Thread-Index: AclvhIK58YFJtluKSBusB/LWP/mjBgAYexVA From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-hoffman-dac-vbr-05.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-hoffman-dac-vbr-04.txt Technical Summary Vouch By Reference (VBR) is a protocol for adding third-party certification to email. It permits independent third parties to certify the owner of a domain name that is associated with received mail. VBR may be performed anywhere along the email transit path, by any capable receiving module, either within the handling service or by end-user software. Working Group Summary This document is not the product of any IETF WG. Protocol Quality VBR has already been implemented in at least one SMTP server product, and pre-release implementations have been made by other developers. None have reported any technical issues with implementing it. The documents were reviewed by Russ Housley for the IESG. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 6 03:39:14 2009 Return-Path: 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 85A563A686E; Tue, 6 Jan 2009 03:39:14 -0800 (PST) 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 EA5F93A6768; Tue, 6 Jan 2009 03:39:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.474 X-Spam-Level: X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 mc7fyCH8J1yB; Tue, 6 Jan 2009 03:39:12 -0800 (PST) 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 E91CB3A679C; Tue, 6 Jan 2009 03:39:11 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,338,1228107600"; d="scan'208";a="156770854" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 06 Jan 2009 06:38:58 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Jan 2009 06:38:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Jan 2009 12:38:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-sieve-managesieve-06.txt to Proposed Standard Thread-Index: AclvWpyHpgf0/avGQ2WN9vkt8R5k5AAmLKTw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-sieve-managesieve-06.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sieve-managesieve-05.txt Technical Summary Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This document describes a protocol "ManageSieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts. Working Group Summary There was a discussion on the mailing list about use of synchronizing literals in the protocol. An earlier version incorrectly documented existing practice and at the same time was inconsistent with IMAP LITERAL+ extension. So there was a concern that some existing implementation might implement this incorrectly. However the author is not aware of any such implementation. More recently, there has been discussion of the overall command structure, mandatory-to-implement security mechanisms, and of some specific details in the sieve URL format. Consensus appears to have been reached on all of these issues. Document Quality There are multiple server and client implementations of the ManageSieve protocol. The following is an incomplete list of servers implementing ManageSieve: CMU, Dbmail, Dovecot, Isode, ArchiveOpteryx, pysieved (Python Managesieve Server), Citadel. The following clients are known to implement ManageSieve: Mulberry, Phil Pennock's sieve-connect, Polymer, Ruby/ManageSieve, Net-ManageSieve (perl), SIEVE plugin for Thunderbird, KMail, gsieve, Emacs-based ManageSieve implementation. Note that many if not most of these implementtations were written according to earlier versions of the specification and may require updates to be compliant with the current version. Personnel Ned Freed is the Document Shepherd. Lisa Dusseault reviewed this for the IESG. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 6 06:27:38 2009 Return-Path: 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 7047B3A68F2; Tue, 6 Jan 2009 06:27:38 -0800 (PST) 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 9A6A73A6869 for ; Tue, 6 Jan 2009 06:27:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.193 X-Spam-Level: X-Spam-Status: No, score=-2.193 tagged_above=-999 required=5 tests=[AWL=0.406, 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 vQfBYLLlsrzM for ; Tue, 6 Jan 2009 06:27:36 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 65F3B3A6840 for ; Tue, 6 Jan 2009 06:27:35 -0800 (PST) Received: (qmail invoked by alias); 06 Jan 2009 14:27:22 -0000 Received: from a91-154-105-43.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.105.43] by mail.gmx.net (mp008) with SMTP; 06 Jan 2009 15:27:22 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19+nikPMaZ+cn7IYiFJvM+exl1eAB6iBLo4+ggthi zD0OJPCjQrEECj From: "Hannes Tschofenig" To: , References: <009b01c96ea9$18b7d900$0201a8c0@nsnintra.net> Date: Tue, 6 Jan 2009 16:30:25 +0200 Message-ID: <027601c9700b$516d5280$0201a8c0@nsnintra.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acluo+D6K8UH3xGqQcuqhiSzW5v0mAABSF2QAFh5+IA= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <009b01c96ea9$18b7d900$0201a8c0@nsnintra.net> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.66 Cc: aaa-doctors@ietf.org Subject: Re: [AAA-DOCTORS] FW: Review of "Software Hub and Spoke Framework"? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 John and Ahmad, could you review the document by the end of this week? Ciao Hannes >-----Original Message----- >From: aaa-doctors-bounces@ietf.org >[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of ext Hannes >Tschofenig >Sent: 04 January, 2009 22:15 >To: aaa-doctors@ietf.org >Subject: [AAA-DOCTORS] FW: Review of "Software Hub and Spoke >Framework"? > >Bernard ran into this document. I guess that this would be >something to review for us as well. >Who volunteers? > > > >________________________________ > > From: owner-radiusext@ops.ietf.org >[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba > Sent: 04 January, 2009 21:36 > To: radiusext@ops.ietf.org > Subject: Review of "Software Hub and Spoke Framework"? > > > The document "'Softwire Hub & Spoke Deployment >Framework with L2TPv2" has gone > to IETF last call: > >http://www.ietf.org/mail-archive/web/ietf-announce/current/msg0 >5459.html > > Has anyone taken a look at this document? It is available here: > >http://tools.ietf.org/html/draft-ietf-softwire-hs-framework-l2tpv2 > > The document does seem to deal with a number of >AAA-related issues, including > limitations in RADIUS accounting. > > > > > > > >_______________________________________________ >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 Tue Jan 6 08:51:17 2009 Return-Path: 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 F0D6D3A68A1; Tue, 6 Jan 2009 08:51:17 -0800 (PST) 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 AE8E83A688D; Tue, 6 Jan 2009 08:51:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.476 X-Spam-Level: X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123, 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 URrMhyz2Gp89; Tue, 6 Jan 2009 08:51:16 -0800 (PST) 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 5972A3A689D; Tue, 6 Jan 2009 08:51:15 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,339,1228107600"; d="scan'208";a="133236322" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jan 2009 11:50:59 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Jan 2009 11:50:58 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Jan 2009 17:50:46 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-pce-dste-02.txt to Proposed Standard Thread-Index: AclwHn5AruoAGfL3QjqL0x6SQzbgGAAAF4ow From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-pce-dste-02.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-dste-02.txt Technical Summary This document specifies a CLASSTYPE object to support Diff-Serve Aware Traffic Engineering (DS-TE) where path computation is performed with an aid of Path Computation Element (PCE). Working Group Summary Good consensus reported (see PROTO writeup by JP Vasseur). The document specifies fairly straightforward protocol extensions to support diff serve when using PCE. Document Quality No known implementation of the I-D but several mentioned that they were planning to implement the protocol extensions specifies in the document. Furthermore, the protocol extensions are very straightforward. Personnel JP Vasseur is the Document Shepherd for this document. Ross Callon is the Responsible Area Director. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 6 08:52:23 2009 Return-Path: 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 335543A68E3; Tue, 6 Jan 2009 08:52:23 -0800 (PST) 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 F00D03A688D; Tue, 6 Jan 2009 08:52:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.477 X-Spam-Level: X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122, 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 KEvNGoJS-ojO; Tue, 6 Jan 2009 08:52:21 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id CE94E3A6405; Tue, 6 Jan 2009 08:52:20 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,339,1228107600"; d="scan'208";a="147658487" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 06 Jan 2009 11:52:06 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Jan 2009 11:52:05 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Jan 2009 17:52:05 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-idr-flow-spec-03.txt to Proposed Standard Thread-Index: AclwHRId5EABXbQ2SwOmJDTeRYE7wgAAf1tw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-idr-flow-spec-03.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-flow-spec-03.txt Technical Summary This document defines a new BGP NLRI encoding format that can be used to distribute traffic flow specifications. This allows the routing system to propagate information regarding more-specific components of the traffic aggregate defined by an IP destination prefix. Additionally it defines two applications of that encoding format. One that can be used to automate inter-domain coordination of traffic filtering, such as what is required in order to mitigate (distributed) denial of service attacks. And a second application to traffic filtering in the context of a BGP/MPLS VPN service. The information is carried via the Border Gateway Protocol (BGP), thereby reusing protocol algorithms, operational experience and administrative processes such as inter-provider peering agreements. Working Group Summary Was there anything in the WG process that is worth noting? For example, was there controversy about particular points or were there decisions where the consensus was particularly rough? Document Quality There are multiple, interoperable implementations. There were no LC comments during WG LC although the technology and draft have been known, discussed and available for many years. Personnel Yakov Rekhter is the Document Shepherd for this document. Dave Ward is the Area Director. IANA Note Future assignments beyond what is specified in the draft are to be made using either the Standards Action process defined in [RFC2434], the Early IANA Allocation process defined in [RFC4020], or the "First Come First Served" policy defined in [RFC2434]. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 6 11:12:13 2009 Return-Path: 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 7EC5E3A69B2; Tue, 6 Jan 2009 11:12:13 -0800 (PST) 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 9E5633A68B1; Tue, 6 Jan 2009 11:12:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.48 X-Spam-Level: X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 ZOKHSkskT4-9; Tue, 6 Jan 2009 11:12:11 -0800 (PST) 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 314C13A6848; Tue, 6 Jan 2009 11:12:11 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,220,1231131600"; d="scan'208";a="133253157" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jan 2009 14:11:56 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jan 2009 14:11:54 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Jan 2009 20:11:45 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-pce-of-06.txt to Proposed Standard Thread-Index: AclwKZXYvuKn+VDVRs+lmoPQLv9+AwACPXBQ From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-pce-of-06.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pce-of-05.txt Technical Summary The computation of one or a set of Traffic Engineering Label Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks, is subject to a set of one or more specific optimization criteria, referred to as objective functions (e.g. minimum cost path, widest path, etc.). In the Path Computation Element (PCE) architecture, a Path Computation Client (PCC) may want a path to be computed for one or more TE LSPs according to a specific objective function. Thus, the PCC needs the ability to instruct the PCE to use the correct objective function. Furthermore, it is possible that not all PCEs support the same set of objective functions, therefore it is useful for the PCC to be able to automatically discover the set of objective functions supported by each PCE. This document defines extensions to the PCE communication Protocol (PCEP) to allow a PCE to indicate the set of objective functions it supports. Extensions are also defined so that a PCC can indicate in a path computation request the required objective function, and so that a PCE can report in a path computation reply the objective function that was used for path computation. Working Group Summary No controversy reported (see PROTO writeup by Adrian Farrel). The I-D had a good level of review and discussion when it was first introduced. However, the last year has been quiet and the working group last call produced no comments. To be sure that there was support, the working group was asked to provide explicit review and approval. A number of participants responded supporting publication. Document Quality A private survey has revealed several implementations of the PCEP extensions defined in this document. Furthermore, there are several further extensions in the pipeline that make use of these extensions to enable new applications of PCE. The document was updated in response to IETF last call comments. Personnel Adrian Farrel is the Document Shepherd for this document. Ross Callon is the Responsible Area Director. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Thu Jan 8 06:05:12 2009 Return-Path: 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 83A8328C14D; Thu, 8 Jan 2009 06:05:12 -0800 (PST) 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 A06D428C15A; Thu, 8 Jan 2009 06:05:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.488 X-Spam-Level: X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 z93nBt-3cZvO; Thu, 8 Jan 2009 06:05:09 -0800 (PST) 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 1A81A28C14D; Thu, 8 Jan 2009 06:05:09 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,234,1231131600"; d="scan'208";a="157101791" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 08 Jan 2009 09:04:55 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Jan 2009 09:04:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 8 Jan 2009 15:04:53 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-pkix-rfc4055-update-01.txt to ProposedStandard Thread-Index: AclxBs/FjGFng0EjQnqMPRtw0+sOEgAkzSxw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-pkix-rfc4055-update-01.txt to ProposedStandard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pkix-rfc4055-update-01.tx t Technical Summary The subjectPublicKeyInfo field of an X.509 certificate carries three data items: an algorithm identifier, optional parameters, and a bit string that represents the public key. The parameters are specific to the algorithm and this field usually contains simple values needed to characterize the public key algorithm, e.g., the generator and modulus for Diffie-Hellman. However, X.509 does not constrain the scope of this parameters field. The ANSI X9.62 standards committee elected to use this field to express potentially complex limitations on how the public key in the certificate can be used, e.g., which key derivation functions can be applied to the bit string that results from a Diffie-Hellman key exchange. After considerable debate, the PKIX WG has decided to not express key usage constraints via this field. Instead, the WG decided that this sort of information should be expressed via use of distinct algorithm identifiers. (This decision is consistent with the observation that current products are not deigned to handle such key usage restrictions expressed in the subjectPublicKeyInfo field.) RFC 4055 such allowed restrictions to be placed in this field when used with RSA-OAEP. This document changes RFC 4055 to say that restrictions MUST NOT be present in the certificate's subjectPublicKeyInfo field when used with RSA-OAEP. It also replaces incorrect references to the publicKeyAlgorithm field with references to the subjectPublicKeyInfo field. As a result, this revised version of RFC 4055 will be consistent with the PKIX WG conventions adopted for this field. Working Group Summary This ID was discussed on the mailing list. A poll was taken on the PKIX list to determine whether the proposed change was the way forward and another poll was taken to determine whether the change would adversely affect implementations. The WG was in favor of the change and no implementer said it would adversely affect their products. Further, vendors that implement RFC 4055 support the change. Document Quality This document is a short update of an existing draft and is comparable in quality to its predecessor. Personnel Steve Kent is the document Shepherd. Pasi Eronen is the responsible security area director. RFC Editor Note Abstract: OLD: It updates the conventions for using the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm with the Public-Key Cryptography Standards (PKCS) #1 version 1.5 signature algorithm in the Internet X.509 Public Key Infrastructure (PKI). NEW: It updates the conventions for using the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key Infrastructure (PKI). Section 1: OLD: RFC 4055 specifies conventions for using the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm with the Public-Key Cryptography Standards (PKCS) #1 version 1.5 signature algorithm in the Internet X.509 Public Key Infrastructure (PKI). NEW: RFC 4055 specifies conventions for using the RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) key transport algorithm in the Internet X.509 Public Key Infrastructure (PKI). _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Thu Jan 8 08:59:28 2009 Return-Path: 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 C8C833A68E0; Thu, 8 Jan 2009 08:59:28 -0800 (PST) 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 8BA593A6863 for ; Thu, 8 Jan 2009 08:59:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.685 X-Spam-Level: X-Spam-Status: No, score=-0.685 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_40=-0.185] 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 n6o1vU83Tpsf for ; Thu, 8 Jan 2009 08:59:26 -0800 (PST) Received: from gumby.elbrysnetworks.com (mail.elbrysnetworks.com [64.140.243.164]) by core3.amsl.com (Postfix) with SMTP id 9F5033A6853 for ; Thu, 8 Jan 2009 08:59:26 -0800 (PST) Received: (qmail 13310 invoked from network); 8 Jan 2009 10:59:08 -0500 Received: from xpsuperdvd2.elbrysnetworks.com (HELO xpsuperdvd2) (172.22.18.93) by gumby.elbrysnetworks.com with SMTP; 8 Jan 2009 10:59:08 -0500 From: "David B. Nelson" To: "'Tschofenig, Hannes \(NSN - FI/Espoo\)'" Date: Thu, 8 Jan 2009 10:58:47 -0500 Organization: Elbrys Networks, Inc. Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-index: Aclxqf2p8QFE/3aeSwOxYd7pwwXjNw== Cc: aaa-doctors@ietf.org Subject: [AAA-DOCTORS] RADIUS / Diameter compatibility boilerplate? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Hannes, During the AAA Doctors lunch at IETF-73 you volunteered for the action item of drafting some boilerplate / template text for the required Diameter Considerations section of RADIUS I-Ds and RFCs. How is that coming along? Regards, Dave David B. Nelson Chief Software Architect Elbrys Networks, Inc. 75 Rochester Ave. Unit 3 Portsmouth, NH 03801 Voice: +1 603.570.2636 FAX: +1 603.766.0934 Skype: david_b_nelson _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Thu Jan 8 23:46:30 2009 Return-Path: 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 70DF43A695E; Thu, 8 Jan 2009 23:46:30 -0800 (PST) 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 DAD5C3A677E for ; Thu, 8 Jan 2009 23:46:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.422 X-Spam-Level: X-Spam-Status: No, score=-6.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 UxrWIrvBH9dD for ; Thu, 8 Jan 2009 23:46:28 -0800 (PST) Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id AD6BC3A65A5 for ; Thu, 8 Jan 2009 23:46:28 -0800 (PST) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n097jcF2025891; Fri, 9 Jan 2009 01:46:10 -0600 Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Jan 2009 09:45:52 +0200 Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by vaebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Jan 2009 09:45:51 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 9 Jan 2009 09:45:53 +0200 Message-ID: <1696498986EFEC4D9153717DA325CB7202DB124C@vaebe104.NOE.Nokia.com> In-Reply-To: <027AC6CC-D3C7-4B8F-AD82-DE622105D7AD@gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AAA-DOCTORS] New version of draft-ietf-dime-mip6-integrated Thread-Index: AclqaO0pcb5rSLNhRiGH8aDF6003+QHxNm5Q References: <1696498986EFEC4D9153717DA325CB7202A049A3@vaebe104.NOE.Nokia.com> <027AC6CC-D3C7-4B8F-AD82-DE622105D7AD@gmail.com> From: To: X-OriginalArrivalTime: 09 Jan 2009 07:45:51.0949 (UTC) FILETIME=[4B9E2FD0:01C9722E] X-Nokia-AV: Clean Cc: aaa-doctors@ietf.org, charliep@wichorus.com, kchowdhury@starentnetworks.com, julien.bournelle@orange-ftgroup.com Subject: Re: [AAA-DOCTORS] New version of draft-ietf-dime-mip6-integrated X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Jouni, Compared to version -11, this moves the MIP6-Feature-Vector and MIP6-Home-Link-Prefix attributes back to the >255 space. I think they should be as they were in version -11. Otherwise, this looks good. Best regards, Pasi > -----Original Message----- > From: ext jouni korhonen [mailto:jounikor@gmail.com] > Sent: 30 December, 2008 12:25 > To: Eronen Pasi (Nokia-NRC/Helsinki) > Cc: kchowdhury@starentnetworks.com; aaa-doctors@ietf.org; > julien.bournelle@orange-ftgroup.com; charliep@wichorus.com > Subject: Re: [AAA-DOCTORS] New version of > draft-ietf-dime-mip6-integrated > > Hi Pasi, all, > > According to my notes we have now converged to a common > understanding > on this I-D. I have prepared an update of the I-D that includes all > comments. See the following link for the diff (PDF) that summarizes > changes since the -10 that was submitted to the IESG: > http://www.tschofenig.priv.at/svn/draft-ietf-dime-mip6-integrated/dime-mip6-integrated-10-to-12-diff.pdf> > Does this revision match others' idea of the agreed on changes? > > Cheers, > Jouni > > > On Dec 18, 2008, at 7:41 PM, > > wrote: > > > Jouni Korhonen wrote: > > > >>> Looking back at the emails, the following things (not related to > >>> this RADIUS/Diameter topic) were still not handled in the > >>> -11 version: > >>> > >>> - Describing the semantics of the MIP6-Home-Link-Prefix in request > >>> messages. > >> > >> Would the following text in Section 4.2.4 work for you? > >> > >> Old: > >> > >> The HAAA MAY act as a central entity managing prefixes for MNs. > >> In this case, the HAAA returns the prefix allocated for the MN > >> and returns it the NAS. The NAS/ASP uses then, for example, > >> mechanisms described in > >> [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home > >> link prefix to the MN. > >> > >> New: > >> > >> The HAAA MAY act as a central entity managing prefixes for MNs. > >> In this case, the HAAA returns the prefix allocated for the MN > >> and returns it the NAS. The NAS/ASP uses then, for example, > >> mechanisms described in > >> [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home > >> link prefix to the MN. The NAS/ASP MAY propose a specific prefix > >> allocation to the HAAA by including the MIP6-Home-Link-Prefix > >> AVP in the request message. However, the HAAA is MAY override > >> the prefix allocation hint proposed by the NAS/AAA and return a > >> different prefix in the response message. > > > > Both this and Lionel's slightly edited version look OK to me. > > > >>> - If the message contains information about multiple HAs, > which home > >>> agent(s) the prefix(es) in MIP6-Home-Link-Prefix AVP(s) belong to. > >>> (One way to solve this would be to move it inside the Grouped AVP; > >>> another way would be to prohibit its use if the message contains > >>> multiple HAs; other solutions may be possible) > >> > >> Actually, I have a vague recollection that independent of number of > >> the HAs, there would be only one prefix. I cannot find anything to > >> back up this now, though. > >> > >> Thus, we could move the MIP6-Home-Link-Prefix AVP inside the MIP6- > >> Agent-Info AVP (in that case, we could actually consider using the > >> Framed-IPv6- Prefix AVP instead of the MIP6-Home-Link-Prefix > >> AVP). Or we could add text that says using the > MIP6-Home-Link-Prefix > >> AVP when there are multiple HAs does not make much sense. > > > > I slightly prefer moving it inside the grouped AVP. > > > > Best regards, > > Pasi > > _______________________________________________ > > 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 Jan 9 01:08:39 2009 Return-Path: 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 F24D728C0F5; Fri, 9 Jan 2009 01:08:38 -0800 (PST) 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 06B123A6A99 for ; Fri, 9 Jan 2009 01:08:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.453 X-Spam-Level: X-Spam-Status: No, score=-1.453 tagged_above=-999 required=5 tests=[AWL=1.145, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vB3IvHlwHSrX for ; Fri, 9 Jan 2009 01:08:36 -0800 (PST) Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id DEAE43A6B00 for ; Fri, 9 Jan 2009 01:08:35 -0800 (PST) Received: by bwz14 with SMTP id 14so28602855bwz.13 for ; Fri, 09 Jan 2009 01:08:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=TlZDqtkW0mPKrDadAw6vLLSbZXBjqiq6eKQFtskJJ8o=; b=cTdTKFZDIOqEVJ24ghWtQyVQ5ZtlE/E/v8l67C94u4Cyo159l/e0ESOkgjmEU+Iiy1 0x8bx2+MbV/3qZL/7gW4a7qlAuuvgnTsxq6axzeJYxrrpWh99lWUrYoXSm1wmsCp3qXH fqVe/Td34iI7s9onFH9V0ieB54c2TQqZF7h6w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=eSm9fuX6foad/W+Q0rycZ78mqZlc+F+fsbJNQCv7VsseLpaFh+XMUnO32buf4qkTjP PTOl9PL2tTdlyz0/QaJ12iAhwERGD/fB9uSVYMVMeFZA9JRpEUuk8LeSanIYrxplWXAn p0L0IPBI32/y8czFWUDymw/arxssS3GI8bvmU= Received: by 10.223.107.19 with SMTP id z19mr1673876fao.27.1231492100962; Fri, 09 Jan 2009 01:08:20 -0800 (PST) Received: by 10.223.108.211 with HTTP; Fri, 9 Jan 2009 01:08:20 -0800 (PST) Message-ID: <3fe59bfe0901090108o61c91844qdcf7664f1d938933@mail.gmail.com> Date: Fri, 9 Jan 2009 11:08:20 +0200 From: "jouni korhonen" To: Pasi.Eronen@nokia.com In-Reply-To: <1696498986EFEC4D9153717DA325CB7202DB124C@vaebe104.NOE.Nokia.com> MIME-Version: 1.0 References: <1696498986EFEC4D9153717DA325CB7202A049A3@vaebe104.NOE.Nokia.com> <027AC6CC-D3C7-4B8F-AD82-DE622105D7AD@gmail.com> <1696498986EFEC4D9153717DA325CB7202DB124C@vaebe104.NOE.Nokia.com> Cc: aaa-doctors@ietf.org, charliep@wichorus.com, kchowdhury@starentnetworks.com, jounikor@gmail.com, julien.bournelle@orange-ftgroup.com Subject: Re: [AAA-DOCTORS] New version of draft-ietf-dime-mip6-integrated X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1763113735==" Sender: aaa-doctors-bounces@ietf.org Errors-To: aaa-doctors-bounces@ietf.org --===============1763113735== Content-Type: multipart/alternative; boundary="----=_Part_252412_24368926.1231492100955" ------=_Part_252412_24368926.1231492100955 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Pasi, Right, I'll move the two AVPs back to <256 space. Will submit a revision soon. Cheers, Jouni On Fri, Jan 9, 2009 at 9:45 AM, wrote: > Jouni, > > Compared to version -11, this moves the MIP6-Feature-Vector and > MIP6-Home-Link-Prefix attributes back to the >255 space. > I think they should be as they were in version -11. > > Otherwise, this looks good. > > Best regards, > Pasi > > > -----Original Message----- > > From: ext jouni korhonen [mailto:jounikor@gmail.com] > > Sent: 30 December, 2008 12:25 > > To: Eronen Pasi (Nokia-NRC/Helsinki) > > Cc: kchowdhury@starentnetworks.com; aaa-doctors@ietf.org; > > julien.bournelle@orange-ftgroup.com; charliep@wichorus.com > > Subject: Re: [AAA-DOCTORS] New version of > > draft-ietf-dime-mip6-integrated > > > > Hi Pasi, all, > > > > According to my notes we have now converged to a common > > understanding > > on this I-D. I have prepared an update of the I-D that includes all > > comments. See the following link for the diff (PDF) that summarizes > > changes since the -10 that was submitted to the IESG: > > > http://www.tschofenig.priv.at/svn/draft-ietf-dime-mip6-integrated/dime-mip6-integrated-10-to-12-diff.pdf > > > > > Does this revision match others' idea of the agreed on changes? > > > > Cheers, > > Jouni > > > > > > On Dec 18, 2008, at 7:41 PM, > > > > wrote: > > > > > Jouni Korhonen wrote: > > > > > >>> Looking back at the emails, the following things (not related to > > >>> this RADIUS/Diameter topic) were still not handled in the > > >>> -11 version: > > >>> > > >>> - Describing the semantics of the MIP6-Home-Link-Prefix in request > > >>> messages. > > >> > > >> Would the following text in Section 4.2.4 work for you? > > >> > > >> Old: > > >> > > >> The HAAA MAY act as a central entity managing prefixes for MNs. > > >> In this case, the HAAA returns the prefix allocated for the MN > > >> and returns it the NAS. The NAS/ASP uses then, for example, > > >> mechanisms described in > > >> [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home > > >> link prefix to the MN. > > >> > > >> New: > > >> > > >> The HAAA MAY act as a central entity managing prefixes for MNs. > > >> In this case, the HAAA returns the prefix allocated for the MN > > >> and returns it the NAS. The NAS/ASP uses then, for example, > > >> mechanisms described in > > >> [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home > > >> link prefix to the MN. The NAS/ASP MAY propose a specific prefix > > >> allocation to the HAAA by including the MIP6-Home-Link-Prefix > > >> AVP in the request message. However, the HAAA is MAY override > > >> the prefix allocation hint proposed by the NAS/AAA and return a > > >> different prefix in the response message. > > > > > > Both this and Lionel's slightly edited version look OK to me. > > > > > >>> - If the message contains information about multiple HAs, > > which home > > >>> agent(s) the prefix(es) in MIP6-Home-Link-Prefix AVP(s) belong to. > > >>> (One way to solve this would be to move it inside the Grouped AVP; > > >>> another way would be to prohibit its use if the message contains > > >>> multiple HAs; other solutions may be possible) > > >> > > >> Actually, I have a vague recollection that independent of number of > > >> the HAs, there would be only one prefix. I cannot find anything to > > >> back up this now, though. > > >> > > >> Thus, we could move the MIP6-Home-Link-Prefix AVP inside the MIP6- > > >> Agent-Info AVP (in that case, we could actually consider using the > > >> Framed-IPv6- Prefix AVP instead of the MIP6-Home-Link-Prefix > > >> AVP). Or we could add text that says using the > > MIP6-Home-Link-Prefix > > >> AVP when there are multiple HAs does not make much sense. > > > > > > I slightly prefer moving it inside the grouped AVP. > > > > > > Best regards, > > > Pasi > > > _______________________________________________ > > > 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 > ------=_Part_252412_24368926.1231492100955 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Pasi,

Right, I'll move the two AVPs back to <256 space. Will submit a revision soon.

Cheers,
    Jouni

On Fri, Jan 9, 2009 at 9:45 AM, <Pasi.Eronen@nokia.com> wrote:
Jouni,

Compared to version -11, this moves the MIP6-Feature-Vector and
MIP6-Home-Link-Prefix attributes back to the >255 space.
I think they should be as they were in version -11.

Otherwise, this looks good.

Best regards,
Pasi

> -----Original Message-----
> From: ext jouni korhonen [mailto:jounikor@gmail.com]
> Sent: 30 December, 2008 12:25
> To: Eronen Pasi (Nokia-NRC/Helsinki)
> Cc: kchowdhury@starentnetworks.com; aaa-doctors@ietf.org;
> julien.bournelle@orange-ftgroup.com; charliep@wichorus.com
> Subject: Re: [AAA-DOCTORS] New version of
> draft-ietf-dime-mip6-integrated
>
> Hi Pasi, all,
>
> According to my notes we have now converged to a common
> understanding
> on this I-D. I have prepared an update of the I-D that includes all
> comments. See the following link for the diff (PDF) that summarizes
> changes since the -10 that was submitted to the IESG:
> http://www.tschofenig.priv.at/svn/draft-ietf-dime-mip6-integrated/dime-mip6-integrated-10-to-12-diff.pdf>

> Does this revision match others' idea of the agreed on changes?
>
> Cheers,
>       Jouni
>
>
> On Dec 18, 2008, at 7:41 PM, <Pasi.Eronen@nokia.com>
> <Pasi.Eronen@nokia.com
>  > wrote:
>
> > Jouni Korhonen wrote:
> >
> >>> Looking back at the emails, the following things (not related to
> >>> this RADIUS/Diameter topic) were still not handled in the
> >>> -11 version:
> >>>
> >>> - Describing the semantics of the MIP6-Home-Link-Prefix in request
> >>> messages.
> >>
> >> Would the following text in Section 4.2.4 work for you?
> >>
> >> Old:
> >>
> >>    The HAAA MAY act as a central entity managing prefixes for MNs.
> >>    In this case, the HAAA returns the prefix allocated for the MN
> >>    and returns it the NAS.  The NAS/ASP uses then, for example,
> >>    mechanisms described in
> >>    [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home
> >>    link prefix to the MN.
> >>
> >> New:
> >>
> >>    The HAAA MAY act as a central entity managing prefixes for MNs.
> >>    In this case, the HAAA returns the prefix allocated for the MN
> >>    and returns it the NAS.  The NAS/ASP uses then, for example,
> >>    mechanisms described in
> >>    [I-D.ietf-mip6-bootstrapping-integrated-dhc] to deliver the home
> >>    link prefix to the MN. The NAS/ASP MAY propose a specific prefix
> >>    allocation to the HAAA by including the MIP6-Home-Link-Prefix
> >>    AVP in the request message. However, the HAAA is MAY override
> >>    the prefix allocation hint proposed by the NAS/AAA and return a
> >>    different prefix in the response message.
> >
> > Both this and Lionel's slightly edited version look OK to me.
> >
> >>> - If the message contains information about multiple HAs,
> which home
> >>> agent(s) the prefix(es) in MIP6-Home-Link-Prefix AVP(s) belong to.
> >>> (One way to solve this would be to move it inside the Grouped AVP;
> >>> another way would be to prohibit its use if the message contains
> >>> multiple HAs; other solutions may be possible)
> >>
> >> Actually, I have a vague recollection that independent of number of
> >> the HAs, there would be only one prefix. I cannot find anything to
> >> back up this now, though.
> >>
> >> Thus, we could move the MIP6-Home-Link-Prefix AVP inside the MIP6-
> >> Agent-Info AVP (in that case, we could actually consider using the
> >> Framed-IPv6- Prefix AVP instead of the MIP6-Home-Link-Prefix
> >> AVP). Or we could add text that says using the
> MIP6-Home-Link-Prefix
> >> AVP when there are multiple HAs does not make much sense.
> >
> > I slightly prefer moving it inside the grouped AVP.
> >
> > Best regards,
> > Pasi
> > _______________________________________________
> > 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

------=_Part_252412_24368926.1231492100955-- --===============1763113735== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors --===============1763113735==-- From aaa-doctors-bounces@ietf.org Fri Jan 9 01:25:57 2009 Return-Path: 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 2DA673A69D7; Fri, 9 Jan 2009 01:25:57 -0800 (PST) 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 EC9463A69BC; Fri, 9 Jan 2009 01:25:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.493 X-Spam-Level: X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, 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 iIzHbDlRKZb4; Fri, 9 Jan 2009 01:25:55 -0800 (PST) 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 4610E3A67BD; Fri, 9 Jan 2009 01:25:53 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,238,1231131600"; d="scan'208";a="133563260" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Jan 2009 04:25:35 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Jan 2009 04:25:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 9 Jan 2009 10:25:20 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for January 15, 2009 Telechat Thread-Index: Aclx5ekBFge10dt9RXaIDY0r/3RPJQAVVytA From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for January 15, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 1/15 IESG telechat. Please send all comments and concerns related to the documents in review until Wednesday 1/14 COB the latest. 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-pce-of-06.txt Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) (Proposed Standard) - 1 of 3 Token: Ross Callon o draft-ietf-pce-dste-02.txt Diff-Serv Aware Class Type Object for Path Computation Element Communication Protocol (Proposed Standard) - 2 of 3 Token: Ross Callon o draft-ietf-sieve-managesieve-06.txt A Protocol for Remotely Managing Sieve Scripts (Proposed Standard) - 3 of 3 Token: Lisa Dusseault 2.1.2 Returning Item o draft-ietf-dkim-ssp-08.txt DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) (Proposed Standard) - 1 of 1 Note: Document shepherd is Stephen Farrell (stephen.farrell@cs.tcd.ie) Token: Pasi Eronen 2.2 Individual Submissions 2.2.1 New Item o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 1 of 1 Token: Russ Housley 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-ospf-manet-mdr-04.txt MANET Extension of OSPF using CDS Flooding (Experimental) - 1 of 3 Token: David Ward o draft-ietf-ospf-manet-mpr-03.txt OSPF MPR Extension for Ad Hoc Networks (Experimental) - 2 of 3 Token: David Ward o draft-ietf-ospf-manet-or-01.txt Extensions to OSPF to Support Mobile Ad Hoc Networking (Experimental) - 3 of 3 Token: David Ward _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 10 05:47:25 2009 Return-Path: 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 121DC3A68EB; Sat, 10 Jan 2009 05:47:25 -0800 (PST) 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 1676D3A68EB for ; Sat, 10 Jan 2009 05:47:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.245 X-Spam-Level: X-Spam-Status: No, score=-2.245 tagged_above=-999 required=5 tests=[AWL=0.354, 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 tXbmhfG-aKLV for ; Sat, 10 Jan 2009 05:47:22 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id D48F43A67DA for ; Sat, 10 Jan 2009 05:47:21 -0800 (PST) Received: (qmail invoked by alias); 10 Jan 2009 13:47:07 -0000 Received: from a91-154-105-43.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.105.43] by mail.gmx.net (mp043) with SMTP; 10 Jan 2009 14:47:07 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX195+XJMtvR5YeeNU41X01MnGrJ2Do4lBdIAA8L6+5 mcCuO0rYnc/g1p From: "Hannes Tschofenig" To: "'Hannes Tschofenig'" , , References: <009b01c96ea9$18b7d900$0201a8c0@nsnintra.net> <027601c9700b$516d5280$0201a8c0@nsnintra.net> Date: Sat, 10 Jan 2009 15:47:37 +0200 Message-ID: <023901c9732a$00225340$0201a8c0@nsnintra.net> MIME-Version: 1.0 X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acluo+D6K8UH3xGqQcuqhiSzW5v0mAABSF2QAFh5+IAAx8ICgA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: <027601c9700b$516d5280$0201a8c0@nsnintra.net> Importance: High X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58 Cc: aaa-doctors@ietf.org Subject: Re: [AAA-DOCTORS] FW: Review of "Software Hub and Spoke Framework"? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 I haven't heard back from you, guys? Please confirm that you are going to review the document! >-----Original Message----- >From: aaa-doctors-bounces@ietf.org >[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of Hannes Tschofenig >Sent: 06 January, 2009 16:30 >To: amuhanna@nortel.com; john.zhao@huawei.com >Cc: aaa-doctors@ietf.org >Subject: Re: [AAA-DOCTORS] FW: Review of "Software Hub and >Spoke Framework"? > >John and Ahmad, > >could you review the document by the end of this week? > >Ciao >Hannes > >>-----Original Message----- >>From: aaa-doctors-bounces@ietf.org >>[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of ext Hannes >>Tschofenig >>Sent: 04 January, 2009 22:15 >>To: aaa-doctors@ietf.org >>Subject: [AAA-DOCTORS] FW: Review of "Software Hub and Spoke >>Framework"? >> >>Bernard ran into this document. I guess that this would be >something to >>review for us as well. >>Who volunteers? >> >> >> >>________________________________ >> >> From: owner-radiusext@ops.ietf.org >>[mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba >> Sent: 04 January, 2009 21:36 >> To: radiusext@ops.ietf.org >> Subject: Review of "Software Hub and Spoke Framework"? >> >> >> The document "'Softwire Hub & Spoke Deployment >Framework with L2TPv2" >>has gone >> to IETF last call: >> >>http://www.ietf.org/mail-archive/web/ietf-announce/current/msg0 >>5459.html >> >> Has anyone taken a look at this document? It is available here: >> >>http://tools.ietf.org/html/draft-ietf-softwire-hs-framework-l2tpv2 >> >> The document does seem to deal with a number of >AAA-related issues, >>including >> limitations in RADIUS accounting. >> >> >> >> >> >> >> >>_______________________________________________ >>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 > _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 10 06:09:09 2009 Return-Path: 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 DEB4D28C18A; Sat, 10 Jan 2009 06:09:09 -0800 (PST) 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 7409428C18A for ; Sat, 10 Jan 2009 06:09:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.252 X-Spam-Level: X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[AWL=0.347, 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 DZSdyaw5VIHx for ; Sat, 10 Jan 2009 06:09:08 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id D9A423A68DF for ; Sat, 10 Jan 2009 06:09:07 -0800 (PST) Received: (qmail invoked by alias); 10 Jan 2009 14:02:13 -0000 Received: from a91-154-105-43.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.105.43] by mail.gmx.net (mp008) with SMTP; 10 Jan 2009 15:02:13 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX1930pBJSM13Hh5OkntGjMucufe8dIChKkhC5tbn6P r4jXC+EJ1L+l7W From: "Hannes Tschofenig" To: "'David B. Nelson'" , "Tschofenig, Hannes \(NSN - FI/Espoo\)" References: Date: Sat, 10 Jan 2009 16:02:43 +0200 Message-ID: <023a01c9732c$1c3ec200$0201a8c0@nsnintra.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aclxqf2p8QFE/3aeSwOxYd7pwwXjNwBgAV4A X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: X-Y-GMX-Trusted: 0 X-FuHaFi: 0.52 Cc: aaa-doctors@ietf.org, dime@ietf.org Subject: Re: [AAA-DOCTORS] RADIUS / Diameter compatibility boilerplate? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Dave, Thanks for the reminder. Based on the discussion we had with Pasi in context of the MIPv6 integrated document I tried to figure out how far we are with the deployment of RADIUS - Diameter translation agents. I got feedback, which I will try to summarize (as mentioned in my recent DIME status update message). Why does that activity relate to the issue of the boilerplate? We are writing something in our documents with a certain model of interworking in mind. For some reason, this interworking does not exist in today's deployment (based on the feedback I received) and so far I haven't received evidence that it will exist in the future. So, here is my thinking: * RADIUS and Diameter are different protocols with different deployment stories. * The data types in RADIUS and Diameter are different. There is overlap but RADIUS offers fewer data types than Diameter. * The design considerations in Diameter are different to the one in RADIUS. A big difference is the fact that Diameter has the concept of applications and RADIUS doesn't have those (ignoring some tiny details). The above-mentioned aspect might lead to different designs in RADIUS and in Diameter when considering the deployment environment and the available protocol mechanisms. This makes translation more complex. Since there is very little translation done (other with legacy systems) this does not really matter that much. This makes me believe that there should not be a requirement to write RADIUS Diameter consideration sections in the document. If document authors want to include Diameter solution aspects into the same document then they can obviously do that. This is a pure document management task. However, they have to consider the entire range of Diameter design considerations and this may lead to the need to define a Diameter application and hence the previously short section might be rather long. In any case, a WGLC should be posted to the DIME mailing list if there are Diameter considerations in the document. Does this make sense? Feedback from the DIME group? Ciao Hannes >-----Original Message----- >From: aaa-doctors-bounces@ietf.org >[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of David B. Nelson >Sent: 08 January, 2009 17:59 >To: 'Tschofenig, Hannes (NSN - FI/Espoo)' >Cc: aaa-doctors@ietf.org >Subject: [AAA-DOCTORS] RADIUS / Diameter compatibility boilerplate? > >Hi Hannes, > >During the AAA Doctors lunch at IETF-73 you volunteered for >the action item of drafting some boilerplate / template text >for the required Diameter Considerations section of RADIUS >I-Ds and RFCs. How is that coming along? > >Regards, > >Dave > >David B. Nelson >Chief Software Architect >Elbrys Networks, Inc. >75 Rochester Ave. Unit 3 >Portsmouth, NH 03801 >Voice: +1 603.570.2636 >FAX: +1 603.766.0934 >Skype: david_b_nelson > > >_______________________________________________ >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 Sat Jan 10 06:18:05 2009 Return-Path: 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 4EA373A6A1E; Sat, 10 Jan 2009 06:18:05 -0800 (PST) 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 B8AF328C19E for ; Sat, 10 Jan 2009 06:18:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.733 X-Spam-Level: X-Spam-Status: No, score=-1.733 tagged_above=-999 required=5 tests=[AWL=0.866, 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 g1I43gkEXC8C for ; Sat, 10 Jan 2009 06:18:02 -0800 (PST) Received: from QMTA07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 948613A6A19 for ; Sat, 10 Jan 2009 06:18:02 -0800 (PST) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA07.westchester.pa.mail.comcast.net with comcast id 1ovy1b00r0EZKEL57qHpE8; Sat, 10 Jan 2009 14:17:49 +0000 Received: from NEWTON603 ([71.232.143.198]) by OMTA01.westchester.pa.mail.comcast.net with comcast id 1qHp1b0034H2mdz3MqHpRC; Sat, 10 Jan 2009 14:17:49 +0000 From: "Dave Nelson" To: , , References: <023a01c9732c$1c3ec200$0201a8c0@nsnintra.net> Date: Sat, 10 Jan 2009 09:17:58 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: <023a01c9732c$1c3ec200$0201a8c0@nsnintra.net> Thread-Index: Aclxqf2p8QFE/3aeSwOxYd7pwwXjNwBgAV4AAACuiOA= Subject: Re: [AAA-DOCTORS] [Dime] RADIUS / Diameter compatibilityboilerplate? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Hannes, I've added RADEXT to the distribution, as well. I agree, based on your summary of the state of the art of translation gateways and the other issues you highlight, that the simple Diameter Considerations text that we've been using, modeled after the assumptions of the Diameter NAS Application (RFC 4005), is a bit misleading. If the recommendation turns out to be that there should not be simplistic RADIUS to Diameter interoperability, then I think there are two follow up issues: (1) Guidance on when Diameter clients and servers can and cannot use (or re-use) RADIUS attributes in the legacy <255 ID space. (2) A prohibition on Diameter documents defining and new AVPs in the legacy <255 ID space. I think there was an assumption that any attributes/AVPs in the legacy ID space would be interchangeable, is a simple fashion. Regards, Dave -----Original Message----- From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Hannes Tschofenig Sent: Saturday, January 10, 2009 9:03 AM To: 'David B. Nelson'; Tschofenig, Hannes (NSN - FI/Espoo) Cc: aaa-doctors@ietf.org; dime@ietf.org Subject: Re: [Dime] [AAA-DOCTORS] RADIUS / Diameter compatibilityboilerplate? Hi Dave, Thanks for the reminder. Based on the discussion we had with Pasi in context of the MIPv6 integrated document I tried to figure out how far we are with the deployment of RADIUS - Diameter translation agents. I got feedback, which I will try to summarize (as mentioned in my recent DIME status update message). Why does that activity relate to the issue of the boilerplate? We are writing something in our documents with a certain model of interworking in mind. For some reason, this interworking does not exist in today's deployment (based on the feedback I received) and so far I haven't received evidence that it will exist in the future. So, here is my thinking: * RADIUS and Diameter are different protocols with different deployment stories. * The data types in RADIUS and Diameter are different. There is overlap but RADIUS offers fewer data types than Diameter. * The design considerations in Diameter are different to the one in RADIUS. A big difference is the fact that Diameter has the concept of applications and RADIUS doesn't have those (ignoring some tiny details). The above-mentioned aspect might lead to different designs in RADIUS and in Diameter when considering the deployment environment and the available protocol mechanisms. This makes translation more complex. Since there is very little translation done (other with legacy systems) this does not really matter that much. This makes me believe that there should not be a requirement to write RADIUS Diameter consideration sections in the document. If document authors want to include Diameter solution aspects into the same document then they can obviously do that. This is a pure document management task. However, they have to consider the entire range of Diameter design considerations and this may lead to the need to define a Diameter application and hence the previously short section might be rather long. In any case, a WGLC should be posted to the DIME mailing list if there are Diameter considerations in the document. Does this make sense? Feedback from the DIME group? Ciao Hannes >-----Original Message----- >From: aaa-doctors-bounces@ietf.org >[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of David B. Nelson >Sent: 08 January, 2009 17:59 >To: 'Tschofenig, Hannes (NSN - FI/Espoo)' >Cc: aaa-doctors@ietf.org >Subject: [AAA-DOCTORS] RADIUS / Diameter compatibility boilerplate? > >Hi Hannes, > >During the AAA Doctors lunch at IETF-73 you volunteered for >the action item of drafting some boilerplate / template text >for the required Diameter Considerations section of RADIUS >I-Ds and RFCs. How is that coming along? _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 10 06:36:38 2009 Return-Path: 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 E743D3A6944; Sat, 10 Jan 2009 06:36:38 -0800 (PST) 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 0BE3728C19E for ; Sat, 10 Jan 2009 06:36:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.265 X-Spam-Level: X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[AWL=0.334, 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 tiPmpaa0oKcV for ; Sat, 10 Jan 2009 06:36:37 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 6FFCD3A67D7 for ; Sat, 10 Jan 2009 06:36:36 -0800 (PST) Received: (qmail invoked by alias); 10 Jan 2009 14:29:42 -0000 Received: from a91-154-105-43.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.105.43] by mail.gmx.net (mp045) with SMTP; 10 Jan 2009 15:29:42 +0100 X-Authenticated: #29516787 X-Provags-ID: V01U2FsdGVkX19kZIYvLVdkyMIoS2lR3eWaheECPb4gyIwX8k6iD5 gZqpnjSwZzV3d4 From: "Hannes Tschofenig" To: "'Dave Nelson'" , , , References: <023a01c9732c$1c3ec200$0201a8c0@nsnintra.net> Date: Sat, 10 Jan 2009 16:30:13 +0200 Message-ID: <023c01c9732f$f3654fd0$0201a8c0@nsnintra.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Aclxqf2p8QFE/3aeSwOxYd7pwwXjNwBgAV4AAACuiOAAAHxgMA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 In-Reply-To: X-Y-GMX-Trusted: 0 X-FuHaFi: 0.5 Subject: Re: [AAA-DOCTORS] [Dime] RADIUS / Diameter compatibilityboilerplate? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Dave, There isn't too much space left in the <255 ID space and hence that consideration might not be too relevant in the future. I would not restrict the possibility to allocate RADIUS attributes (for example from the extended attribute space) in a Diameter document or todo Diameter AVP code allocation in a RADIUS document. The problem is that a more detailed investigation about this subject will take some time. Do you have that time? Ciao Hannes >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >Behalf Of Dave Nelson >Sent: 10 January, 2009 16:18 >To: aaa-doctors@ietf.org; dime@ietf.org; radiusext@ops.ietf.org >Subject: Re: [Dime] [AAA-DOCTORS] RADIUS / Diameter >compatibilityboilerplate? > >Hi Hannes, > >I've added RADEXT to the distribution, as well. > >I agree, based on your summary of the state of the art of >translation gateways and the other issues you highlight, that >the simple Diameter Considerations text that we've been using, >modeled after the assumptions of the Diameter NAS Application >(RFC 4005), is a bit misleading. > >If the recommendation turns out to be that there should not be >simplistic RADIUS to Diameter interoperability, then I think >there are two follow up >issues: > >(1) Guidance on when Diameter clients and servers can and >cannot use (or >re-use) RADIUS attributes in the legacy <255 ID space. > >(2) A prohibition on Diameter documents defining and new AVPs >in the legacy ><255 ID space. > >I think there was an assumption that any attributes/AVPs in >the legacy ID space would be interchangeable, is a simple fashion. > >Regards, > >Dave > >-----Original Message----- >From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On >Behalf Of Hannes Tschofenig >Sent: Saturday, January 10, 2009 9:03 AM >To: 'David B. Nelson'; Tschofenig, Hannes (NSN - FI/Espoo) >Cc: aaa-doctors@ietf.org; dime@ietf.org >Subject: Re: [Dime] [AAA-DOCTORS] RADIUS / Diameter >compatibilityboilerplate? > >Hi Dave, > >Thanks for the reminder. > >Based on the discussion we had with Pasi in context of the >MIPv6 integrated document I tried to figure out how far we are >with the deployment of RADIUS >- Diameter translation agents. > >I got feedback, which I will try to summarize (as mentioned in >my recent DIME status update message). > >Why does that activity relate to the issue of the boilerplate? >We are writing something in our documents with a certain model >of interworking in mind. For some reason, this interworking >does not exist in today's deployment (based on the feedback I >received) and so far I haven't received evidence that it will >exist in the future. > >So, here is my thinking: > >* RADIUS and Diameter are different protocols with different >deployment stories. > >* The data types in RADIUS and Diameter are different. There >is overlap but RADIUS offers fewer data types than Diameter. > >* The design considerations in Diameter are different to the >one in RADIUS. >A big difference is the fact that Diameter has the concept of >applications and RADIUS doesn't have those (ignoring some tiny >details). > >The above-mentioned aspect might lead to different designs in >RADIUS and in Diameter when considering the deployment >environment and the available protocol mechanisms. > >This makes translation more complex. Since there is very >little translation done (other with legacy systems) this does >not really matter that much. > >This makes me believe that there should not be a requirement >to write RADIUS Diameter consideration sections in the document. > >If document authors want to include Diameter solution aspects >into the same document then they can obviously do that. This >is a pure document management task. However, they have to >consider the entire range of Diameter design considerations >and this may lead to the need to define a Diameter application >and hence the previously short section might be rather long. > >In any case, a WGLC should be posted to the DIME mailing list >if there are Diameter considerations in the document. > >Does this make sense? Feedback from the DIME group? > >Ciao >Hannes > >>-----Original Message----- >>From: aaa-doctors-bounces@ietf.org >>[mailto:aaa-doctors-bounces@ietf.org] On Behalf Of David B. Nelson >>Sent: 08 January, 2009 17:59 >>To: 'Tschofenig, Hannes (NSN - FI/Espoo)' >>Cc: aaa-doctors@ietf.org >>Subject: [AAA-DOCTORS] RADIUS / Diameter compatibility boilerplate? >> >>Hi Hannes, >> >>During the AAA Doctors lunch at IETF-73 you volunteered for >the action >>item of drafting some boilerplate / template text for the required >>Diameter Considerations section of RADIUS I-Ds and RFCs. How is that >>coming along? > > >_______________________________________________ >DiME mailing list >DiME@ietf.org >https://www.ietf.org/mailman/listinfo/dime > _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 10 06:48:46 2009 Return-Path: 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 033E628C14C; Sat, 10 Jan 2009 06:48:46 -0800 (PST) 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 B305328C10C for ; Sat, 10 Jan 2009 06:48:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.789 X-Spam-Level: X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[AWL=0.810, 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 2ZvfmOuTHpxo for ; Sat, 10 Jan 2009 06:48:44 -0800 (PST) Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id BD17B3A6980 for ; Sat, 10 Jan 2009 06:48:43 -0800 (PST) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA09.westchester.pa.mail.comcast.net with comcast id 1opp1b0050EZKEL59qoX5Y; Sat, 10 Jan 2009 14:48:31 +0000 Received: from NEWTON603 ([71.232.143.198]) by OMTA01.westchester.pa.mail.comcast.net with comcast id 1qoV1b00T4H2mdz3MqoV9x; Sat, 10 Jan 2009 14:48:30 +0000 From: "Dave Nelson" To: , , References: <023a01c9732c$1c3ec200$0201a8c0@nsnintra.net> <023c01c9732f$f3654fd0$0201a8c0@nsnintra.net> Date: Sat, 10 Jan 2009 09:48:39 -0500 Message-ID: <281A3B25382A4F96A5204602866D7501@NEWTON603> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: <023c01c9732f$f3654fd0$0201a8c0@nsnintra.net> Thread-Index: Aclxqf2p8QFE/3aeSwOxYd7pwwXjNwBgAV4AAACuiOAAAHxgMAAAqDRg Subject: Re: [AAA-DOCTORS] [Dime] RADIUS / Diameter compatibilityboilerplate? X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Hannes Tschofenig writes... > There isn't too much space left in the <255 ID space and hence > that consideration might not be too relevant in the future. But it's another reason to restrict it right now -- to conserve such space for RADIUS applications. Unless, of course, the issues you've enumerated do not apply in a specific use case, for example when no new Diameter application is required and simple RADIUS data types suffice to the use case. > I would not restrict the possibility to allocate RADIUS attributes > (for example from the extended attribute space) in a Diameter > document or todo Diameter AVP code allocation in a RADIUS document. Well, RADIUS Extended Attributes is a different case to consider. Given the impedance mismatch between the Diameter AVP data model and the more restricted RADIUS Extended Attribute data model, there are some serious design issues. For example, to share these EAs/APVs the Diameter solution must be designed to fit within the RADIUS data model restrictions. > The problem is that a more detailed investigation about this > subject will take some time. Correct. > Do you have that time? Probably not. Nor do I have the required Diameter expertise. That's why I suggested a stop-gap "fix" in the form "just don't do that". :-) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 13 02:40:07 2009 Return-Path: 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 048903A69B3; Tue, 13 Jan 2009 02:40:07 -0800 (PST) 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 416B83A68B0; Tue, 13 Jan 2009 02:40:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.48 X-Spam-Level: X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 4s1CivAHt5c4; Tue, 13 Jan 2009 02:40:05 -0800 (PST) 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 0D4453A69BF; Tue, 13 Jan 2009 02:40:04 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,258,1231131600"; d="scan'208";a="157572035" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 13 Jan 2009 05:39:49 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Jan 2009 05:39:49 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 13 Jan 2009 11:39:32 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-l2tpext-tdm-06.txt to Proposed Standard Thread-Index: Acl0/nAFhfvMBpDJRGqSrtkq2cyz0QAa1huQ From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-l2tpext-tdm-06.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-tdm-06.txt Technical Summary This document describes transport of TDM bit-streams over the Layer Two Tunneling Protocol Version 3 (L2TPv3). It describes extensions of L2TPv3 for the setup and maintenance of structure-agnostic and structure-aware TDM Pseudowires, to transport TDM bit-streams over an IP network. Working Group Summary There is consensus in the WG to publish this document. Document Quality The l2tpext WG has reviewed this document. All concerns raised during review and last call have been addressed. Yaakov Stein performed a very detailed review during WGLC, with the conclusion that "this ID looks ready for publication" at . This document defines an application of L2TPv3 to transport another type of traffic, and is consistent with corresponding PWE3 documents. Carlos Pignataro is the WG shepherd for this document. RFC Editor Note Section 4., paragraph 12: EXPLANATION: Adding Error code of zero. OLD: 1. EC-TBD-1 - Bit Rate values disagree. 2. EC-TBD-2 - Different trunk types in the case of trunk- specific CESoPSN with CAS 3. EC-TBD-3 - Requested payload size too big or too small. 4. EC-TBD-4 - RTP header cannot be generated. 5. EC-TBD-5 - Requested timestamp clock frequency cannot be generated NEW: | 0 - No TDM PW parameter error 1. EC-TBD-1 - Bit Rate values disagree. 2. EC-TBD-2 - Different trunk types in the case of trunk- specific CESoPSN with CAS 3. EC-TBD-3 - Requested payload size too big or too small. 4. EC-TBD-4 - RTP header cannot be generated. 5. EC-TBD-5 - Requested timestamp clock frequency cannot be generated IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 13 02:41:03 2009 Return-Path: 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 8D7603A6956; Tue, 13 Jan 2009 02:41:02 -0800 (PST) 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 7A5DE3A69B3; Tue, 13 Jan 2009 02:40:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.181 X-Spam-Level: X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599, J_CHICKENPOX_93=0.6] 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 abh4XLa5rssY; Tue, 13 Jan 2009 02:40:58 -0800 (PST) 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 1E9E63A69A8; Tue, 13 Jan 2009 02:40:58 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,258,1231131600"; d="scan'208";a="157572168" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 13 Jan 2009 05:40:43 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Jan 2009 05:40:43 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 13 Jan 2009 11:39:57 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-ipdvb-sec-req-09.txt to Informational RFC Thread-Index: Acl0/mI3gzCuX6A7SaWPF/LNVsbnKQAbNkGg From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-ipdvb-sec-req-09.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipdvb-sec-req-09.txt Technical Summary This document provides a threat analysis and derives the security requirements when using the Transport Stream, TS, to support an Internet network-layer using the Unidirectional Lightweight Encapsulation (ULE) defined in RFC4326. The document also provides the motivation for link-layer security for a ULE Stream. A ULE Stream may be used to send IPv4 packets, IPv6 packets, and other Protocol Data Units (PDUs) to an arbitrarily large number of Receivers supporting unicast and/or multicast transmission. Working Group Summary This document builds on RFC 4326, and identifies a set of security-related topics that impact IP operation over a range of broadcast links supporting IP. Document Quality The IPDVB WG has reached consensus that this document is ready for publication as an informational RFC. This document does not define a protocol or new mechanism.RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 13 05:11:10 2009 Return-Path: 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 1DF1E3A69F7; Tue, 13 Jan 2009 05:11:10 -0800 (PST) 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 BD01E3A67EE; Tue, 13 Jan 2009 05:11:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.483 X-Spam-Level: X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 xGa+Li+Jtj+w; Tue, 13 Jan 2009 05:11:07 -0800 (PST) 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 958493A68F7; Tue, 13 Jan 2009 05:11:07 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,260,1231131600"; d="scan'208";a="157587616" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 13 Jan 2009 08:10:52 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 13 Jan 2009 08:10:50 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 13 Jan 2009 14:10:21 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-mext-nemo-mib-04.txt to Proposed Standard Thread-Index: Acl1eBVypL3gA2MBS+6wN5FEijNVUwACB2aQ From: "Romascanu, Dan (Dan)" To: , , "MIB Doctors (E-mail)" Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-mext-nemo-mib-04.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-mib-01.txt Technical Summary This memo defines a portion of the Management Information Base (MIB), the network mobility support (NEMO) MIB, for use with network management protocols in the Internet community. In particular, the NEMO MIB will be used to monitor and control a mobile ipv6 node with NEMO functionality. Working Group Summary The WG seems to agree in the need for this document and no-one seems to oppose to the document. Document Quality There are some vendors like Cisco working on this MIB development. In addition, KAME developers who implemented RFC-4295 (Mobile IPv6 MIB) probably will add this support as well. Alex Petrescu did a thorough review of the MIB. The document still needs review by a MIB doctor. Personnel The document shepherd for this document is Marcelo Bagnulo. The responsible AD is Jari Arkko. MIB doctor reviewer TBD. RFC Editor Note (Insert RFC Editor Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 09:13:57 2009 Return-Path: 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 0CE393A69B8; Wed, 14 Jan 2009 09:13:57 -0800 (PST) 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 BEA4F3A69B8 for ; Wed, 14 Jan 2009 09:13:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.486 X-Spam-Level: X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113, 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 xqPJp-KFqEnn for ; Wed, 14 Jan 2009 09:13:55 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id BE5503A6359 for ; Wed, 14 Jan 2009 09:13:54 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,263,1231131600"; d="scan'208";a="148586562" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 14 Jan 2009 12:13:39 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 14 Jan 2009 12:13:39 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 14 Jan 2009 18:13:37 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AAA / RADIUS content in draft-ietf-softwire-hs-framework-l2tpv2 Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZg== From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] AAA / RADIUS content in draft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 The Softwire Hub & Spoke Deployment Framework with L2TPv2 I-D http://www.ietf.org/internet-drafts/draft-ietf-softwire-hs-framework-l2t pv2-10.txt is on the agenda of the IESG telechat tomorrow for approval as a Proposed Standard. This document has a couple of sections (4.3, 9.1) that refer to AAA and RADIUS. Can somebody please have a look to the content of these sections? 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 Jan 14 09:33:19 2009 Return-Path: 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 C1CB93A69B8; Wed, 14 Jan 2009 09:33:19 -0800 (PST) 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 845FF3A69C4 for ; Wed, 14 Jan 2009 09:33:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.819 X-Spam-Level: X-Spam-Status: No, score=-1.819 tagged_above=-999 required=5 tests=[AWL=0.780, 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 D97xozmjoeEg for ; Wed, 14 Jan 2009 09:33:17 -0800 (PST) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 8D38D3A68D6 for ; Wed, 14 Jan 2009 09:33:17 -0800 (PST) Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA08.westchester.pa.mail.comcast.net with comcast id 3NzN1b00617dt5G58VZ3CM; Wed, 14 Jan 2009 17:33:03 +0000 Received: from NEWTON603 ([71.232.143.198]) by OMTA13.westchester.pa.mail.comcast.net with comcast id 3VZ31b0084H2mdz3ZVZ3ou; Wed, 14 Jan 2009 17:33:03 +0000 From: "Dave Nelson" To: "'Romascanu, Dan \(Dan\)'" , , References: Date: Wed, 14 Jan 2009 12:33:08 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+w Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Dan Romascanu writes... > Can somebody please have a look to the content of these sections? 4.3. Authentication Authorization Accounting RFC 2865 "Remote Authentication Dial In User Service (RADIUS)" [RFC2865]. DBN: Current document. Updated by RFC2868, RFC3575, RFC5080. RFC 2867 "RADIUS Accounting Modifications for Tunnel Protocol Support" [RFC2867]. DBN: Current document. RFC 2868 "RADIUS Attributes for Tunnel Protocol Support" [RFC2868]. DBN: Current document. RFC 3162 "RADIUS and IPv6" [RFC3162]. DBN: Current document. DBN: I can't attest that this list of references is necessary and sufficient to the requirements of Softwires, however. 9.1. RADIUS Accounting RADIUS Accounting for L2TP and PPP are documented (see Section 4.3). When deploying Softwire solutions, operators may experience difficulties to differentiate the address family of the traffic reported in accounting information from RADIUS. This problem and some potential solutions are described in [I-D.stevant-softwire-accounting]. DBN: I have not reviewed the referenced I-D, but it's quite likely that a lack of (standardized) RADIUS attributes capable of representing address families might inhibit the straightforward application of RADIUS Accounting. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 09:36:53 2009 Return-Path: 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 087F53A684E; Wed, 14 Jan 2009 09:36:53 -0800 (PST) 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 B099A3A684E for ; Wed, 14 Jan 2009 09:36:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.48 X-Spam-Level: X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119, 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 cfEmR2uozPEG for ; Wed, 14 Jan 2009 09:36:50 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 524FF3A676A for ; Wed, 14 Jan 2009 09:36:50 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,263,1231131600"; d="scan'208";a="148589582" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 14 Jan 2009 12:36:34 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 14 Jan 2009 12:36:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 14 Jan 2009 18:36:31 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+wAAB89nA= References: From: "Romascanu, Dan (Dan)" To: "Dave Nelson" , , Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 See also section 2.5 in the document. Dan > -----Original Message----- > From: Dave Nelson [mailto:d.b.nelson@comcast.net] > Sent: Wednesday, January 14, 2009 7:33 PM > To: Romascanu, Dan (Dan); aaa-doctors@ietf.org; radiusext@ops.ietf.org > Subject: RE: [AAA-DOCTORS] AAA / RADIUS content > indraft-ietf-softwire-hs-framework-l2tpv2 > > Dan Romascanu writes... > > > Can somebody please have a look to the content of these sections? > > > 4.3. Authentication Authorization Accounting > > RFC 2865 "Remote Authentication Dial In User Service (RADIUS)" > [RFC2865]. > > DBN: Current document. Updated by RFC2868, RFC3575, RFC5080. > > RFC 2867 "RADIUS Accounting Modifications for Tunnel Protocol > Support" [RFC2867]. > > DBN: Current document. > > RFC 2868 "RADIUS Attributes for Tunnel Protocol Support" > [RFC2868]. > > DBN: Current document. > > RFC 3162 "RADIUS and IPv6" [RFC3162]. > > DBN: Current document. > > DBN: I can't attest that this list of references is necessary > and sufficient to the requirements of Softwires, however. > > > 9.1. RADIUS Accounting > > RADIUS Accounting for L2TP and PPP are documented (see > Section 4.3). > > When deploying Softwire solutions, operators may experience > difficulties to differentiate the address family of the traffic > reported in accounting information from RADIUS. This problem and > some potential solutions are described in > [I-D.stevant-softwire-accounting]. > > DBN: I have not reviewed the referenced I-D, but it's quite > likely that a lack of (standardized) RADIUS attributes > capable of representing address families might inhibit the > straightforward application of RADIUS Accounting. > > > > _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 09:45:09 2009 Return-Path: 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 019213A686A; Wed, 14 Jan 2009 09:45:09 -0800 (PST) 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 836993A686A for ; Wed, 14 Jan 2009 09:45:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.829 X-Spam-Level: X-Spam-Status: No, score=-1.829 tagged_above=-999 required=5 tests=[AWL=0.770, 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 Ou7uw96EP13S for ; Wed, 14 Jan 2009 09:45:06 -0800 (PST) Received: from QMTA10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id A155C3A67B4 for ; Wed, 14 Jan 2009 09:45:06 -0800 (PST) Received: from OMTA05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA10.westchester.pa.mail.comcast.net with comcast id 3V3h1b05h0vyq2s5AVksc5; Wed, 14 Jan 2009 17:44:52 +0000 Received: from NEWTON603 ([71.232.143.198]) by OMTA05.westchester.pa.mail.comcast.net with comcast id 3Vkc1b00U4H2mdz3RVkcaU; Wed, 14 Jan 2009 17:44:36 +0000 From: "Dave Nelson" To: "'Romascanu, Dan \(Dan\)'" , , References: Date: Wed, 14 Jan 2009 12:44:57 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+wAAB89nAAAB01gA== Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 > See also section 2.5 in the document. 2.5. Authentication, Authorization and Accounting (AAA) L2TPv2 supports optional mutual Control Channel authentication and leverages the optional mutual PPP per-session authentication. L2TPv2 is well integrated with AAA solutions (such as RADIUS) for both authentication and authorization. Most L2TPv2 implementations available in the market support logging of authentication and authorization events. DBN: This paragraph contains an assertion about the integration of existing L2TPv2 implementations with RADIUS implementations. I'm not in a position to validate or refute that assertion from personal knowledge, but it seems reasonable on its face. L2TPv2 integration with RADIUS accounting (RADIUS Accounting extension for tunnel [RFC2867]) allows the collection and reporting of L2TPv2 Softwire usage statistics. DBN: Sure. RADIUS Accounting does support usage statistics reporting for all kinds of provisioned sessions, based on connect time and data transfer. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 10:19:31 2009 Return-Path: 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 B76393A69B8; Wed, 14 Jan 2009 10:19:31 -0800 (PST) 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 68F2F3A694D for ; Wed, 14 Jan 2009 10:19:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.474 X-Spam-Level: X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 2ZMyjMB1uBrq for ; Wed, 14 Jan 2009 10:19:29 -0800 (PST) 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 747E63A69C2 for ; Wed, 14 Jan 2009 10:19:27 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,263,1231131600"; d="scan'208";a="134065340" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 14 Jan 2009 13:19:10 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 14 Jan 2009 13:19:09 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 14 Jan 2009 19:19:08 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+wAAHyK3A= References: From: "Romascanu, Dan (Dan)" To: "Dave Nelson" , , Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Actually the whole section 8 is about 'Considerations about RADIUS Integration' so this needs review.. Dan > -----Original Message----- > From: Dave Nelson [mailto:d.b.nelson@comcast.net] > Sent: Wednesday, January 14, 2009 7:33 PM > To: Romascanu, Dan (Dan); aaa-doctors@ietf.org; radiusext@ops.ietf.org > Subject: RE: [AAA-DOCTORS] AAA / RADIUS content > indraft-ietf-softwire-hs-framework-l2tpv2 > > Dan Romascanu writes... > > > Can somebody please have a look to the content of these sections? > > > 4.3. Authentication Authorization Accounting > > RFC 2865 "Remote Authentication Dial In User Service (RADIUS)" > [RFC2865]. > > DBN: Current document. Updated by RFC2868, RFC3575, RFC5080. > > RFC 2867 "RADIUS Accounting Modifications for Tunnel Protocol > Support" [RFC2867]. > > DBN: Current document. > > RFC 2868 "RADIUS Attributes for Tunnel Protocol Support" > [RFC2868]. > > DBN: Current document. > > RFC 3162 "RADIUS and IPv6" [RFC3162]. > > DBN: Current document. > > DBN: I can't attest that this list of references is necessary > and sufficient to the requirements of Softwires, however. > > > 9.1. RADIUS Accounting > > RADIUS Accounting for L2TP and PPP are documented (see > Section 4.3). > > When deploying Softwire solutions, operators may experience > difficulties to differentiate the address family of the traffic > reported in accounting information from RADIUS. This problem and > some potential solutions are described in > [I-D.stevant-softwire-accounting]. > > DBN: I have not reviewed the referenced I-D, but it's quite > likely that a lack of (standardized) RADIUS attributes > capable of representing address families might inhibit the > straightforward application of RADIUS Accounting. > > > > _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 10:41:15 2009 Return-Path: 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 D9D493A68B2; Wed, 14 Jan 2009 10:41:15 -0800 (PST) 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 20AE23A68B2 for ; Wed, 14 Jan 2009 10:41:15 -0800 (PST) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID" X-Spam-Flag: NO X-Spam-Score: -1.989 X-Spam-Level: X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, J_CHICKENPOX_32=0.6] 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 EwPkdDyAb701 for ; Wed, 14 Jan 2009 10:41:13 -0800 (PST) Received: from bay0-omc2-s41.bay0.hotmail.com (bay0-omc2-s41.bay0.hotmail.com [65.54.246.177]) by core3.amsl.com (Postfix) with ESMTP id 8167E3A6813 for ; Wed, 14 Jan 2009 10:41:13 -0800 (PST) Received: from hotmail.com ([10.4.31.19]) by bay0-omc2-s41.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Jan 2009 10:40:58 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 14 Jan 2009 10:40:58 -0800 Message-ID: Received: from 131.107.0.105 by BLU137-DAV9.phx.gbl with DAV; Wed, 14 Jan 2009 18:40:54 +0000 X-Originating-IP: [131.107.0.105] X-Originating-Email: [bernard_aboba@hotmail.com] X-Sender: bernard_aboba@hotmail.com From: "Bernard Aboba" To: "'Dave Nelson'" , "'Romascanu, Dan \(Dan\)'" , , References: In-Reply-To: Date: Wed, 14 Jan 2009 10:40:52 -0800 Message-ID: <002c01c97677$a060bd10$e1223730$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+wAAB89nAAAB01gAABhNsw Content-Language: en-us X-OriginalArrivalTime: 14 Jan 2009 18:40:58.0534 (UTC) FILETIME=[A43BD460:01C97677] Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Presently, not all the scenarios described in the document are properly supported by AAA. As a result, the document redefines existing uses of RADIUS standard attributes, as well as suggesting implementation of documents that are currently still Internet Drafts. Section 8 updates several existing RADIUS standards RFCs, including: * RFC 2868, by defining new interpretations of the Tunnel-Client-Endpoint and Tunnel-Server-Endpoint attributes in situations where addressing attributes are not present. * RFC 2865, by defining new interpretations of the Framed-IP-Address and Framed-IP-Netmask attributes. * RFC 2866, by referencing draft-stevant-softwire-accounting, which redefines the format of the NAS-IP-Address attribute (which only supports IPv4 addresses; NAS-IPv6-Address is used to contain IPv6 addresses). Is this really appropriate for a framework document? >From draft-stevant-software-accounting-01.txt: A RADIUS accounting entry, as defined in [RFC2867], also includes the NASIPAddress attribute, which gives the IP address of the NAS used as the softwire endpoint. Based on this information, an operator can decide if this softwire is based on IPv4 or IPv6. In the case of provider only deploying IPv6 over IPv4 and IPv4 over IPv6 softwires, the nature of the traffic reported in the accounting information depends of the address family of NASIPAddress (if NASIPAddress is IPv4, accounted traffic is IPv6, if NASIPAddress is IPv6, accounted traffic is IPv4). However, this solution requires extra checking when building accounting report and obviously does not work in case of IPvX over IPvX softwires. 8.1. Softwire Endpoints 8.1.1. IPv6 Softwires If the RADIUS server includes a Framed-Interface-Id attribute [RFC3162], the Softwire Concentrator must send it to the Softwire Initiator in the Interface-Identifier field of its IPV6CP Configuration Request message. If the Framed-IPv6-Prefix attribute [RFC3162] is included, that prefix must be used in the router advertisements sent to the SI. If Framed-IPv6-Prefix is not present but Framed-IPv6-Pool is, the SC must choose a prefix with that pool to send RAs. If none of the attributes above are included but the AAA server returns the Tunnel-Client-Endpoint and Tunnel-Server-Endpoint attributes [RFC2868] with the correct address family, these must be used in the IPV6CP Interface-Identifier and for the Router Advertisements. [BA] The above paragraph defines new interpretations of these attributes. 8.1.2. IPv4 Softwires If the Framed-IP-Address attribute [RFC2865] is present, the Softwire Concentrator must provide that address to the Softwire Initiator during IPCP address negotiation. That is, when the Softwire Initiator requests an IP address from the Softwire Concentrator, the address provided should be the Framed-IP-Address. If the Framed-IP-Address attribute is not present and the Tunnel- Client-Endpoint and Tunnel-Server-Endpoint attributes [RFC2868] are present and of the correct address family, these should be used in the IPCP IP-Address configuration option. [BA] The above paragraph defines new interpretations of these attributes. 8.2. Delegated Prefixes 8.2.1. IPv6 Prefixes If the attribute Delegated-IPv6-Prefix [RFC4818] is present in the RADIUS Access-Accept message, it must be used by the Softwire Concentrator for the delegation of the IPv6 prefix. Since the prefix delegation is performed by DHCPv6 and the attribute is linked to a username, the SC must associate the DHCP Unique Identifier (DUID) of a DHCPv6 request to the tunnel it came from and its user. Interaction between RADIUS, PPP and DHCPv6 server may follow the mechanism proposed in [I-D.ietf-dhc-v6-relay-radius]. In this case, during the Softwire authentication phase, PPP collects the RADIUS attributes for the user such as Delegated-IPv6-Prefix. A specific DHCPv6 relay is assigned to the Softwire. The DHCPv6 relay fills in these attributes in the Relay agent RADIUS Attribute Option (RRAO) DHCPv6 option, before forwarding the DHCPv6 requests to the DHCPv6 server. [BA] The above paragraph makes what would appear to be a normative reference to an I-D. 8.2.2. IPv4 Prefixes The combination of the Framed-IP-Address and Framed-IP-Netmask attributes [RFC2865] may be used by the Softwire Concentrator to delegate an IPv4 prefix to the Softwire Initiator. [BA] The above paragraph defines new interpretations of these attributes. -----Original Message----- From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Dave Nelson Sent: Wednesday, January 14, 2009 9:45 AM To: 'Romascanu, Dan (Dan)'; aaa-doctors@ietf.org; radiusext@ops.ietf.org Subject: RE: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 > See also section 2.5 in the document. 2.5. Authentication, Authorization and Accounting (AAA) L2TPv2 supports optional mutual Control Channel authentication and leverages the optional mutual PPP per-session authentication. L2TPv2 is well integrated with AAA solutions (such as RADIUS) for both authentication and authorization. Most L2TPv2 implementations available in the market support logging of authentication and authorization events. DBN: This paragraph contains an assertion about the integration of existing L2TPv2 implementations with RADIUS implementations. I'm not in a position to validate or refute that assertion from personal knowledge, but it seems reasonable on its face. L2TPv2 integration with RADIUS accounting (RADIUS Accounting extension for tunnel [RFC2867]) allows the collection and reporting of L2TPv2 Softwire usage statistics. DBN: Sure. RADIUS Accounting does support usage statistics reporting for all kinds of provisioned sessions, based on connect time and data transfer. -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 14 10:53:55 2009 Return-Path: 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 A15AA3A69A9; Wed, 14 Jan 2009 10:53:55 -0800 (PST) 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 73A0D3A69A9 for ; Wed, 14 Jan 2009 10:53:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.854 X-Spam-Level: X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=0.745, 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 wvuO0Rm-kX5i for ; Wed, 14 Jan 2009 10:53:53 -0800 (PST) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 8A2323A686A for ; Wed, 14 Jan 2009 10:53:53 -0800 (PST) Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA08.westchester.pa.mail.comcast.net with comcast id 3Vbv1b00M16LCl058WtfCi; Wed, 14 Jan 2009 18:53:39 +0000 Received: from NEWTON603 ([71.232.143.198]) by OMTA06.westchester.pa.mail.comcast.net with comcast id 3WtN1b0024H2mdz3SWtNGY; Wed, 14 Jan 2009 18:53:22 +0000 From: "Dave Nelson" To: "'Romascanu, Dan \(Dan\)'" , , References: Date: Wed, 14 Jan 2009 13:53:44 -0500 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 In-Reply-To: Thread-Index: Acl2a3AtDPd3bpScQnKA0qVKoQtAZgAATX+wAAHyK3AAATAt0A== Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 > Actually the whole section 8 is about 'Considerations about RADIUS > Integration' so this needs review. Sorry, it would have behooved me to read the document rather than simply checking the sections you called out. Too much multi-tasking today. It looks like Bernard has covered this section in his post. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 18 00:57:24 2009 Return-Path: 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 8044228C16B; Sun, 18 Jan 2009 00:57:24 -0800 (PST) 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 425BE3A6924; Sun, 18 Jan 2009 00:57:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.47 X-Spam-Level: X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 0x1jhXIZ8Xqm; Sun, 18 Jan 2009 00:57:21 -0800 (PST) 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 9A91B3A67D2; Sun, 18 Jan 2009 00:57:20 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,283,1231131600"; d="scan'208,223";a="134403749" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Jan 2009 03:57:02 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jan 2009 03:57:00 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 18 Jan 2009 09:56:51 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: BOF requests and OPS open area meeting at IETF-74 Thread-Index: Acl5SrRgCTE+f0rqSoaYG501AQC32A== From: "Romascanu, Dan (Dan)" To: "ops-area (IETF)" Cc: aaa-doctors@ietf.org, "MIB Doctors \(E-mail\)" , ops-dir@ietf.org Subject: [AAA-DOCTORS] BOF requests and OPS open area meeting at IETF-74 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 >From the list of cut-off dates of IETF-74: > February 2, 2009 Monday - Cutoff date for requests to Area Directors to schedule BOFs at 17:00 PST (01:00 Tuesday, February 3 UTC/GMT). To request a BOF, please see instructions on Requesting a BOF. > February 9, 2009 Monday - Cutoff date for Area Directors to approve BOF requests at 17:00 PST (01:00 Tuesday, February 10 UTC/GMT). In between the IAB and IESG telechat that will review the BOF requests is scheduled for Thursday 2/5. If there are plans to submit any such request in the OPS Area, Ron and me would be interested to hear as soon as possible. Also, we have asked for a 2-hour meeting slot for the OPS Open Area meeting in San Francisco. Please send us any requests for mini-BOFs, presentations or items for discussion at the open area meeting. Thanks and Regards, Ron and Dan _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Tue Jan 20 02:45:45 2009 Return-Path: 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 E64AA3A6BBA; Tue, 20 Jan 2009 02:45:45 -0800 (PST) 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 7D81E3A6BC2; Tue, 20 Jan 2009 02:45:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.472 X-Spam-Level: X-Spam-Status: No, score=-2.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 UVAtpKf8AP20; Tue, 20 Jan 2009 02:45:43 -0800 (PST) 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 034BE3A6B1B; Tue, 20 Jan 2009 02:45:42 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,295,1231131600"; d="scan'208";a="158366779" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 20 Jan 2009 05:45:25 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jan 2009 05:45:24 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 20 Jan 2009 11:45:06 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-melnikov-sieve-imapext-metadata-08.txt to Proposed Standard Thread-Index: Acl6tioPSOCYkxZQQxWoGj6hGnaPswANemog From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-melnikov-sieve-imapext-metadata-08.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-melnikov-sieve-imapext-metadat a-08.txt Technical Summary The SIEVE mail filtering language - extension for accessing mailbox metadata extension provides a way for a SIEVE script to test annotations stored on an IMAP server supporting the METADATA extension. Working Group Summary This document has been discussed and reviewed in the SIEVE Working Group. There is consensus in the Working Group to publish this document as a Proposed Standard. Document Quality A number of implementors have expressed interest in this extension. Personal Document Shepherd: Cyrus Daboo AD: Lisa Dusseault _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Thu Jan 22 10:58:32 2009 Return-Path: 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 B332728C270; Thu, 22 Jan 2009 10:58:32 -0800 (PST) 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 A50B928C26C; Thu, 22 Jan 2009 10:58:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.477 X-Spam-Level: X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122, 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 VNZB5hJDFirZ; Thu, 22 Jan 2009 10:58:30 -0800 (PST) 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 BB64428C262; Thu, 22 Jan 2009 10:58:30 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,307,1231131600"; d="scan'208";a="158713502" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 22 Jan 2009 13:58:10 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Jan 2009 13:58:09 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 22 Jan 2009 19:57:50 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-radext-management-authorization-06.txt to Proposed Standard Thread-Index: Acl8wgzJzLkIB64xTjGY9Zr2f+VQOgAATH8Q From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-radext-management-authorization-06.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-radext-management-authori zation-06.txt Technical Summary This document specifies RADIUS attributes for authorization and service provisioning of Network Access Server (NAS) management. Both local and remote management are supported, with granular access rights and management privileges. Specific provisions are made for remote management via framed management protocols, and for specification of a protected transport protocol. Working Group Summary There have been 2 WGLCs on the document. Much of the discussion on the document has centered around the model for provisioning of protected transports, as well as the different remote administration mechanisms (secure and insecure) to be supported. There has also been discussion of the relationship between Framed Management (introduced in this draft) and the pseudo-TTY management model supported in RFC 2865. Document Quality The document was reviewed by the Juergen Schenwaelder for the ISMS WG and by Vijay Gurbani for Gen-ART. Personnel Bernard Aboba is the PROTO-shepherd, and Dan Romascanu is the responsible AD. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Fri Jan 23 00:13:29 2009 Return-Path: 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 6A96328C167; Fri, 23 Jan 2009 00:13:29 -0800 (PST) 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 BC37F3A69AD; Fri, 23 Jan 2009 00:13:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.481 X-Spam-Level: X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 vLOlXIWN68sS; Fri, 23 Jan 2009 00:13:26 -0800 (PST) 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 737EF3A67FB; Fri, 23 Jan 2009 00:13:26 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,311,1231131600"; d="scan'208";a="158774654" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.avaya.com with ESMTP; 23 Jan 2009 03:13:03 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 23 Jan 2009 03:13:01 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 23 Jan 2009 09:12:38 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for January 29, 2009 Telechat Thread-Index: Acl84wR0qA528lBeQ+Kj8buGm3KIIwATeYrg From: "Romascanu, Dan (Dan)" To: , , "MIB Doctors (E-mail)" , "dns directorate" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for January 29, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 1/29. Please review the relevant documents and WG charters brought up for approval and send me your comments until Wednesday 1/28 COB the latest. The full agenda and links to the documents is available at http://www.ietf.org/IESG/agenda.html. Thanks and Regards, Dan 2.1 WG Submissions 2.1.1 New Item o draft-ietf-mext-nemo-mib-04.txt NEMO Management Information Base (Proposed Standard) - 1 of 10 Token: Jari Arkko o draft-ietf-radext-management-authorization-06.txt Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 10 Token: Dan Romascanu o draft-ietf-pkix-rfc4055-update-01.txt Update for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 10 Token: Pasi Eronen o draft-ietf-softwire-mesh-framework-05.txt Softwire Mesh Framework (Proposed Standard) - 4 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-safi-04.txt BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 5 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-ipsec-01.txt BGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of 10 Token: Mark Townsley o draft-ietf-softwire-bgp-te-attribute-04.txt BGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10 Token: Mark Townsley o draft-ietf-softwire-v4nlri-v6nh-01.txt Advertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 8 of 10 Token: Mark Townsley o draft-ietf-tls-psk-new-mac-aes-gcm-05.txt Pre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of 10 Note: Document Shepherd is jsalowey@cisco.com Token: Pasi Eronen o draft-ietf-idr-flow-spec-03.txt Dissemination of flow specification rules (Proposed Standard) - 10 of 10 Token: David Ward 2.1.2 Returning Item o draft-ietf-mipshop-mstp-solution-11.txt IEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 1 Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item o draft-stjohns-sipso-06.txt Common Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 3 Token: Tim Polk o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 2 of 3 Token: Russ Housley o draft-melnikov-sieve-imapext-metadata-08.txt The Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 3 of 3 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-trill-prob-05.txt Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 1 of 3 Token: Mark Townsley o draft-ietf-pim-rpf-vector-08.txt The RPF Vector TLV (Informational) - 2 of 3 Token: David Ward o draft-ietf-tls-ecdhe-psk-05.txt ECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 3 of 3 Token: Pasi Eronen 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 NONE 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 NONE 3.3.2 Returning Item NONE 3.3.3 For Action o draft-irtf-routing-history-09.txt Analysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2 Token: Russ Housley o draft-irtf-routing-reqs-10.txt A Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2 Token: Russ Housley 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval o Network Configuration (netconf) - 1 of 2 Token: Dan Romascanu o IP Performance Metrics (ippm) - 2 of 2 Token: Lars Eggert _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 24 22:52:53 2009 Return-Path: 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 3C7803A68D8; Sat, 24 Jan 2009 22:52:53 -0800 (PST) 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 E318C3A6452; Sat, 24 Jan 2009 22:52:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.483 X-Spam-Level: X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 WnD4QmHgtZf2; Sat, 24 Jan 2009 22:52:51 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id D4D8D3A6405; Sat, 24 Jan 2009 22:52:50 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="149734726" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jan 2009 01:52:32 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Jan 2009 01:52:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 07:52:10 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-andreasen-sipping-rfc3603bis-07.txt toInformational RFC Thread-Index: Acl+ZmAtqO3OKvajTXu8xiwtXxB6vwAUv/4g From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-andreasen-sipping-rfc3603bis-07.txt toInformational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-andreasen-sipping-rfc3603bis-0 7.txt Technical Summary In order to deploy a residential telephone service at very large scale across different domains, it is necessary for trusted elements owned by different service providers to exchange trusted information that conveys customer-specific information and expectations about the parties involved in the call. This document describes private extensions to the Session Initiation Protocol (SIP) [RFC3261] for supporting the exchange of customer information and billing information between trusted entities in the PacketCable Distributed Call Signaling Architecture. These extensions provide mechanisms for access network coordination to prevent theft of service, customer originated trace of harassing calls, support for operator services and emergency services, and support for various other regulatory issues. The use of the extensions is only applicable within closed administrative domains, or among federations of administrative domains with previously agreed-upon policies where coordination of charging and other functions is required. Working Group Summary None Document Quality This is a minor update to RFC 3603 which is a P-Header. Personnel Proto Document Shepherd is Mary Barnes. Expert Review was done by Miguel A. Garcia. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 24 22:54:29 2009 Return-Path: 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 5D3253A6452; Sat, 24 Jan 2009 22:54:29 -0800 (PST) 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 399323A6452; Sat, 24 Jan 2009 22:54:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.483 X-Spam-Level: X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 xBoN3mGFAjXl; Sat, 24 Jan 2009 22:54:27 -0800 (PST) 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 D8DDA3A6405; Sat, 24 Jan 2009 22:54:26 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="135071981" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jan 2009 01:54:06 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Jan 2009 01:54:06 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 07:53:44 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-avt-post-repair-rtcp-xr-04.txt to Proposed Standard Thread-Index: Acl+ZghZ8zXe0Pw7TjazN4GmqRs9ZwAU3YSw From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-avt-post-repair-rtcp-xr-04.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-avt-post-repair-rtcp-xr-0 4.txt Technical Summary This document defines a new report block type within the framework of RTP Control Protocol (RTCP) Extended Reports (XR). One of the initial XR report block types is the Loss Run Length Encoding (RLE) Report Block. This report conveys the information regarding the individual Real-time Transport Protocol (RTP) packet receipt and loss events experienced during the RTCP interval preceding the transmission of the report. The new report, which is referred to as the Post-repair Loss RLE Report, carries the information regarding the remaining lost packets after all loss-repair methods are applied. By comparing the RTP packet receipts/losses before and after the loss repair is completed, one can determine the effectiveness of the loss-repair methods in an aggregated fashion. This document also defines the signaling of the Post-repair Loss RLE Report in the Session Description Protocol (SDP). Working Group Summary The document has been reviewed by the AVT working group to ensure consistency with RTCP XR. Document Quality There are implementations of RTCP-XR and this draft adds a new report type. The document was reviewed by Alan Clark and Geoff Hunt, both have been involved with the RTCP-XR work. Personnel Roni Even is the document shepherd. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 24 22:55:12 2009 Return-Path: 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 89C153A68D8; Sat, 24 Jan 2009 22:55:12 -0800 (PST) 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 219AD3A6452; Sat, 24 Jan 2009 22:55:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.484 X-Spam-Level: X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, 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 9lyWRxwX6Tx7; Sat, 24 Jan 2009 22:55:11 -0800 (PST) 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 C7DFC3A6405; Sat, 24 Jan 2009 22:55:10 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="135072009" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jan 2009 01:54:52 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Jan 2009 01:54:51 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 07:54:46 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-mmusic-file-transfer-mech-10.txt to Proposed Standard Thread-Index: Acl+ZATSuilJkp6kS+6XjDfnI5x5dAAVa0KA From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-mmusic-file-transfer-mech-10.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mmusic-file-transfer-mech -09.txt Technical summary: The document defines extensions to the SDP offer/answer model to enable file transfer as part of SDP-negotiated multimedia sessions. It also specifies using MSRP for the actual file transmission. Working Group summary: The MMUSIC WG has firm consenses on publishing this document as Proposed Standard. Document quality: The document is considered ready for publication. An early interoperability test of independent implementations from various major vendors on an image sharing specification (which uses the file transfer I-D as a basis) took place already in 2007 under the auspices of the GSM Association. The interop event provided useful input for this and other specifications. Personnel: The document shepherd is Joerg Ott, the responsible AD is Cullen Jennings. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sat Jan 24 22:56:25 2009 Return-Path: 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 B5F063A688A; Sat, 24 Jan 2009 22:56:25 -0800 (PST) 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 4A5483A6452; Sat, 24 Jan 2009 22:56:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.485 X-Spam-Level: X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 zWXtndb07WsT; Sat, 24 Jan 2009 22:56:24 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 3F9703A6405; Sat, 24 Jan 2009 22:56:24 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="149734835" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jan 2009 01:56:00 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2009 01:55:59 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 07:55:37 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-geopriv-pdif-lo-profile-14.txt to Proposed Standard Thread-Index: Acl+Y7LU3Yp6vUFMTZymRU9KmpuC3wAViuXg From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-geopriv-pdif-lo-profile-14.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-geopriv-pdif-lo-profile-1 0.txt Technical Summary The Presence Information Data Format Location Object (PIDF-LO) specification provides a flexible and versatile means to represent location information. There are, however, circumstances that arise when information needs to be constrained in how it is represented. In these circumstances the range of options that need to be implemented are reduced. There is growing interest in being able to use location information contained in a PIDF-LO for routing applications. To allow successful interoperability between applications, location information needs to be normative and more tightly constrained than is currently specified in the RFC 4119 (PIDF-LO). This document makes recommendations on how to constrain, represent and interpret locations in a PIDF-LO. It further recommends a subset of GML that is mandatory to implement by applications involved in location based routing. Working Group Summary This document reflects a strong consensus of the GEOPRIV working group. Document Quality The document was well reviewed within the working group and received comment from SIMPLE participants (specifically about ensuring it took the presence data model into consideration) Personnel Robert Sparks is the Document Shepherd. Cullen Jennings is the responsible AD. The document has no IANA considerations. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 25 05:12:50 2009 Return-Path: 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 32F8328C14C; Sun, 25 Jan 2009 05:12:50 -0800 (PST) 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 0A5693A6A68; Sun, 25 Jan 2009 05:12:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.489 X-Spam-Level: X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110, 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 JKZI+Md4m28g; Sun, 25 Jan 2009 05:12:48 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 14F643A69B1; Sun, 25 Jan 2009 05:12:48 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="149744468" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jan 2009 08:12:30 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Jan 2009 08:12:30 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 14:12:08 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-loreto-simple-im-srv-label-03.txt to Proposed Standard Thread-Index: Acl9JNNoR9JwwKVsTDewL0mbTSdqbwByZ/lQ From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-loreto-simple-im-srv-label-03.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-loreto-simple-im-srv-label-02. txt Technical Summary This document registers with IANA two new DNS SRV Protocol Labels for resolving Instant Messaging and Presence services with SIP. These registrations are necessary because the original definitions of the SRV system for resolving the protocol associated with the "im" and "pres" URI schemes did not register any SIP service. Working Group Summary This document is an individual submission. Document Quality The RAI-ART team reviewed this document (review by Miguel Garcia). Personnel Jon Peterson reviewed this document for the IESG, and is the document shepherd. Gen-ART review was provided by Suresh Krishnan. RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 25 05:32:52 2009 Return-Path: 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 83C7728C170; Sun, 25 Jan 2009 05:32:52 -0800 (PST) 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 C3F863A6A40; Sun, 25 Jan 2009 05:32:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.49 X-Spam-Level: X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 BDas5EGFsVUG; Sun, 25 Jan 2009 05:32:50 -0800 (PST) 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 50FE23A68BA; Sun, 25 Jan 2009 05:32:50 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="135079713" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jan 2009 08:32:31 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2009 08:32:28 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 14:32:06 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-speermint-terminology-17.txt to Informational RFC Thread-Index: Acl9JGe8pDIdUOsYQYi5E4t/Mjl0lgBzN43w From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-speermint-terminology-17.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-speermint-terminology-17. txt Technical Summary This document defines the basic terminology that is to be used in describing Session PEERing for Multimedia INTerconnect (SPEERMINT). Working Group Summary There is consensus in the WG to publish this document. Several Working Group Last Calls have been issued, and we have finally achieved consensus and resolved all concerns. All changes suggested by the WG have been made to this draft. A nits review has also been performed by our secretary, and those changes made as well. Document Quality There are no protocol implementations proposed, only terminology. The new terms and now consistently in use across all SPEERMINT documents. Personnel Document Shepherd: Jason Livingood Responsible AD: Jon Peterson IANA Experts Required: No RFC Editor Note (Insert RFC Editor Note here or remove section) IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 25 05:39:16 2009 Return-Path: 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 ABBF228C172; Sun, 25 Jan 2009 05:39:16 -0800 (PST) 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 AF72828C14C; Sun, 25 Jan 2009 05:39:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.49 X-Spam-Level: X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.109, 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 46HUjJZOUXqQ; Sun, 25 Jan 2009 05:39:15 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id B037628C105; Sun, 25 Jan 2009 05:39:14 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="149745078" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 25 Jan 2009 08:38:56 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 25 Jan 2009 08:38:55 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 14:38:33 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-tls-psk-new-mac-aes-gcm-05.txt to Proposed Standard Thread-Index: Acl8ybwQHMjao8Y1S3iMb+OYL0BHwQCKHJaQ From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-tls-psk-new-mac-aes-gcm-05.txt to Proposed Standard X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tls-psk-new-mac-aes-gcm-0 5.txt Technical Summary RFC 4279 and RFC 4785 describe pre-shared key cipher suites for Transport Layer Security (TLS). However, all those cipher suites use SHA-1 as their MAC algorithm. This document describes a set of pre-shared key cipher suites for TLS which uses stronger digest algorithms (i.e., SHA-256 or SHA-384) and another set which uses the Advanced Encryption Standard (AES) in Galois Counter Mode (GCM). Working Group Summary This document is a product of the Transport Layer Security (TLS) Working Group. The document represents the consensus of the TLS working group. Document Quality There are no existing implementations, but working group members have shown interest in the document. Personnel The document shepherd is Joe Salowey. The responsible area director is Pasi Eronen. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Sun Jan 25 05:39:40 2009 Return-Path: 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 D416028C172; Sun, 25 Jan 2009 05:39:40 -0800 (PST) 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 6156D28C14C; Sun, 25 Jan 2009 05:39:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.491 X-Spam-Level: X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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+CZ2xDaOBkV; Sun, 25 Jan 2009 05:39:38 -0800 (PST) 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 2552728C105; Sun, 25 Jan 2009 05:39:37 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,321,1231131600"; d="scan'208";a="135079878" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 25 Jan 2009 08:39:19 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 25 Jan 2009 08:39:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 25 Jan 2009 14:38:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-tls-ecdhe-psk-05.txt to Informational RFC Thread-Index: Acl8yYXKb8rqm6V4Tz26kXDx1DmBCQCKLT0Q From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-tls-ecdhe-psk-05.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tls-ecdhe-psk-05.txt Technical Summary This document extends RFC 4279, RFC 4492 and RFC 4785, and specifies a set of cipher suites that use a pre-shared key (PSK) to authenticate an Elliptic Curve Diffie-Hellman exchange (ECDH). These cipher suites provide Perfect Forward Secrecy (PFS). Working Group Summary This document is a product of the Transport Layer Security (TLS) Working Group. The document represents the consensus of the TLS working group. Document Quality There are no existing implementations, but working group members have shown interest in the document. Personnel The document shepherd is Joe Salowey. The responsible area director is Pasi Eronen. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Mon Jan 26 02:54:18 2009 Return-Path: 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 E2B093A6AA5; Mon, 26 Jan 2009 02:54:18 -0800 (PST) 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 DFDE53A6A62 for ; Sun, 25 Jan 2009 09:22:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.663 X-Spam-Level: X-Spam-Status: No, score=-1.663 tagged_above=-999 required=5 tests=[AWL=0.936, 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 yHsekx4IOK4j for ; Sun, 25 Jan 2009 09:22:59 -0800 (PST) Received: from liberty.deployingradius.com (liberty.deployingradius.com [88.191.76.128]) by core3.amsl.com (Postfix) with ESMTP id 2F7163A6AA7 for ; Sun, 25 Jan 2009 09:22:59 -0800 (PST) Received: from Thor.local (pas38-1-82-67-71-238.fbx.proxad.net [82.67.71.238]) by liberty.deployingradius.com (Postfix) with ESMTPSA id F31B412342BC; Sun, 25 Jan 2009 18:22:40 +0100 (CET) Message-ID: <497C9FE0.7020403@deployingradius.com> Date: Sun, 25 Jan 2009 18:22:40 +0100 From: Alan DeKok User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: In-Reply-To: X-Enigmail-Version: 0.95.7 X-Mailman-Approved-At: Mon, 26 Jan 2009 02:54:17 -0800 Cc: aaa-doctors@ietf.org, radiusext@ops.ietf.org Subject: Re: [AAA-DOCTORS] AAA / RADIUS content indraft-ietf-softwire-hs-framework-l2tpv2 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Romascanu, Dan (Dan) wrote: > Actually the whole section 8 is about 'Considerations about RADIUS > Integration' so this needs review.. I agree with Bernard here. The document isn't in good shape, and the I-D's it references require drastic changes to the RADIUS protocol. Alan DeKok. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors From aaa-doctors-bounces@ietf.org Wed Jan 28 00:40:10 2009 Return-Path: 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 7885C3A6BEA; Wed, 28 Jan 2009 00:40:10 -0800 (PST) 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 5572A3A6910; Wed, 28 Jan 2009 00:40:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.385 X-Spam-Level: X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227] 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 K0jgKIWsJghY; Wed, 28 Jan 2009 00:40:08 -0800 (PST) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 48AAD3A6BEA; Wed, 28 Jan 2009 00:40:08 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,337,1231131600"; d="scan'208";a="150051532" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 28 Jan 2009 03:39:48 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 28 Jan 2009 03:39:48 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 28 Jan 2009 09:39:35 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Evaluation: draft-ietf-ccamp-pc-and-sc-reqs-06.txt to Informational RFC thread-index: AcmBBZSnxgGnUy0tSlKmQuDN85kB8QAHjm7A From: "Romascanu, Dan (Dan)" To: , Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-ccamp-pc-and-sc-reqs-06.txt to Informational RFC X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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----- A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ccamp-pc-and-sc-reqs-06.t xt Technical Summary From a Carrier perspective, the possibility of turning a Permanent Connection (PC) into a Soft Permanent Connection (SPC) and vice versa, without actually affecting Data Plane traffic being carried over it, is a valuable option. In other terms, such operation can be seen as a way of transferring the ownership and control of an existing and in-use Data Plane connection between the Management Plane and the Control Plane, leaving its Data Plane state untouched. This informational document sets out the requirements for such procedures within a Generalized Multiprotocol Label Switching (GMPLS) network. Working Group Summary There were no problems with consensus for this document. In the early stages there were some very strong opinions about the value of this work. Some vendors and operators did not believe that the function would be useful in the networks they build. However, over time, other vendors and operators strongly supported the function, and since it is described as an optional function in equipment and deployment, the working group did not object to this work proceeding. See proto writeup by Deborah Brungard. Document Quality This is a requirements specification, and cannot be implemented. Note that work is already in progress within the CCAMP working group to develop protocol solutions. Personnel Deborah Brungard is the Document Shepherd for this document. Ross Callon is the Responsible Area Director. There are no IANA actions for this document. RFC Editor Note Please move the "Conventions used in this document" to be at the end of section 1 (introduction), as section 1.1. IRTF Note (Insert IRTF Note here or remove section) IESG Note (Insert IESG Note here or remove section) IANA Note (Insert IANA Note here or remove section) _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors