Re: [kitten] [Technical Errata Reported] RFC6680 (4337)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Sat, 18 April 2015 22:49 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B46521A88E4 for <kitten@ietfa.amsl.com>; Sat, 18 Apr 2015 15:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 GLvhqCuiYYb6 for <kitten@ietfa.amsl.com>; Sat, 18 Apr 2015 15:49:37 -0700 (PDT)
Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (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 DE4731A88D5 for <kitten@ietf.org>; Sat, 18 Apr 2015 15:49:36 -0700 (PDT)
Received: by qcyk17 with SMTP id k17so41565699qcy.1 for <kitten@ietf.org>; Sat, 18 Apr 2015 15:49:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YORV/2o0ntKbsNxEC0QPxzyb46sx7pdzM9UmaeZHfMA=; b=FZfm255lm0SZEM5viOPTUcz2NkP9cnKUhtcUEI1CP3w23PolKw0ZzoNmUNHfMzdLxb smaIxrntqLpX5bPWG5gv5uwZ3fdJL79VRWUIbklFzGFsD08dkHieT6lQznpUE7QO+Fi3 +S2RJDsEgRrFdFb+it3M1Q7EyiEh1P1QOmY+PRAZv3A7/fZBFl5ELdB7pOmMwAiaDSMV eQlSNxaBBSBT7x9JTMXIqMdOIpoO2WHdbmlQ51MwY4EvLuxjhtCg9XVeEWqPSzxN3HLe fmU1uXHToNMqoSKqW2Tw+F49qkT5G5cwnto8IHeXJaZ3/5qodVmDPBIW1D2Hj7maLNzc lkzA==
X-Received: by 10.55.20.159 with SMTP id 31mr17617304qku.64.1429397376212; Sat, 18 Apr 2015 15:49:36 -0700 (PDT)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by mx.google.com with ESMTPSA id z93sm11166227qgd.45.2015.04.18.15.49.34 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Apr 2015 15:49:34 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <20150418215222.7ABFD180206@rfc-editor.org>
Date: Sat, 18 Apr 2015 18:49:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4268E41F-712E-425D-B514-C0023D311462@gmail.com>
References: <20150418215222.7ABFD180206@rfc-editor.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/66VqwDNIWKjqDNPiG81260oN2nM>
X-Mailman-Approved-At: Sat, 18 Apr 2015 15:54:11 -0700
Cc: "kitten@ietf.org" <kitten@ietf.org>, "hartmans-ietf@mit.edu" <hartmans-ietf@mit.edu>, "leifj@sunet.se" <leifj@sunet.se>
Subject: Re: [kitten] [Technical Errata Reported] RFC6680 (4337)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 18 Apr 2015 22:49:38 -0000

Authors,

Please let us know what you think and if you agree with the errata, is the proposed text good.

We are trying to reduce work load a bit and have chairs/authors handling errata.  Stephen and I will update once we have received guidance.

Thanks,
Kathleen 

Sent from my iPhone

> On Apr 18, 2015, at 5:52 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC6680,
> "Generic Security Service Application Programming Interface (GSS-API) Naming Extensions".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6680&eid=4337
> 
> --------------------------------------
> Type: Technical
> Reported by: Benjamin Kaduk <kaduk@mit.edu>
> 
> Section: 7.5
> 
> Original Text
> -------------
>   This function outputs the value(s) associated with a given GSS name
>   object for a given name attribute.
> 
> Corrected Text
> --------------
>   This function outputs the value(s) associated with a given GSS name
>   object for a given name attribute.  It is permitted to block pending
>   network interactions when the attr input is not an attribute which
>   would be included in the attrs output of a call to GSS_Inquire_name()
>   on the same name input.
> 
> 
> Notes
> -----
> RFC 6680 makes no mention of blocking or not blocking on network interaction, though RFC 2743 does.  This seems like the most reasonable interpretation of what is currently in RFC 6680.  Calls which are not explicitly permitted to block are assumed to be not permitted to block.
> 
> 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 (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6680 (draft-ietf-kitten-gssapi-naming-exts-15)
> --------------------------------------
> Title               : Generic Security Service Application Programming Interface (GSS-API) Naming Extensions
> Publication Date    : August 2012
> Author(s)           : N. Williams, L. Johansson, S. Hartman, S. Josefsson
> Category            : PROPOSED STANDARD
> Source              : Common Authentication Technology Next Generation
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>