Re: [netmod] Whitespace in XML encoding - allowed ?

Kent Watsen <kwatsen@juniper.net> Tue, 09 October 2018 17:24 UTC

Return-Path: <kwatsen@juniper.net>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9699A127332 for <netmod@ietfa.amsl.com>; Tue, 9 Oct 2018 10:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.157
X-Spam-Level:
X-Spam-Status: No, score=-3.157 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 ZXuxFOaxVNL4 for <netmod@ietfa.amsl.com>; Tue, 9 Oct 2018 10:24:20 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 9BE34126CB6 for <netmod@ietf.org>; Tue, 9 Oct 2018 10:24:20 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w99HO37m015311; Tue, 9 Oct 2018 10:24:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=Q6FeRT2T23M0e+uwK3jRLgAmwtZvnf1i+8llU+/BvKY=; b=UuwhVm2oV1lSEQzOU1/xYxcQ6gnnnNbx+1KRTjqx16kmRo8NNSd8HJw45A74MKwjh/lA NkF08ctpgG9+eYbXOQPh1vMKq7KY9bxEjgnksGI/2Axhg0VzRAfue4xpTKpTHNcpzSKs VoH+AAxnPcuZDF5kBfgBz4GCqedOanG6Mwbz63lbqyXe/gnazXUGKMFn/uWxg+bi6mHx jJbIaG5a/SX2P2v8o7Wa7xjyvRCVMcov1y9XrbQpn3lMdyLH6HdmdEcTdvEw5IdHDtyM 0eiJ5bSP0r5SxTjCKmZr0oE87kPkQjXyjR2IrOaPpcMaVuF05nQX4k7HFlg4yhabVtXO Tw==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0023.outbound.protection.outlook.com [207.46.163.23]) by mx0b-00273201.pphosted.com with ESMTP id 2n0s0pgykw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 09 Oct 2018 10:24:18 -0700
Received: from BYAPR05MB4664.namprd05.prod.outlook.com (52.135.233.78) by BYAPR05MB4933.namprd05.prod.outlook.com (52.135.235.204) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.19; Tue, 9 Oct 2018 17:24:15 +0000
Received: from BYAPR05MB4664.namprd05.prod.outlook.com ([fe80::d45d:b92d:3e87:ef9f]) by BYAPR05MB4664.namprd05.prod.outlook.com ([fe80::d45d:b92d:3e87:ef9f%3]) with mapi id 15.20.1228.020; Tue, 9 Oct 2018 17:24:15 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Ladislav Lhotka <lhotka@nic.cz>, Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Whitespace in XML encoding - allowed ?
Thread-Index: AQHUX65zMY3LKhsc8UeIQzNDxdo7xaUWuNSAgAAuoYA=
Date: Tue, 09 Oct 2018 17:24:15 +0000
Message-ID: <BFEC1F81-8447-4B51-82CB-0E944E843F63@juniper.net>
References: <14e78aaa-4508-970a-d1a0-e091ffaf5c8e@ericsson.com> <871s8zh0cu.fsf@nic.cz>
In-Reply-To: <871s8zh0cu.fsf@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.2.180910
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB4933; 6:p0UB1/vV22Af+dIuueHYZ9MsIvzOr1WavfihqjmS9kOIKLu/AR4e9kRZdcfvMNClML4mfh5xXbqePMB+L1G+LHmGZNsWVj+ps9lCnWXncgN4Gl54p7h2EDUONjvoN+pmbcgYdEZ/NxqQWNWYBJmkvSp30Pntqei5cBV2clscMMH9xRyv4RD+yIy2TUwXOeFtKS4bKp3hEM97R7vFx8RIFnzfEbLDHhcQ+UQjIM/mxtNGEgWwQPmVN2USWxEvjf+36NZP6FNtZutZR+G2XaHvunCiAiyp77jqsPtPMB5bNy3DTe1TsfHZ7toBqi2IJJZ7CrkD43v2t2vsRWZZNhY8f9P14FDf3B1VA+Jej3ycaeuCVmXnAxnEu6RB7AOnIzk3UQnDNM48VVRWsH+tRfGkiN8T0kARU3uMnEU1rng6V/2MnNZgDNkjS05xXWPy37qhsI7bOhbizUirU16GsAziGQ==; 5:lWKDUWsvbsQeBPHvrrvalXikHJRj/ZnNoWCGqF6mbWQy8pMjctimJ0adX/PpRINcGGoDpTPB4DpNmMWXzsDgwpQRysRIP6iWet5ssqBfZICW2KGdhhZSBlfdKKMAfRgb3LcA8vW+hYgm/O6xSNDETMxGssp+0BS93HeFq3zoFa8=; 7:wddzFnkC7aAW6SHqUtv8spAvIMAcunNMv7P+GsdX/3ME+vIzKXHQ6tMdHkj8vVk+w0wZEXBaFjbp/Ra5DnBDvgsqVRDx9q3yu0cqfODZVkolC3FzKDk4swTghiZ6Iaa567hf5ezzJbzlCrewe2N9RXipe695p51S1MZQ4bQrcSDX5rHSNePJJaZJGImfbeQA1/HN7d8K4EfcV8vH3dnliRKkotmodBU/hK2Zt3YMS4z9ONVgv7DovMEH3zplFgWI
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 6faa535c-f01c-4263-cea8-08d62e0c09a2
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB4933;
x-ms-traffictypediagnostic: BYAPR05MB4933:
x-microsoft-antispam-prvs: <BYAPR05MB4933051433EA071C493CC28AA5E70@BYAPR05MB4933.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(3231355)(944501410)(52105095)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(201708071742011)(7699051); SRVR:BYAPR05MB4933; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB4933;
x-forefront-prvs: 08200063E9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(366004)(396003)(376002)(39860400002)(199004)(189003)(2906002)(110136005)(305945005)(478600001)(58126008)(316002)(229853002)(6436002)(8936002)(6246003)(86362001)(26005)(486006)(558084003)(7736002)(11346002)(2616005)(476003)(446003)(186003)(6506007)(14454004)(76176011)(2900100001)(3846002)(6116002)(33656002)(102836004)(53936002)(6512007)(106356001)(99286004)(82746002)(36756003)(5660300001)(105586002)(5250100002)(66066001)(2501003)(68736007)(25786009)(8676002)(81156014)(6486002)(81166006)(97736004)(256004)(71200400001)(71190400001)(83716004); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4933; H:BYAPR05MB4664.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: tDWLh9sFk+h0B0Bl7RCiuk+8cBCSwwQvGcVM5vPGLGQrrUZxnma60pM4aNB0zbD09lNqibFm2J0G7VlsNgP/wux5F8WSakqzgVC0Al2OknpdANIcxtkPcjKHg/KKCCMINR1bDQP6TW0D0xV6sSdpRvoS0TLdrSXBLqS/MuLWrv++K51ClLEiurXDt/tgo7G6bFpn8JQa3p4Q/HlBkNznv/1Q1TRxsajnhtRDLEeuxL9BSiLDcCSF1ciqJOTr5jWSCdm6Yfn+RgnUhK/+ezN0zLF0GF7Dayrh4oiIaxpnVLmHhI8W08cw4KX7HTNkMliuuJLe3kQnAn5Cecd+Z5pQahmWA2x2bqKUPXFv1uYmTwA=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <7E9098C5DC810141920AC2405F924AAC@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 6faa535c-f01c-4263-cea8-08d62e0c09a2
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2018 17:24:15.4172 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4933
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-10-09_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=919 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810090168
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/gSTEG8WQTWeE1JohP2JOasQdFzI>
Subject: Re: [netmod] Whitespace in XML encoding - allowed ?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2018 17:24:23 -0000

As Martin points out, this is how XML works.

As a result, XML instance documents are poster-child examples for why long lines occur sometimes, and where the artwork-folding draft shines when placing said examples into drafts.

Lada, good point, but would there be a layer violation?

Kent // contributor