From nobody Sat Feb 4 16:32:06 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BECC12943D for ; Sat, 4 Feb 2017 16:32:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_FAIL=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5lD2L0_jI8Gu for ; Sat, 4 Feb 2017 16:32:04 -0800 (PST) Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 614B5127A90 for ; Sat, 4 Feb 2017 16:32:03 -0800 (PST) Received: by power.freeradius.org (Postfix, from userid 1000) id 0BC892241139; Sun, 5 Feb 2017 01:32:02 +0100 (CET) From: aland@freeradius.org To: X-Mailer: mail (GNU Mailutils 2.99.99) Message-Id: <20170205003202.0BC892241139@power.freeradius.org> Date: Sun, 5 Feb 2017 01:32:02 +0100 (CET) Archived-At: Subject: [AAA-DOCTORS] Automatic tech report for Sun Feb 5 01:32:01 CET 2017 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2017 00:32:05 -0000 This is an automatically generated email. It lists the IETF internet-drafts which are WG items and which reference RADIUS. Drafts from the RADEXT and DIME working groups are not included. -- draft-ietf-abfab-aaa-saml-14 In IESG processing - ID Tracker state draft-ietf-abfab-arch-13 In IESG processing - ID Tracker state draft-ietf-dnsop-isp-ip6rdns-01 Active draft-ietf-softwire-map-radius-05 Active From nobody Thu Feb 9 01:52:25 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0616A129636 for ; Thu, 9 Feb 2017 01:52:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.521 X-Spam-Level: X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kefx3ICgYtf6 for ; Thu, 9 Feb 2017 01:52:22 -0800 (PST) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B329512941E for ; Thu, 9 Feb 2017 01:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10330; q=dns/txt; s=iport; t=1486633941; x=1487843541; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=2rMe/H3ncL7zyYXaQrdD7SdFZkihdHSvmIfCk6kIyaI=; b=kmNYel74ZzxSziJuAgpSBV3Ndy9AX7xAHxyLmFIiA9+FgyVtvDtqZx8Y Uu9kvAeP/rxedPkTMUVe8Op+rayLEqfLUcesuI09JB27oTtEesCpLSxRS lewY02RGYVBsXhM0kOSK5Qk3mQZPeBp58JJMoDC/mXSDV0CK+Axf34JN6 A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AoAgAcO5xY/xbLJq1DEQkaAQEBAQIBA?= =?us-ascii?q?QEBCAEBAQGEMgMnX41hcpB4H4I6hVKEc4MLhSyCDCqFeAKDORgBAgEBAQEBAQF?= =?us-ascii?q?iHQuEaQEGJ2IcAwECLyEsAggGDQYCAQGJWAMVDi2xLTorhwkNhAoBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBH4ZMggUIgmKBPIEVRoEEEkeFRQWJDBGHbIovOIZthwwBhBi?= =?us-ascii?q?Be1OERIMthkaKNFqIBR84E2sfEwgVFRiEaA0QgWI/NQETiGoBAQE?= X-IronPort-AV: E=Sophos;i="5.35,349,1484006400"; d="scan'208,217";a="652352517" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2017 09:52:19 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v199qJok006234 for ; Thu, 9 Feb 2017 09:52:19 GMT References: <20170209025634.0538BB80107@rfc-editor.org> To: "aaa-doctors@ietf.org" From: Benoit Claise X-Forwarded-Message-Id: <20170209025634.0538BB80107@rfc-editor.org> Message-ID: <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> Date: Thu, 9 Feb 2017 10:52:20 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170209025634.0538BB80107@rfc-editor.org> Content-Type: multipart/alternative; boundary="------------2B8B4B78FBFF6CD4F3870FB5" Archived-At: Subject: [AAA-DOCTORS] Fwd: [Technical Errata Reported] RFC6733 (4931) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 09:52:24 -0000 This is a multi-part message in MIME format. --------------2B8B4B78FBFF6CD4F3870FB5 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit AAA doctors, What do you think of this errata? Regards, B. -------- Forwarded Message -------- Subject: [Technical Errata Reported] RFC6733 (4931) Date: Wed, 8 Feb 2017 18:56:34 -0800 From: RFC Errata System To: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, charset=UTF-8@rfc-editor.org The following errata report has been submitted for RFC6733, "Diameter Base Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4931 -------------------------------------- Type: Technical Reported by: Luiz Solis Section: 6.1.9 Original Text ------------- Figure 6.1 provides an example of message routing using the procedures listed in these sections. (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) (Origin-Realm=example.net) (Origin-Realm=example.net) (Destination-Realm=example.com) (Destination-Realm=example.com) (Route-Record=nas.example.net) +------+ ------> +------+ ------> +------+ | | (Request) | | (Request) | | | NAS +-------------------+ DRL +-------------------+ HMS | | | | | | | +------+ <------ +------+ <------ +------+ example.net (Answer) example.net (Answer) example.com (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) (Origin-Realm=example.com) (Origin-Realm=example.com) Figure 6: Routing of Diameter messages Corrected Text -------------- Figure 6.1 provides an example of message routing using the procedures listed in these sections. (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) (Origin-Realm=example.net) (Origin-Realm=example.net) (Destination-Realm=example.com) (Destination-Realm=example.com) (Route-Record=nas.example.net)* (Route-Record=nas.example.net) (Route-Record=drl.example.net)* +------+ ------> +------+ ------> +------+ | | (Request) | | (Request) | | | NAS +-------------------+ DRL +-------------------+ HMS | | | | | | | +------+ <------ +------+ <------ +------+ example.net (Answer) example.net (Answer) example.com (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) (Origin-Realm=example.com) (Origin-Realm=example.com) *Optional. Figure 6: Routing of Diameter messages Notes ----- The relay or proxy agent should append their own identity optionally in an additional Route-Record AVP (282). Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6733 (draft-ietf-dime-rfc3588bis-33) -------------------------------------- Title : Diameter Base Protocol Publication Date : October 2012 Author(s) : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed. Category : PROPOSED STANDARD Source : Diameter Maintenance and Extensions Area : Operations and Management Stream : IETF Verifying Party : IESG . --------------2B8B4B78FBFF6CD4F3870FB5 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7bit AAA doctors,

What do you think of this errata?

Regards, B.


-------- Forwarded Message --------
Subject: [Technical Errata Reported] RFC6733 (4931)
Date: Wed, 8 Feb 2017 18:56:34 -0800
From: RFC Errata System <rfc-editor@rfc-editor.org>
To: vf0213@gmail.com, jari.arkko@ericsson.com, john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com
CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, charset=UTF-8@rfc-editor.org 


The following errata report has been submitted for RFC6733,
"Diameter Base Protocol".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4931

--------------------------------------
Type: Technical
Reported by: Luiz Solis <luizsolis@hotmail.com>

Section: 6.1.9

Original Text
-------------
Figure 6.1 provides an example of message routing using the procedures
listed in these sections.

(Origin-Host=nas.example.net)    (Origin-Host=nas.example.net)
(Origin-Realm=example.net)       (Origin-Realm=example.net)
(Destination-Realm=example.com)  (Destination-Realm=example.com)
                                 (Route-Record=nas.example.net)

+------+      ------>      +------+      ------>      +------+
|      |     (Request)     |      |      (Request)    |      |
| NAS  +-------------------+ DRL  +-------------------+ HMS  |
|      |                   |      |                   |      |
+------+     <------       +------+     <------       +------+
example.net    (Answer)   example.net     (Answer)   example.com
(Origin-Host=hms.example.com)   (Origin-Host=hms.example.com)
(Origin-Realm=example.com)      (Origin-Realm=example.com)

       Figure 6: Routing of Diameter messages

Corrected Text
--------------
Figure 6.1 provides an example of message routing using the procedures
listed in these sections.

(Origin-Host=nas.example.net)    (Origin-Host=nas.example.net)
(Origin-Realm=example.net)       (Origin-Realm=example.net)
(Destination-Realm=example.com)  (Destination-Realm=example.com)
(Route-Record=nas.example.net)*  (Route-Record=nas.example.net)
                                 (Route-Record=drl.example.net)*
+------+      ------>      +------+      ------>      +------+
|      |     (Request)     |      |      (Request)    |      |
| NAS  +-------------------+ DRL  +-------------------+ HMS  |
|      |                   |      |                   |      |
+------+     <------       +------+     <------       +------+
example.net    (Answer)   example.net     (Answer)   example.com
(Origin-Host=hms.example.com)   (Origin-Host=hms.example.com)
(Origin-Realm=example.com)      (Origin-Realm=example.com)

*Optional.

                  Figure 6: Routing of Diameter messages

Notes
-----
The relay or proxy agent should append their own identity optionally in an additional Route-Record AVP (282).

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6733 (draft-ietf-dime-rfc3588bis-33)
--------------------------------------
Title               : Diameter Base Protocol
Publication Date    : October 2012
Author(s)           : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed.
Category            : PROPOSED STANDARD
Source              : Diameter Maintenance and Extensions
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG
.
--------------2B8B4B78FBFF6CD4F3870FB5-- From nobody Thu Feb 9 13:31:14 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B545129C8F for ; Thu, 9 Feb 2017 13:31:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wbZ3YWd84FZ for ; Thu, 9 Feb 2017 13:31:08 -0800 (PST) Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8D1412951F for ; Thu, 9 Feb 2017 13:31:02 -0800 (PST) Received: by mail-pg0-x22f.google.com with SMTP id 194so3808678pgd.2 for ; Thu, 09 Feb 2017 13:31:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JvDsb5XyJobM3tkeCnQFkxlGCVLwy/NXBX4Ih6nuU08=; b=jOy4vPm91KDBkn5XI5/Biv4ZxaR9dc0Xz20F+s1dezs4dRAxoNspUGA4HlvCAtaurH 5dGUQXQ2N9QJ+OJPUdbjIHRnW0/LZpC4PiFlDCOUeGKrojZAZ6lC9adIw4fb8NSrFjWu eyQAApT0j1hMReYMUuMKntGViQ/kX4A/9c9oZChUhlNdrxVQfGS0h+B5vHhi/3XkUxIC dSBqnBdps/E9sKbNiIEOXXCkN4QVN87p4yIre4ay39W0iBvRC50nZbju9HUTTgMiwdtW zM26dBTlOoN/BDYYtuYDcd10Z8gMB3eSEX3LIclj15Yc1DLNsRcjVveQtjx6Xbt8IdbC SP9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JvDsb5XyJobM3tkeCnQFkxlGCVLwy/NXBX4Ih6nuU08=; b=rpop1GMp5sugZcHP+KhsLqmWF1UaOF0hXgqnnvU0ua9aAlwlwwh23Gi0uqThOxj56H GxeSvnte61RuAJmy6oK2ql7CFYEUhrQX72elL1KOb0Nn6kIgtPYBtik17MuDnrQKfOc3 6eBcBvCLtW98Ff87X8SDlzUlpvlqMzpmCsJtLnFaXogRCAntT5mMcYFAYSbt4QnzkHlF 1IqtCz9sdDpU5Atx3o8cn5Lajpr8jUdrv5MjOBp5lotWhIBwVNCuvegDlsDFdpsEsb1j GZLxDdBJEuLIksRKhexfwJbQHFdQWa0Pl8eAEF5L08ZXHc00D/nVXOL4FnpW06rp8XdG e90Q== X-Gm-Message-State: AMke39nJ9nu3674kGFAST+FT3f32r4kNxvufyEOtoipUyEeZyVinb7geaizJIvOsy2cXWw== X-Received: by 10.98.218.9 with SMTP id c9mr5953524pfh.99.1486675862264; Thu, 09 Feb 2017 13:31:02 -0800 (PST) Received: from [10.0.0.5] (c-24-5-144-221.hsd1.ca.comcast.net. [24.5.144.221]) by smtp.gmail.com with ESMTPSA id e13sm17084109pgn.38.2017.02.09.13.31.00 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 09 Feb 2017 13:31:00 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Jouni In-Reply-To: <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> Date: Thu, 9 Feb 2017 13:30:56 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <2D7E6B41-F065-478C-8C26-6A0DE98B0A62@gmail.com> References: <20170209025634.0538BB80107@rfc-editor.org> <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> To: Benoit Claise X-Mailer: Apple Mail (2.2104) Archived-At: Cc: "aaa-doctors@ietf.org" Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 21:31:12 -0000 RFC6733 Sections 2.9 and 6.1.9 are rather clear that a relay and a proxy = MUST append a Route-Record to all requests forwarded with the identity = of the peer from which the request was received. There is no text that a = relay or a proxy should add its own identity. If the agent were to add = its own identity it would result duplicate entries of Route-Records if = there are more than one agent on the path. Additionally an agent adding = its own identity to a Route-Record seems to go against a MUST Section = 6.7.1. This errata should be rejected. - Jouni > On 09 Feb 2017, at 01:52, Benoit Claise wrote: >=20 > AAA doctors, >=20 > What do you think of this errata? >=20 > Regards, B. >=20 >=20 > -------- Forwarded Message -------- > Subject: [Technical Errata Reported] RFC6733 (4931) > Date: Wed, 8 Feb 2017 18:56:34 -0800 > From: RFC Errata System > To: vf0213@gmail.com, jari.arkko@ericsson.com, = john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, = joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com > CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, = charset=3DUTF-8@rfc-editor.org >=20 > The following errata report has been submitted for RFC6733, > "Diameter Base Protocol". >=20 > -------------------------------------- > You may review the report below and at: >=20 > http://www.rfc-editor.org/errata_search.php?rfc=3D6733&eid=3D4931 >=20 >=20 > -------------------------------------- > Type: Technical > Reported by: Luiz Solis=20 > >=20 >=20 > Section: 6.1.9 >=20 > Original Text > ------------- > Figure 6.1 provides an example of message routing using the procedures > listed in these sections. >=20 > (Origin-Host=3Dnas.example.net) (Origin-Host=3Dnas.example.net) > (Origin-Realm=3Dexample.net) (Origin-Realm=3Dexample.net) > (Destination-Realm=3Dexample.com) (Destination-Realm=3Dexample.com) > (Route-Record=3Dnas.example.net) >=20 > +------+ ------> +------+ ------> +------+ > | | (Request) | | (Request) | | > | NAS +-------------------+ DRL +-------------------+ HMS | > | | | | | | > +------+ <------ +------+ <------ +------+ > example.net (Answer) example.net (Answer) example.com > (Origin-Host=3Dhms.example.com) (Origin-Host=3Dhms.example.com) > (Origin-Realm=3Dexample.com) (Origin-Realm=3Dexample.com) >=20 > Figure 6: Routing of Diameter messages >=20 > Corrected Text > -------------- > Figure 6.1 provides an example of message routing using the procedures > listed in these sections. >=20 > (Origin-Host=3Dnas.example.net) (Origin-Host=3Dnas.example.net) > (Origin-Realm=3Dexample.net) (Origin-Realm=3Dexample.net) > (Destination-Realm=3Dexample.com) (Destination-Realm=3Dexample.com) > (Route-Record=3Dnas.example.net)* (Route-Record=3Dnas.example.net) > (Route-Record=3Ddrl.example.net)* > +------+ ------> +------+ ------> +------+ > | | (Request) | | (Request) | | > | NAS +-------------------+ DRL +-------------------+ HMS | > | | | | | | > +------+ <------ +------+ <------ +------+ > example.net (Answer) example.net (Answer) example.com > (Origin-Host=3Dhms.example.com) (Origin-Host=3Dhms.example.com) > (Origin-Realm=3Dexample.com) (Origin-Realm=3Dexample.com) >=20 > *Optional. >=20 > Figure 6: Routing of Diameter messages >=20 > Notes > ----- > The relay or proxy agent should append their own identity optionally = in an additional Route-Record AVP (282). >=20 > Instructions: > ------------- > This erratum is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party =20 > can log in to change the status and edit the report, if necessary.=20 >=20 > -------------------------------------- > RFC6733 (draft-ietf-dime-rfc3588bis-33) > -------------------------------------- > Title : Diameter Base Protocol > Publication Date : October 2012 > Author(s) : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, = Ed. > Category : PROPOSED STANDARD > Source : Diameter Maintenance and Extensions > Area : Operations and Management > Stream : IETF > Verifying Party : IESG > . >=20 >=20 > _______________________________________________ > AAA-DOCTORS mailing list > AAA-DOCTORS@ietf.org > https://www.ietf.org/mailman/listinfo/aaa-doctors From nobody Thu Feb 9 16:33:08 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 142771294DB for ; Thu, 9 Feb 2017 16:33:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEzs3Lf8e6sM for ; Thu, 9 Feb 2017 16:33:05 -0800 (PST) Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12A6E1295E4 for ; Thu, 9 Feb 2017 16:33:05 -0800 (PST) Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id BF3B01C0A21; Fri, 10 Feb 2017 01:33:03 +0100 (CET) Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.69]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 9983F6006B; Fri, 10 Feb 2017 01:33:03 +0100 (CET) Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILMA2.corporate.adroot.infra.ftgroup ([fe80::bc1c:ad2f:eda3:8c3d%18]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 01:33:03 +0100 From: To: Jouni , Benoit Claise Thread-Topic: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) Thread-Index: AQHSgxvZU7X7cKR5ZEStlfM1ZB5ejqFhWu7w Date: Fri, 10 Feb 2017 00:33:02 +0000 Message-ID: <23724_1486686783_589D0A3F_23724_194_1_6B7134B31289DC4FAF731D844122B36E0C038C63@OPEXCLILM43.corporate.adroot.infra.ftgroup> References: <20170209025634.0538BB80107@rfc-editor.org> <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> <2D7E6B41-F065-478C-8C26-6A0DE98B0A62@gmail.com> In-Reply-To: <2D7E6B41-F065-478C-8C26-6A0DE98B0A62@gmail.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.168.234.1] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "aaa-doctors@ietf.org" Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 00:33:07 -0000 The Route-Record is primarily used to detect loops: 6.1.3. Receiving Requests A relay or proxy agent MUST check for forwarding loops when receiving requests. A loop is detected if the server finds its own identity in a Route-Record AVP. When such an event occurs, the agent MUST answer with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. How to populate the Route-Record is described twice: Section 2.9: As noted in Section 6.1.9, a relay or proxy agent MUST append a Route-Record AVP to all requests forwarded. The AVP contains the identity of the peer from which the request was received. 6.7.1. Route-Record AVP The Route-Record AVP (AVP Code 282) is of type DiameterIdentity. The identity added in this AVP MUST be the same as the one received in the Origin-Host of the Capabilities Exchange message. Therefore the "rather clear" used by Jouni is almost an euphemism :) I think that Luis was maybe misled by the following text: 6.1.3. Receiving Requests A relay or proxy agent MUST check for forwarding loops when receiving requests. A loop is detected if the server finds its own identity in a Route-Record AVP. When such an event occurs, the agent MUST answer with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. in which "find its own identity" might have been confusing out of context. = But sections 2.9 and 6.7.1 should have clarified this misunderstanding.=20 Whatever the reason for the proposed errata, it can be safely rejected. Regards, Lionel > -----Message d'origine----- > De=A0: AAA-DOCTORS [mailto:aaa-doctors-bounces@ietf.org] De la part de Jo= uni > Envoy=E9=A0: jeudi 9 f=E9vrier 2017 22:31 > =C0=A0: Benoit Claise > Cc=A0: aaa-doctors@ietf.org > Objet=A0: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) >=20 > RFC6733 Sections 2.9 and 6.1.9 are rather clear that a relay and a proxy = MUST > append a Route-Record to all requests forwarded with the identity of the = peer > from which the request was received. There is no text that a relay or a p= roxy > should add its own identity. If the agent were to add its own identity it= would > result duplicate entries of Route-Records if there are more than one agen= t on > the path. Additionally an agent adding its own identity to a Route-Record= seems > to go against a MUST Section 6.7.1. >=20 > This errata should be rejected. >=20 > - Jouni >=20 > > On 09 Feb 2017, at 01:52, Benoit Claise wrote: > > > > AAA doctors, > > > > What do you think of this errata? > > > > Regards, B. > > > > > > -------- Forwarded Message -------- > > Subject: [Technical Errata Reported] RFC6733 (4931) > > Date: Wed, 8 Feb 2017 18:56:34 -0800 > > From: RFC Errata System > > To: vf0213@gmail.com, jari.arkko@ericsson.com, > john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, > joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com > > CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, > charset=3DUTF-8@rfc-editor.org > > > > The following errata report has been submitted for RFC6733, "Diameter > > Base Protocol". > > > > -------------------------------------- > > You may review the report below and at: > > > > http://www.rfc-editor.org/errata_search.php?rfc=3D6733&eid=3D4931 > > > > > > -------------------------------------- > > Type: Technical > > Reported by: Luiz Solis > > > > > > > > Section: 6.1.9 > > > > Original Text > > ------------- > > Figure 6.1 provides an example of message routing using the procedures > > listed in these sections. > > > > (Origin-Host=3Dnas.example.net) (Origin-Host=3Dnas.example.net) > > (Origin-Realm=3Dexample.net) (Origin-Realm=3Dexample.net) > > (Destination-Realm=3Dexample.com) (Destination-Realm=3Dexample.com) > > (Route-Record=3Dnas.example.net) > > > > +------+ ------> +------+ ------> +------+ > > | | (Request) | | (Request) | | > > | NAS +-------------------+ DRL +-------------------+ HMS | > > | | | | | | > > +------+ <------ +------+ <------ +------+ > > example.net (Answer) example.net (Answer) example.com > > (Origin-Host=3Dhms.example.com) (Origin-Host=3Dhms.example.com) > > (Origin-Realm=3Dexample.com) (Origin-Realm=3Dexample.com) > > > > Figure 6: Routing of Diameter messages > > > > Corrected Text > > -------------- > > Figure 6.1 provides an example of message routing using the procedures > > listed in these sections. > > > > (Origin-Host=3Dnas.example.net) (Origin-Host=3Dnas.example.net) > > (Origin-Realm=3Dexample.net) (Origin-Realm=3Dexample.net) > > (Destination-Realm=3Dexample.com) (Destination-Realm=3Dexample.com) > > (Route-Record=3Dnas.example.net)* (Route-Record=3Dnas.example.net) > > (Route-Record=3Ddrl.example.net)* > > +------+ ------> +------+ ------> +------+ > > | | (Request) | | (Request) | | > > | NAS +-------------------+ DRL +-------------------+ HMS | > > | | | | | | > > +------+ <------ +------+ <------ +------+ > > example.net (Answer) example.net (Answer) example.com > > (Origin-Host=3Dhms.example.com) (Origin-Host=3Dhms.example.com) > > (Origin-Realm=3Dexample.com) (Origin-Realm=3Dexample.com) > > > > *Optional. > > > > Figure 6: Routing of Diameter messages > > > > Notes > > ----- > > The relay or proxy agent should append their own identity optionally in= an > additional Route-Record AVP (282). > > > > Instructions: > > ------------- > > This erratum is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or rejected. > > When a decision is reached, the verifying party can log in to change > > the status and edit the report, if necessary. > > > > -------------------------------------- > > RFC6733 (draft-ietf-dime-rfc3588bis-33) > > -------------------------------------- > > Title : Diameter Base Protocol > > Publication Date : October 2012 > > Author(s) : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, = Ed. > > Category : PROPOSED STANDARD > > Source : Diameter Maintenance and Extensions > > Area : Operations and Management > > Stream : IETF > > Verifying Party : IESG > > . > > > > > > _______________________________________________ > > AAA-DOCTORS mailing list > > AAA-DOCTORS@ietf.org > > https://www.ietf.org/mailman/listinfo/aaa-doctors >=20 > _______________________________________________ > AAA-DOCTORS mailing list > AAA-DOCTORS@ietf.org > https://www.ietf.org/mailman/listinfo/aaa-doctors ___________________________________________________________________________= ______________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confiden= tielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu= ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el= ectroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou = falsifie. Merci. This message and its attachments may contain confidential or privileged inf= ormation that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and dele= te this message and its attachments. As emails may be altered, Orange is not liable for messages that have been = modified, changed or falsified. Thank you. From nobody Thu Feb 9 23:52:37 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 563F612A04B for ; Thu, 9 Feb 2017 23:52:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.523 X-Spam-Level: X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8Du5G2PF4YM for ; Thu, 9 Feb 2017 23:52:34 -0800 (PST) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79B0412A047 for ; Thu, 9 Feb 2017 23:52:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8193; q=dns/txt; s=iport; t=1486713153; x=1487922753; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=GLYjkvaI4G9Ch8/xt0KR/NGTfohEcca1gLTe80tb6VU=; b=JZa72c595bK5beSMN2DUueGFcc6GJtEW6pG5rJU7CJ+uAyYRfo/aqE6c 78Y+ncSfuADuiT4Nobz03dwkFwWKp0ZPUuIZFyfknXE2fzyUGzqYbkAu1 RK6f5COdegAwdXjzchY5TI795yrHMsP7IrotxDZAaug0ID4POTpyGqlP1 s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A3AgBEcJ1Y/xbLJq1DEQkZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGEMwMnX41hcpB7H4I6hVKEc4g3gg0fC4V4AoMvGAECAQEBAQE?= =?us-ascii?q?BAWIohGkBAQEEAQElCwEFNgsQCxEDAQIBJwchBh8JCAYBDAYCAQGJXAMVDi2xD?= =?us-ascii?q?zqHPA2EDgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTIIFCIJigTyBFUaBBAsHCgE?= =?us-ascii?q?GQoUaHwEEiQwRh2yES4VkOoZvhwwBhBiBe1OERIMthkaKNVuIBR84E2MIHxMIF?= =?us-ascii?q?RUYJIREDRCBYj81AROHOoItAQEB?= X-IronPort-AV: E=Sophos;i="5.35,140,1484006400"; d="scan'208";a="652376989" Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Feb 2017 07:52:31 +0000 Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1A7qUnp031130; Fri, 10 Feb 2017 07:52:30 GMT To: lionel.morand@orange.com, Jouni References: <20170209025634.0538BB80107@rfc-editor.org> <2b129b48-9d8a-333c-1595-3671d43e45f1@cisco.com> <2D7E6B41-F065-478C-8C26-6A0DE98B0A62@gmail.com> <23724_1486686783_589D0A3F_23724_194_1_6B7134B31289DC4FAF731D844122B36E0C038C63@OPEXCLILM43.corporate.adroot.infra.ftgroup> From: Benoit Claise Message-ID: <88456c05-28d2-9062-e612-543b9c2bbbb3@cisco.com> Date: Fri, 10 Feb 2017 08:52:26 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <23724_1486686783_589D0A3F_23724_194_1_6B7134B31289DC4FAF731D844122B36E0C038C63@OPEXCLILM43.corporate.adroot.infra.ftgroup> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Cc: "aaa-doctors@ietf.org" Subject: Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 07:52:36 -0000 Thank you Lionel and Jouni. Regards, B. > The Route-Record is primarily used to detect loops: > > 6.1.3. Receiving Requests > > A relay or proxy agent MUST check for forwarding loops when receiving > requests. A loop is detected if the server finds its own identity in > a Route-Record AVP. When such an event occurs, the agent MUST answer > with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. > > How to populate the Route-Record is described twice: > > Section 2.9: > > As noted in Section 6.1.9, a relay or proxy agent MUST append a > Route-Record AVP to all requests forwarded. The AVP contains the > identity of the peer from which the request was received. > > 6.7.1. Route-Record AVP > > The Route-Record AVP (AVP Code 282) is of type DiameterIdentity. The > identity added in this AVP MUST be the same as the one received in > the Origin-Host of the Capabilities Exchange message. > > Therefore the "rather clear" used by Jouni is almost an euphemism :) > > I think that Luis was maybe misled by the following text: > > 6.1.3. Receiving Requests > > A relay or proxy agent MUST check for forwarding loops when receiving > requests. A loop is detected if the server finds its own identity in > a Route-Record AVP. When such an event occurs, the agent MUST answer > with the Result-Code AVP set to DIAMETER_LOOP_DETECTED. > > in which "find its own identity" might have been confusing out of context. But sections 2.9 and 6.7.1 should have clarified this misunderstanding. > > Whatever the reason for the proposed errata, it can be safely rejected. > > Regards, > > Lionel > > >> -----Message d'origine----- >> De : AAA-DOCTORS [mailto:aaa-doctors-bounces@ietf.org] De la part de Jouni >> Envoyé : jeudi 9 février 2017 22:31 >> À : Benoit Claise >> Cc : aaa-doctors@ietf.org >> Objet : Re: [AAA-DOCTORS] [Technical Errata Reported] RFC6733 (4931) >> >> RFC6733 Sections 2.9 and 6.1.9 are rather clear that a relay and a proxy MUST >> append a Route-Record to all requests forwarded with the identity of the peer >> from which the request was received. There is no text that a relay or a proxy >> should add its own identity. If the agent were to add its own identity it would >> result duplicate entries of Route-Records if there are more than one agent on >> the path. Additionally an agent adding its own identity to a Route-Record seems >> to go against a MUST Section 6.7.1. >> >> This errata should be rejected. >> >> - Jouni >> >>> On 09 Feb 2017, at 01:52, Benoit Claise wrote: >>> >>> AAA doctors, >>> >>> What do you think of this errata? >>> >>> Regards, B. >>> >>> >>> -------- Forwarded Message -------- >>> Subject: [Technical Errata Reported] RFC6733 (4931) >>> Date: Wed, 8 Feb 2017 18:56:34 -0800 >>> From: RFC Errata System >>> To: vf0213@gmail.com, jari.arkko@ericsson.com, >> john.loughney@nokia.com, glenzorn@gmail.com, bclaise@cisco.com, >> joelja@bogus.com, jouni.nospam@gmail.com, lionel.morand@orange.com >>> CC: luizsolis@hotmail.com, dime@ietf.org, text/plain@rfc-editor.org, >> charset=UTF-8@rfc-editor.org >>> The following errata report has been submitted for RFC6733, "Diameter >>> Base Protocol". >>> >>> -------------------------------------- >>> You may review the report below and at: >>> >>> http://www.rfc-editor.org/errata_search.php?rfc=6733&eid=4931 >>> >>> >>> -------------------------------------- >>> Type: Technical >>> Reported by: Luiz Solis >>> >>> >>> >>> Section: 6.1.9 >>> >>> Original Text >>> ------------- >>> Figure 6.1 provides an example of message routing using the procedures >>> listed in these sections. >>> >>> (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) >>> (Origin-Realm=example.net) (Origin-Realm=example.net) >>> (Destination-Realm=example.com) (Destination-Realm=example.com) >>> (Route-Record=nas.example.net) >>> >>> +------+ ------> +------+ ------> +------+ >>> | | (Request) | | (Request) | | >>> | NAS +-------------------+ DRL +-------------------+ HMS | >>> | | | | | | >>> +------+ <------ +------+ <------ +------+ >>> example.net (Answer) example.net (Answer) example.com >>> (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) >>> (Origin-Realm=example.com) (Origin-Realm=example.com) >>> >>> Figure 6: Routing of Diameter messages >>> >>> Corrected Text >>> -------------- >>> Figure 6.1 provides an example of message routing using the procedures >>> listed in these sections. >>> >>> (Origin-Host=nas.example.net) (Origin-Host=nas.example.net) >>> (Origin-Realm=example.net) (Origin-Realm=example.net) >>> (Destination-Realm=example.com) (Destination-Realm=example.com) >>> (Route-Record=nas.example.net)* (Route-Record=nas.example.net) >>> (Route-Record=drl.example.net)* >>> +------+ ------> +------+ ------> +------+ >>> | | (Request) | | (Request) | | >>> | NAS +-------------------+ DRL +-------------------+ HMS | >>> | | | | | | >>> +------+ <------ +------+ <------ +------+ >>> example.net (Answer) example.net (Answer) example.com >>> (Origin-Host=hms.example.com) (Origin-Host=hms.example.com) >>> (Origin-Realm=example.com) (Origin-Realm=example.com) >>> >>> *Optional. >>> >>> Figure 6: Routing of Diameter messages >>> >>> Notes >>> ----- >>> The relay or proxy agent should append their own identity optionally in an >> additional Route-Record AVP (282). >>> Instructions: >>> ------------- >>> This erratum is currently posted as "Reported". If necessary, please >>> use "Reply All" to discuss whether it should be verified or rejected. >>> When a decision is reached, the verifying party can log in to change >>> the status and edit the report, if necessary. >>> >>> -------------------------------------- >>> RFC6733 (draft-ietf-dime-rfc3588bis-33) >>> -------------------------------------- >>> Title : Diameter Base Protocol >>> Publication Date : October 2012 >>> Author(s) : V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed. >>> Category : PROPOSED STANDARD >>> Source : Diameter Maintenance and Extensions >>> Area : Operations and Management >>> Stream : IETF >>> Verifying Party : IESG >>> . >>> >>> >>> _______________________________________________ >>> AAA-DOCTORS mailing list >>> AAA-DOCTORS@ietf.org >>> https://www.ietf.org/mailman/listinfo/aaa-doctors >> _______________________________________________ >> AAA-DOCTORS mailing list >> AAA-DOCTORS@ietf.org >> https://www.ietf.org/mailman/listinfo/aaa-doctors > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > . > From nobody Sat Feb 11 16:32:36 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F41129498 for ; Sat, 11 Feb 2017 16:32:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_FAIL=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ngNmYVBr3G7 for ; Sat, 11 Feb 2017 16:32:33 -0800 (PST) Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id AE4AA1293FB for ; Sat, 11 Feb 2017 16:32:33 -0800 (PST) Received: by power.freeradius.org (Postfix, from userid 1000) id 3732F22417B7; Sun, 12 Feb 2017 01:32:02 +0100 (CET) From: aland@freeradius.org To: X-Mailer: mail (GNU Mailutils 2.99.99) Message-Id: <20170212003202.3732F22417B7@power.freeradius.org> Date: Sun, 12 Feb 2017 01:32:02 +0100 (CET) Archived-At: Subject: [AAA-DOCTORS] Automatic tech report for Sun Feb 12 01:32:02 CET 2017 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Feb 2017 00:32:35 -0000 This is an automatically generated email. It lists the IETF internet-drafts which are WG items and which reference RADIUS. Drafts from the RADEXT and DIME working groups are not included. -- draft-ietf-abfab-aaa-saml-14 In IESG processing - ID Tracker state draft-ietf-abfab-arch-13 In IESG processing - ID Tracker state draft-ietf-dnsop-isp-ip6rdns-01 Active draft-ietf-softwire-map-radius-05 Active From nobody Sat Feb 18 16:32:36 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE6C1296B6 for ; Sat, 18 Feb 2017 16:32:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_FAIL=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNi7rD1_cYke for ; Sat, 18 Feb 2017 16:32:33 -0800 (PST) Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC5F1296B3 for ; Sat, 18 Feb 2017 16:32:33 -0800 (PST) Received: by power.freeradius.org (Postfix, from userid 1000) id C45D52240CE4; Sun, 19 Feb 2017 01:32:01 +0100 (CET) From: aland@freeradius.org To: X-Mailer: mail (GNU Mailutils 2.99.99) Message-Id: <20170219003201.C45D52240CE4@power.freeradius.org> Date: Sun, 19 Feb 2017 01:32:01 +0100 (CET) Archived-At: Subject: [AAA-DOCTORS] Automatic tech report for Sun Feb 19 01:32:01 CET 2017 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 00:32:35 -0000 This is an automatically generated email. It lists the IETF internet-drafts which are WG items and which reference RADIUS. Drafts from the RADEXT and DIME working groups are not included. -- draft-ietf-abfab-aaa-saml-14 In IESG processing - ID Tracker state draft-ietf-abfab-arch-13 In IESG processing - ID Tracker state draft-ietf-dnsop-isp-ip6rdns-01 Active draft-ietf-softwire-map-radius-05 Active From nobody Sat Feb 25 16:32:06 2017 Return-Path: X-Original-To: aaa-doctors@ietfa.amsl.com Delivered-To: aaa-doctors@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D6912955D for ; Sat, 25 Feb 2017 16:32:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_FAIL=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Lf8jM04yu6F for ; Sat, 25 Feb 2017 16:32:03 -0800 (PST) Received: from power.freeradius.org (power.freeradius.org [195.154.231.44]) by ietfa.amsl.com (Postfix) with ESMTP id 97BF6129551 for ; Sat, 25 Feb 2017 16:32:03 -0800 (PST) Received: by power.freeradius.org (Postfix, from userid 1000) id 645352240E7F; Sun, 26 Feb 2017 01:32:02 +0100 (CET) From: aland@freeradius.org To: X-Mailer: mail (GNU Mailutils 2.99.99) Message-Id: <20170226003202.645352240E7F@power.freeradius.org> Date: Sun, 26 Feb 2017 01:32:02 +0100 (CET) Archived-At: Subject: [AAA-DOCTORS] Automatic tech report for Sun Feb 26 01:32:02 CET 2017 X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 00:32:05 -0000 This is an automatically generated email. It lists the IETF internet-drafts which are WG items and which reference RADIUS. Drafts from the RADEXT and DIME working groups are not included. -- draft-ietf-abfab-aaa-saml-14 In IESG processing - ID Tracker state draft-ietf-abfab-arch-13 In IESG processing - ID Tracker state draft-ietf-dnsop-isp-ip6rdns-01 Active draft-ietf-softwire-map-radius-05 Active