[Trans] pasting URL's

"Salz, Rich" <rsalz@akamai.com> Fri, 26 March 2021 19:38 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400403A0B5F for <trans@ietfa.amsl.com>; Fri, 26 Mar 2021 12:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.251, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 GhP3DN9lB5XN for <trans@ietfa.amsl.com>; Fri, 26 Mar 2021 12:38:22 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5C43A0B58 for <trans@ietf.org>; Fri, 26 Mar 2021 12:38:22 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 12QJYvhY015275 for <trans@ietf.org>; Fri, 26 Mar 2021 19:38:21 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=cnlz9gQmIjYV9Zjb+l2ggxOVLmrqcMxru7yZ8ZZvp6o=; b=IY9/5gu8ihIUTWw7zbpEYSW/0lf6NoQAjGzWNShchmjekqAUaTZGQzWyIjuDcARvbn1o 9L/2cY45HtKWTQPZYcTtkHsEY13gT0KBeGTc5uyKGc7xI4hpna3Fg45MSrofijJdjFg+ HAufEDV8fBBGagsE7kCyg6qr9MfaEo+XSnR7N7wpHrCLE1+ZbvmITRVkRdyfU+BU3rBB w6trLHw1CjIyHsLbgL3QCkRbbTA3CsWmbz75gSUuf1tSF5T0r0uGTdgcvv23OO4T1xWv XJ1885MgI0cWw/c77fAUM5pDT+C/3FDpz++hPW/02D8SQtVUxo3Pr0LTf9itDpNBQz0r ww==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 37h15wgp9m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <trans@ietf.org>; Fri, 26 Mar 2021 19:38:20 +0000
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 12QJahno024418 for <trans@ietf.org>; Fri, 26 Mar 2021 15:38:20 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint6.akamai.com with ESMTP id 37h18ajqms-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <trans@ietf.org>; Fri, 26 Mar 2021 15:38:20 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 26 Mar 2021 15:38:19 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.012; Fri, 26 Mar 2021 15:38:19 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "trans@ietf.org" <trans@ietf.org>
Thread-Topic: pasting URL's
Thread-Index: AQHXIneSkEq2oxrI7k6q91mYxt9H5g==
Date: Fri, 26 Mar 2021 19:38:19 +0000
Message-ID: <956778BF-4E5D-49EF-8B93-98D59D6C19BF@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.47.21031401
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.118.139]
Content-Type: multipart/alternative; boundary="_000_956778BF4E5D49EF8B9398D59D6C19BFakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-26_11:2021-03-26, 2021-03-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 adultscore=0 malwarescore=0 mlxscore=0 mlxlogscore=838 bulkscore=0 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2103250000 definitions=main-2103260145
X-Proofpoint-GUID: YCAeibgGv9FhVsxuyvWqFbGuzx6dW8y_
X-Proofpoint-ORIG-GUID: YCAeibgGv9FhVsxuyvWqFbGuzx6dW8y_
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-26_11:2021-03-26, 2021-03-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 bulkscore=0 spamscore=0 clxscore=1015 impostorscore=0 mlxlogscore=765 adultscore=0 mlxscore=0 phishscore=0 priorityscore=1501 malwarescore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2103250000 definitions=main-2103260145
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 184.51.33.61) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint6
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/buN5hy4bkpUbbB7zsB8L13M9jiM>
Subject: [Trans] pasting URL's
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2021 19:38:27 -0000

In https://datatracker.ietf.org/doc/draft-ietf-trans-rfc6962-bis/ballot/ Adam Roach (former AD) makes the following COMMENT.  Note his paragraph that says “Unless the intention…”  I don’t know why this is a COMMENT and wasn’t a DISCUSS.

What are we going to do?  Ignore the comment:


>  Clients are configured with a base URL for a log and construct URLs
>  for requests by appending suffixes to this base URL.  This structure
>  places some degree of restriction on how log operators can deploy
>  these services, as noted in [RFC7320].  However, operational
>  experience with version 1 of this protocol has not indicated that
>  these restrictions are a problem in practice.

The synthesis of URLs by a protocol in this fashion is prohibited by BCP 190:

   Scheme definitions define the presence, format, and semantics of a
   path component in URIs; all other specifications MUST NOT constrain,
   or define the structure or the semantics for any path component.

Unless the intention of this document is to update BCP 190 to change this
normative requirement, we can't publish it in its current form. Note that doing
so would require a change of venue, as updates to BCP 190 would not be covered
by the current TRANS charter.

Please see BCP 190 section 3 for alternate approaches. All three approaches
could be made to work for CT, and I would be happy to explain how to do so if
clarification is desired.