IETF Logo Mail Archive

Re: [Dime] Strange paragraph in http://tools.ietf.org/html/draft-ietf-dime-rfc3588bis-21

Matt Holdrege <holdrege@gmail.com> Sat, 19 July 2014 08:49 UTC

Return-Path: <holdrege@gmail.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8C51A0167 for <dime@ietfa.amsl.com>; Sat, 19 Jul 2014 01:49:05 -0700 (PDT)
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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 nDUhIYADsXtg for <dime@ietfa.amsl.com>; Sat, 19 Jul 2014 01:49:03 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96C451A00D2 for <dime@ietf.org>; Sat, 19 Jul 2014 01:49:03 -0700 (PDT)
Received: by mail-oi0-f41.google.com with SMTP id a141so2324561oig.28 for <dime@ietf.org>; Sat, 19 Jul 2014 01:49:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FyRofPSZdn/4pxJwLPxLyk1fOhu6/mGNk1YyGBn1NHQ=; b=WzoRiqh9GXUU7f4on3bXnPDio96Uq6si2nFVzlU7w2pCSxwAFhj4O65zN/dTIoAAKx E7yV9VSMmgRV4AU3530htVi8ZPe9bcKSM9jgyzyQwMlDrjKH/agiMWJrWxKtzMpU16gk PpcFfCYoEQwEmzRdVv+UrCIsL0tORTWso3ywp3Vh3W77bNtlKGHDg497ONkpVgt/Ftzz jWhCvdHPpULtKAnqdCtbkEreFvzK67WyBcEBMsjFhzF6cgoYAgBiPATvfRuFVN4yg5E6 z94URb+qGF6PRCwqSLnDG5elw9GolGJdy9kfvkySmJmw4cZ7m16GJRKaPTptuUkH7cld ePuA==
MIME-Version: 1.0
X-Received: by 10.60.174.3 with SMTP id bo3mr14459734oec.31.1405759743050; Sat, 19 Jul 2014 01:49:03 -0700 (PDT)
Received: by 10.202.181.70 with HTTP; Sat, 19 Jul 2014 01:49:03 -0700 (PDT)
In-Reply-To: <53C9985F.4080908@gmail.com>
References: <CAFtys5=Lqf1R385YmPxRWMwS78dbD96x9CwZ3w0G9rn1xf7tTg@mail.gmail.com> <53C9985F.4080908@gmail.com>
Date: Sat, 19 Jul 2014 10:49:03 +0200
Message-ID: <CAFtys5mmG5uyEgfzoCNyJRrvUz0ceXG15F3+SO4E48e0+rLsLQ@mail.gmail.com>
From: Matt Holdrege <holdrege@gmail.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
Content-Type: multipart/alternative; boundary="089e011844ce1fcefe04fe87f295"
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/CzIMS4bA1PkDJEa45GujYDffO5I
Cc: dime@ietf.org
Subject: Re: [Dime] Strange paragraph in http://tools.ietf.org/html/draft-ietf-dime-rfc3588bis-21
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jul 2014 08:49:05 -0000

Ouch! Sorry. I guess I wasn't looking in the right place. I see that the
paragraph was fixed anyways.

Thanks,
-Matt


On Fri, Jul 18, 2014 at 11:57 PM, Jouni Korhonen <jouni.nospam@gmail.com>
wrote:

> Matt,
>
> RFC3588 has been obsoleted by RFC6733 (i.e. no use to look into 3588bis
> versions).
>
> - Jouni
>
> 7/18/2014 10:25 PM, Matt Holdrege kirjoitti:
>
>> Hi,
>>
>> Sorry to butt in with a minor nit, but I noticed that section 2.2
>> appears to have mutually exclusive statements.
>>
>> 1. Connections between Diameter peers SHOULD be protected by TLS.
>> 2. The Diameter protocol MUST NOT be used without any security mechanism.
>>
>> I thought the text in RFC 3588 was ok, minus all the NAS bits? Or maybe
>> say that the "Diameter protocol must not be used without inclusive or
>> external transport layer security". Or some such text?
>>
>> -Matt
>>
>>
>>
>> _______________________________________________
>> DiME mailing list
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>>
>>

v2.23.0 | Report a Bug | By Email