Re: [radext] New DTLS document

"Joseph Salowey (jsalowey)" <jsalowey@cisco.com> Tue, 07 May 2013 00:46 UTC

Return-Path: <jsalowey@cisco.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207E821F8C35 for <radext@ietfa.amsl.com>; Mon, 6 May 2013 17:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.979
X-Spam-Level:
X-Spam-Status: No, score=-109.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqj9jaszU7Wt for <radext@ietfa.amsl.com>; Mon, 6 May 2013 17:45:55 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 26C0A21F86E4 for <radext@ietf.org>; Mon, 6 May 2013 17:45:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2519; q=dns/txt; s=iport; t=1367887555; x=1369097155; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RReCfrkOVtdDclZIjVjewuGq31UdMPUsAb2/SzfOO2o=; b=GpK9MTwj0CouNZonpS2XBo7JxhYhpEVIa/N5GGTzXnexWPumu5Zw2AiB B1IW8HcEp8SjS+bMi5WGMG8m1ASEUezDfDwOLDajCDe4SjpFKRlCPJm14 6Vv2TuxW85CjhYnoJkYvV/3RmS8zCPoteB0Al9e4F+Oap8q5TmbLHa4nm U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAO1NiFGtJXHB/2dsb2JhbABQgwe/P4EKFnSCHwEBAQMBeQULAgEIGAokIRElAgQOBQgTh18DCQayRYYZDYgSjFuCIwIxB4JyYQOIYIxqjXeFIYMNgic
X-IronPort-AV: E=Sophos;i="4.87,624,1363132800"; d="scan'208";a="207114219"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 07 May 2013 00:45:54 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r470jsF7013395 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 7 May 2013 00:45:54 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.125]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.02.0318.004; Mon, 6 May 2013 19:45:54 -0500
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
Thread-Topic: [radext] New DTLS document
Thread-Index: AQHOPxrSUMYvYTIR/ESEOHVAZTrrOpjtPcYAgAHZJgCAAtwTAIAAf/aAgAAuUICABqzMAA==
Date: Tue, 7 May 2013 00:45:54 +0000
Message-ID: <A95B4818FD85874D8F16607F1AC7C628BC542F@xmb-rcd-x09.cisco.com>
References: <516EA97E.2000005@deployingradius.com> <C47910C2-BCEA-4DC2-A016-C98D67B62DD9@gmail.com> <A95B4818FD85874D8F16607F1AC7C628B4032E@xmb-rcd-x09.cisco.com> <0E1BBA4B-1985-43C3-800A-AF336CABEF30@gmail.com> <517FBD04.1050009@deployingradius.com> <B43B810F-DBF3-4CCD-BFA0-494E10819D2A@gmail.com> <51828E77.9020303@deployingradius.com> <061B9149-3354-4E53-8721-FCD86BF03EF0@gmail.com>
In-Reply-To: <061B9149-3354-4E53-8721-FCD86BF03EF0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.33.248.202]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FA5971BA8DB0D84B9C99F3A8D5FADF07@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<radext@ietf.org>" <radext@ietf.org>, Alan DeKok <aland@deployingradius.com>
Subject: Re: [radext] New DTLS document
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 00:46:08 -0000

On May 2, 2013, at 11:49 AM, Jouni Korhonen <jouni.nospam@gmail.com> wrote:

> Hi,
> 
> On May 2, 2013, at 7:04 PM, Alan DeKok <aland@deployingradius.com> wrote:
> 
>> Jouni Korhonen wrote:
>>> I would be ok to remove Section 5.1.2 entirely.
>> 
>> Which means that the rest of the document needs to be updated, too.
>> It talks about accepting UDP and DTLS on the same port.  Section 5.1.2
>> is only *justification* for why that works.  The other sections say
>> *how* it's supposed to work.
>> 
>> i.e. Deleting 5.1.2 means we'd have to delete more than half of
>> Section 3, too.
> 
> That would be a side effect of this approach. However, most folks
> (including me) seems to be okish keeping the current text as well.
> So it would be Joe's voice that counts here now.
> 
[Joe]   So, I don't see any description as to how the transition mechanism allows transition to the new port.   Without this it seems its not really a transition mechanism but something that is intended to be around for a while.  So I think we either need to define how to actually transition or fix the mechanism.  


> 
>>> However, if WG wants to keep
>>> Section 5.1.2 I would add a note there that it is intended to be a short term 
>>> migration solution and can be turned off at some point of time. Implementations
>>> and deployments are encouraged to switch to the RADIUS-DTLS port as soon as
>>> possible. Would that be OK for the WG?
>> 
>> I already added that in the latest rev.  See Section 3:
>> 
>>  This section describes how clients and servers should transition to
>>  DTLS.  There is a fair amount of discussion around this transition,
>>  as it is critical to get it correct.  We expect that once
>>  implementations have transitioned to RADIUS/DTLS, the text in this
>>  section will no longer be relevant.
>> 
>> If we're just going to turn off UDP, we don't need any transition
>> path.  We just break the network, and let everyone figure out what to do.
>> 
>> The whole point of the text in Section 3 is to document how the
>> transition path is handled.  Including (if so desired) accepting UDP and
>> DTLS on the same port.
>> 
>> I can add duplicate text in Section 5.1.2.  But the idea is for people
>> to read the *entire* document, and act on it as a whole.
> 
> No need to duplicate. A pointer back to Section 3 would definitely 
> suffice.
> 
> - Jouni
> 
> 
>> 
>> Alan DeKok.
>