Re: [weirds] Ted Lemon's Discuss on draft-ietf-weirds-rdap-query-16: (with DISCUSS and COMMENT)

Pete Resnick <presnick@qti.qualcomm.com> Thu, 30 October 2014 00:32 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4AA61ACE70; Wed, 29 Oct 2014 17:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 wN_NUeBLFByK; Wed, 29 Oct 2014 17:32:43 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0338F1ACE71; Wed, 29 Oct 2014 17:32:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1414629163; x=1446165163; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=QVmPevajKZTwi5aVRTqs2kKm0pDnN3ojl/hPSfFSNEQ=; b=VdkLcmeJA9CQPuaOTFqw2mJI28OkPei142XE4xmFOaSoYGtkrbQ/TOAU WTrEnYshC+VJItdbYC6zJW04tVWBxGmpY50zA958hMGaICRLnpEz0ttIm GwS0CIvzvnoBrmbd4AOnFOl7RJIIh+TrB39vCur7q1Vq2uHCR2MoJeZmt c=;
X-IronPort-AV: E=McAfee;i="5600,1067,7606"; a="171510490"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Oct 2014 17:32:42 -0700
X-IronPort-AV: E=Sophos;i="5.07,281,1413270000"; d="scan'208";a="765615286"
Received: from nasanexhc11.na.qualcomm.com ([172.30.39.6]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Oct 2014 17:32:42 -0700
Received: from NASANEXM01F.na.qualcomm.com (10.46.201.192) by nasanexhc11.na.qualcomm.com (172.30.39.6) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 29 Oct 2014 17:32:41 -0700
Received: from apc-qrc004-rpdu-k02-lf.qualcomm.com (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.46.201.192) with Microsoft SMTP Server (TLS) id 15.0.913.22; Wed, 29 Oct 2014 17:32:35 -0700
Message-ID: <54518722.2040005@qti.qualcomm.com>
Date: Wed, 29 Oct 2014 17:32:34 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <20141029184749.10576.92440.idtracker@ietfa.amsl.com> <54517E02.6020501@qti.qualcomm.com> <FE21B784-4961-40CB-9556-2CE3ACDCBF64@nominum.com>
In-Reply-To: <FE21B784-4961-40CB-9556-2CE3ACDCBF64@nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (129.46.53.226) To NASANEXM01F.na.qualcomm.com (10.46.201.192)
Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/-xdpk9Vy7X2rI6QHJN88TS3Q4Og
Cc: weirds-chairs@tools.ietf.org, The IESG <iesg@ietf.org>, draft-ietf-weirds-rdap-query@tools.ietf.org, weirds@ietf.org
Subject: Re: [weirds] Ted Lemon's Discuss on draft-ietf-weirds-rdap-query-16: (with DISCUSS and COMMENT)
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Oct 2014 00:32:45 -0000

On 10/29/14 5:09 PM, Ted Lemon wrote:
> On Oct 29, 2014, at 7:53 PM, Pete Resnick<presnick@qti.qualcomm.com>  wrote:
>    
>> A client that does the right thing and only queries all-a-label or all-u-label strings is going to get consistent results, because it is taking responsibility to do the appropriate mappings. But if the client is blindly handing over labels it got from somewhere else (which is why you would get mixed stuff),
>>      
> Why would the client do that?

Because clients get their input from all sorts of weird places, and some 
not-so-smart clients do not have the machinery to do the right thing. 
They SHOULD, but they don't.

> Why not specify what the right thing is for the client to do as a SHOULD, and _then_ explain what might break if it doesn't, rather than just sort of talking about it and hoping for the best?
>    

But that's exactly what the second full paragraph of 3.1.3 says now: 
SHOULD be either U-Labels or A-Labels, might break if not (see section 
6.1), here are reasons you might see brokenness, and servers can do what 
they will to make things right.

> Also, U-labels are case-sensitive.   So the semantic difference you're describing doesn't actually exist.

If servers could count on only getting real U-labels, of course. And if 
servers could simply reject crappy input out of hand, life would be much 
simpler. But AFAIU this is a case in which some servers (which serve 
particular constituencies) have to be a bit liberal in what they accept. 
So I think we have to give some information in the document about what 
to do when you get "interesting" input.

> (BTW, what I just explained in the above paragraph gives me a headache and tells me we should _never_ use IDN for any writing system that has case, because it will be insanely easy to spoof.   But you probably already knew that.)
>    

:-)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478