IETF Logo Mail Archive

Re: [kitten] New URI Discovery Draft

Matt Rogers <mrogers@redhat.com> Mon, 26 September 2016 17:02 UTC

Return-Path: <mrogers@redhat.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B05A612B30C for <kitten@ietfa.amsl.com>; Mon, 26 Sep 2016 10:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.218
X-Spam-Level:
X-Spam-Status: No, score=-9.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-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 H1Psvng7gKxc for <kitten@ietfa.amsl.com>; Mon, 26 Sep 2016 10:02:29 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 573D112B24B for <kitten@ietf.org>; Mon, 26 Sep 2016 10:02:29 -0700 (PDT)
Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 035F3C04B923 for <kitten@ietf.org>; Mon, 26 Sep 2016 17:02:29 +0000 (UTC)
Received: from unused (unused [10.10.52.232] (may be forged)) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u8QH2SSX012594; Mon, 26 Sep 2016 13:02:28 -0400
Message-ID: <1474909347.15526.41.camel@redhat.com>
From: Matt Rogers <mrogers@redhat.com>
To: Petr Spacek <pspacek@redhat.com>, Nathaniel McCallum <npmccallum@redhat.com>, kitten@ietf.org
Date: Mon, 26 Sep 2016 13:02:27 -0400
In-Reply-To: <fc190d9c-2e8f-d727-1a66-c678cd850a32@redhat.com>
References: <1474669521.30344.15.camel@redhat.com> <c2e61e27-8a6c-1d38-140e-0c019b0a13a2@redhat.com> <1474905318.15526.31.camel@redhat.com> <fc190d9c-2e8f-d727-1a66-c678cd850a32@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Mon, 26 Sep 2016 17:02:29 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/seU4-BopC6JkoOktZxVlaNzOxhc>
Cc: Simo Sorce <simo@redhat.com>
Subject: Re: [kitten] New URI Discovery Draft
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2016 17:02:31 -0000

On Mon, 2016-09-26 at 18:01 +0200, Petr Spacek wrote:
> 
> Fine with me. The main point is that if we do not define criticality
> or at
> least reserved character now it will be impossible to enforce it on
> older
> clients. Maybe we can reserve "!" character now and say that
> character
> immediately following "!" must be ignored by clients implementing
> this version
> of the draft?
> 

I'm thinking that the flag should not be ignored, but just that in this
version of the draft '!' is reserved but ignored and no criticality is
assumed on the following flag. In a future version the '!' could
indicate that the following flag is critical.

Regards,
Matt

v2.23.0 | Report a Bug | By Email