Re: [provreg] RFC 5733: street changes with contact:update

齐超 <qichao@cnnic.cn> Fri, 15 November 2013 05:33 UTC

Return-Path: <qichao@cnnic.cn>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEE8611E8119 for <provreg@ietfa.amsl.com>; Thu, 14 Nov 2013 21:33:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.5
X-Spam-Level:
X-Spam-Status: No, score=-93.5 tagged_above=-999 required=5 tests=[AWL=1.431, BAYES_40=-0.185, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4oxa7OIufbMw for <provreg@ietfa.amsl.com>; Thu, 14 Nov 2013 21:33:48 -0800 (PST)
Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 9751A11E8127 for <provreg@ietf.org>; Thu, 14 Nov 2013 21:33:45 -0800 (PST)
X-EYOUMAIL-SMTPAUTH: qichao@cnnic.cn
Received: from unknown218.241.111.100 (HELO qichao) (218.241.111.100) by 218.241.118.7 with SMTP; Fri, 15 Nov 2013 13:33:42 +0800
Date: Fri, 15 Nov 2013 13:33:44 +0800
Organization: CNNIC
From: =?GB2312?B?xuuzrA==?= <qichao@cnnic.cn>
To: "provreg@ietf.org" <provreg@ietf.org>, "Klaus Malorny" <Klaus.Malorny@knipp.de>
References: <5284EE10.5020809@knipp.de>
X-Priority: 3
X-Mailer: Foxmail 7.0.1.76[cn]
Mime-Version: 1.0
Message-ID: <20131115133344234416115@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart523775815062_=----"
Subject: Re: [provreg] RFC 5733: street changes with contact:update
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>, <mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>, <mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Nov 2013 05:33:54 -0000

Hello, Klaus,

I think it is necessary to come to a conclusion what is meaning of  label <contact:street> :
1,   two <street> is alternative,  e.g.
   C:            <contact:street>one address</contact:street>
   C:            <contact:street>another address</contact:street>
   C:            <contact:city>Dulles</contact:city>
   C:            <contact:sp>VA</contact:sp>
   C:            <contact:pc>20166-6503</contact:pc>
   C:            <contact:cc>US</contact:cc>  
2,   two <street>  is supposed to be composed to a complete address, e.g.
   C:            <contact:street>high level of address</contact:street>
   C:            <contact:street>low level of address</contact:street>
   C:            <contact:city>Dulles</contact:city>
   C:            <contact:sp>VA</contact:sp>
   C:            <contact:pc>20166-6503</contact:pc>
   C:            <contact:cc>US</contact:cc>

for 1, replacing one is acceptable.

for 2, replacing all is reasonable.


The RFC5733 example is :
   C:            <contact:addr>
   C:              <contact:street>124 Example Dr.</contact:street>
   C:              <contact:street>Suite 200</contact:street>
   C:              <contact:city>Dulles</contact:city>
   C:              <contact:sp>VA</contact:sp>
   C:              <contact:pc>20166-6503</contact:pc>
   C:              <contact:cc>US</contact:cc>
   C:            </contact:addr>

Two streets 'Suite 200' and '124 Example Dr.' is not obvious for me...  Can anybody explain it?