Re: [kitten] Opsdir last call review of draft-ietf-kitten-rfc5653bis-05

Joe Clarke <jclarke@cisco.com> Wed, 06 September 2017 14:19 UTC

Return-Path: <jclarke@cisco.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 423B9132FC0; Wed, 6 Sep 2017 07:19:28 -0700 (PDT)
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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 1EzwDmFJ6ced; Wed, 6 Sep 2017 07:19:27 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA3F8132FC1; Wed, 6 Sep 2017 07:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1232; q=dns/txt; s=iport; t=1504707566; x=1505917166; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=4BcDq4sKkI0C8B7GkODXrOo72dtA6zSGmKGieZXh8RM=; b=jo4qtMqmHddrAU9+gpN0fIDEdtqNEh4qgFIaWtc0tlsecBsPZ8v1quJg yEoHX26VLXGhdu87IrP0kjm20j4PAgo7Z78PHSwQeFD6hPhzHwcQxdPlw s2P4M66uyODSp+LYek5XpHCrMkEXbVIJRqEDlHhtEy+JlxICvTKhJFHIY 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CSAgDpArBZ/4cNJK1eGQEBAQEBAQEBAQEBBwEBAQEBg1qBeYN3mkKBTyKYOgqFPgKEPEMUAQIBAQEBAQEBayiFGAEBAQECASNWEAsYAgImAgJXBg0GAgEBiiUIrhWCJ4s4AQEBAQEBAQEBAQEBAQEBAQEhgQ2CHYICgU6BYysLgnKICIJhBaB0lFGLVIcdlSuBOTYhgQ1TJBWFYRyCAyQ2iiUBAQE
X-IronPort-AV: E=Sophos;i="5.41,484,1498521600"; d="scan'208";a="482127587"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Sep 2017 14:19:26 +0000
Received: from [10.118.87.94] (rtp-jclarke-nitro13.cisco.com [10.118.87.94]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v86EJPwd004963; Wed, 6 Sep 2017 14:19:25 GMT
To: Weijun Wang <weijun.wang@oracle.com>
Cc: ops-dir@ietf.org, kitten@ietf.org, ietf@ietf.org, draft-ietf-kitten-rfc5653bis.all@ietf.org
References: <150463800843.29826.6748894127604407016@ietfa.amsl.com> <2D53D28B-DCAD-485C-A8E5-182EA9C13F16@oracle.com> <54e49125-b10e-b756-19fe-57b78594efe0@cisco.com> <C13B158F-ABAD-4B7F-B863-B975C1196746@oracle.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco
Message-ID: <b96bf6aa-74f6-0135-8e72-dafce869df65@cisco.com>
Date: Wed, 06 Sep 2017 10:19:25 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <C13B158F-ABAD-4B7F-B863-B975C1196746@oracle.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/o0F0vhskq55s59b-3GtnALnB_2w>
Subject: Re: [kitten] Opsdir last call review of draft-ietf-kitten-rfc5653bis-05
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 06 Sep 2017 14:19:28 -0000

On 9/6/17 10:17, Weijun Wang wrote:
> Hi Joe
> 
>> On Sep 6, 2017, at 9:00 PM, Joe Clarke <jclarke@cisco.com> wrote:
>>
>> "A program that intends to run with both old and new GSS Java bindings
>> can use reflection to check the availability of this new method and call
>> it accordingly."
> 
> Accepted. You do not mean to remove the existing "New JGSS programs should make use of this new method but it is not mandatory" sentence, right?

Correct.  I was just changing that last sentence.  I intended you to
keep the quoted sentence you have above.

> 
> Is there anything else I need to touch before posting the -06 version of this ID?

Not from my OPS-DIR review.

> 
>> But my experience with Java is that you may not get the jar you expect,
>> and changes like this that are said to be "compatible" can often bite you.
> 
> Since this is inside Java SE, hopefully the situation is better than a 3rd party API. Of course, with the new modularized structure introduced in JDK 9, people might start making JDK images of their own which contain modules from different releases and different vendors...

Yes.  It was really the "compatible" word that piqued my thinking.

Joe

> 
> Thanks
> Max
>