From nobody Tue Mar 1 08:08:42 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609611B3B86 for ; Mon, 29 Feb 2016 12:24:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.621 X-Spam-Level: X-Spam-Status: No, score=0.621 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no 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 4CSpeQWNPaoq for ; Mon, 29 Feb 2016 12:24:04 -0800 (PST) Received: from pechora3.lax.icann.org (pechora3.icann.org [IPv6:2620:0:2d0:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 725E51B3B85 for ; Mon, 29 Feb 2016 12:24:04 -0800 (PST) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id u1TKNhHP002571 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Feb 2016 20:24:04 GMT Received: by mail-io0-x231.google.com with SMTP id l127so199366687iof.3 for ; Mon, 29 Feb 2016 12:24:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coactus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=xXp2dger1BfgH6LL6RSgbKe8EILNiujQRL+EaaIKV2c=; b=yw3kTQVfzfXZ4gl1Y/7kiFd29W7Je0v8A0Twj7G4uwSUfFZAUdUWq0FnhqsEArV8I1 pPcv/AvgCRVzXOO8/8vqr1PvjZkfLQkYCTVA0HpyxQQIkt8IIP7J1mxuUCwoe0m3ii2O SciWDPC9NQvBR8ssGiImI3N8U75szz+lpl2kmown99oiVBeyGFtvRrBY8XeVeaQQp8EO OcwVuipVTzqoLtZ9JTf0bJ9sg5VoQS/8pHflmp9E+VCtc+d5vVeJ4I7iNz+ABWKdR4O2 BH/bXZRpGPrOWlSpUXFw7wDMRJRdVXqmmjAG04IOPGHkMRXNrktA61+v1+jL9ZTyyyGF qd0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=xXp2dger1BfgH6LL6RSgbKe8EILNiujQRL+EaaIKV2c=; b=E2W4LW55nM8kdtDTkszqj1l/GcqUJIEdiI586S7D8ZGcMh0UQX5tDCmJl1xUMFrCCA BwZk/a3y4ZQ9w5dboVinKsq+9AdEFzUx5EjUNxPTSACT6KB/tRxD9oRBhTC070+TFt6w 9kNYI6P0zVzl2G5aH8P40OiTq2aZbl1DT/pqf2eH9s/GOYcqfppr67SLYHTt11MccBUt DAtCFY22F/xN/OjQUGYbHRItybQWDxuH+FOTHfo5kIboBasuD4Xoxj1Oqa96t5eQ7ryy UAlm1Kw+TqyP9ZOE22FPJ2uMXv/qmktU4zqY6B86G7LCVb1r4HSgf9D6NbWksiMdUuYo BwzQ== X-Gm-Message-State: AG10YOSQbFyEoM2fdxjy5Xn5024XYeZFcdzxXCrnOFf7wMdDQkmeUslvPLisejy65MZjyWmtoO0FhNJozt3lSg== MIME-Version: 1.0 X-Received: by 10.107.9.193 with SMTP id 62mr21495077ioj.27.1456777423469; Mon, 29 Feb 2016 12:23:43 -0800 (PST) Sender: mark@coactus.com Received: by 10.64.167.171 with HTTP; Mon, 29 Feb 2016 12:23:43 -0800 (PST) X-Originating-IP: [98.103.17.38] In-Reply-To: References: Date: Mon, 29 Feb 2016 15:23:43 -0500 X-Google-Sender-Auth: qzMwI0hxjT7_R0i-613vHnFMWgg Message-ID: From: Mark Baker To: "Van De Velde, Gunter (Nokia - BE)" Content-Type: text/plain; charset=UTF-8 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [IPv6:2620:0:2d0:201::1:73]); Mon, 29 Feb 2016 20:24:04 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Tue, 01 Mar 2016 08:08:41 -0800 Cc: "ietf-types@iana.org" , "Henderickx, Wim \(Nokia - BE\)" , "Simpson, Adam 1. \(Nokia - CA\)" Subject: Re: [media-types] Request for "first come first serve" codepoint allocation for draft-ietf-idr-flowspec-redirect-ip X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 20:24:06 -0000 Hi Gunter. ietf-types@iana.org is for IANA registration of Internet media types, while what you appear to be registering here is something different. Unfortunately, after a quick look around, I've been unable to find where your type of registration needs to be made, but perhaps your AD would know. From nobody Tue Mar 1 08:08:44 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14EA41B3C23 for ; Mon, 29 Feb 2016 13:08:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.664 X-Spam-Level: X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 SzxnLiiyYJCT for ; Mon, 29 Feb 2016 13:08:12 -0800 (PST) Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4792E1B3C28 for ; Mon, 29 Feb 2016 13:08:12 -0800 (PST) Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id u1TL7oTE017101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Mon, 29 Feb 2016 21:08:11 GMT Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 51BB9B0DAE04C; Mon, 29 Feb 2016 21:07:45 +0000 (GMT) Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u1TL7n4R002701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 29 Feb 2016 21:07:49 GMT Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u1TL7mV6010392 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Feb 2016 22:07:49 +0100 Received: from FR711WXCHMBA06.zeu.alcatel-lucent.com ([169.254.2.137]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Mon, 29 Feb 2016 22:07:49 +0100 From: "Van De Velde, Gunter (Nokia - BE)" To: EXT Mark Baker Thread-Topic: [media-types] Request for "first come first serve" codepoint allocation for draft-ietf-idr-flowspec-redirect-ip Thread-Index: AQHRcy8Z3hdgc3Ad9Ea3ySYMU8zvfJ9DhBsA Date: Mon, 29 Feb 2016 21:07:47 +0000 Message-ID: <1B17A3AF-256A-4F76-B392-426057F4E775@alcatel-lucent.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.41] Content-Type: text/plain; charset="utf-8" Content-ID: <5E37C330736B304F925BD78116918430@exchange.lucent.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [192.0.46.73]); Mon, 29 Feb 2016 21:08:11 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Tue, 01 Mar 2016 08:08:41 -0800 Cc: "ietf-types@iana.org" , "Henderickx, Wim \(Nokia - BE\)" , "Simpson, Adam 1. \(Nokia - CA\)" Subject: Re: [media-types] Request for "first come first serve" codepoint allocation for draft-ietf-idr-flowspec-redirect-ip X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Feb 2016 21:08:15 -0000 TWFueSB0aGFua3MgTWFyay4NCg0KT25lIG9mIHlvdXIgY29sbGVhZ3VlcyBwcm92aWRlZCBtZSBz aW1pbGFyICBpbmZvcm1hdGlvbi4gSeKAmW0gcmVhY2hpbmcgb3V0IHRvIHRoZSBBROKAmXMgdG8g c2VlIGlmIHRoZXkgaGF2ZSBhIGNsdWUgd2hpY2ggZW1haWwgbGlzdCBpIHNob3VsZCB1c2UuIEkg bG9va2VkIG15c2VsZiBhcm91bmQgYWxzbywgYW5kIGl0IHNlZW1zIG5vdCB0cml2aWFsIHRvIGlk ZW50aWZ5IGl0LiBJIGhvcGUgdGhlIEFE4oCZcyBjYW4gaGVscCBtZSBvdXQuDQoNCkJlIHdlbGwg YW5kIG1hbnkgdGhhbmtzIGFnYWluIGZvciB5b3VyIHN3aWZ0IGFkdmljZS4NCg0KRy8NCg0KDQoN Cg0KT24gMjkvMDIvMTYgMjE6MjMsICJtYXJrQGNvYWN0dXMuY29tIG9uIGJlaGFsZiBvZiBFWFQg TWFyayBCYWtlciIgPG1hcmtAY29hY3R1cy5jb20gb24gYmVoYWxmIG9mIGRpc3RvYmpAYWNtLm9y Zz4gd3JvdGU6DQoNCj5IaSBHdW50ZXIuIGlldGYtdHlwZXNAaWFuYS5vcmcgaXMgZm9yIElBTkEg cmVnaXN0cmF0aW9uIG9mIEludGVybmV0DQo+bWVkaWEgdHlwZXMsIHdoaWxlIHdoYXQgeW91IGFw cGVhciB0byBiZSByZWdpc3RlcmluZyBoZXJlIGlzIHNvbWV0aGluZw0KPmRpZmZlcmVudC4gVW5m b3J0dW5hdGVseSwgYWZ0ZXIgYSBxdWljayBsb29rIGFyb3VuZCwgSSd2ZSBiZWVuIHVuYWJsZQ0K PnRvIGZpbmQgd2hlcmUgeW91ciB0eXBlIG9mIHJlZ2lzdHJhdGlvbiBuZWVkcyB0byBiZSBtYWRl LCBidXQgcGVyaGFwcw0KPnlvdXIgQUQgd291bGQga25vdy4NCg== From nobody Tue Mar 1 08:08:46 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 238BA1A8BB2 for ; Mon, 29 Feb 2016 18:44:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.875 X-Spam-Level: * X-Spam-Status: No, score=1.875 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, MIME_8BIT_HEADER=0.3, SPF_SOFTFAIL=0.665, T_DKIM_INVALID=0.01] autolearn=no 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 YR_Z0f5I8IAu for ; Mon, 29 Feb 2016 18:44:51 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7DBB1A8BB5 for ; Mon, 29 Feb 2016 18:44:50 -0800 (PST) Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-hk2apc01on0109.outbound.protection.outlook.com [104.47.124.109]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id u212iSPv029249 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Tue, 1 Mar 2016 02:44:50 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XN8hMhNV0144c8sXK20jXxhZ6hYhdzW+ncdqLstBMSE=; b=JPP7EHzkAYeDpCCfkLCgcWVe+QHoL7Kt0DP3vE8Zh6wva29IqTnnKCkYlrGqPWId10/rEUjPewbDfN+3UZ6Gp6wj8Y7u+SsJ2sBkqvpJcj64sVFMqBWr3+wD3Ik3oWEeERWhtMYm+y/8qADoUt7mVHmKDDQ8swkFKnF+N0UJRRs= Authentication-Results: nokia.com; dkim=none (message not signed) header.d=none;nokia.com; dmarc=none action=none header.from=it.aoyama.ac.jp; Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0144.jpnprd01.prod.outlook.com (10.161.134.148) with Microsoft SMTP Server (TLS) id 15.1.415.20; Tue, 1 Mar 2016 02:44:26 +0000 To: "Van De Velde, Gunter (Nokia - BE)" , "ietf-types@iana.org" References: From: "=?UTF-8?Q?Martin_J._D=c3=bcrst?=" Organization: Aoyama Gakuin University Message-ID: <56D5020A.7080201@it.aoyama.ac.jp> Date: Tue, 1 Mar 2016 11:44:26 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [133.2.210.64] X-ClientProxiedBy: TY1PR0201CA0042.apcprd02.prod.outlook.com (25.164.90.180) To TY1PR01MB0144.jpnprd01.prod.outlook.com (25.161.134.148) X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 2:GpicA7z8QglOeXfqbTtCTsDS+LExP0uISAlOkiW6yCetLdCRn1LrHJG6abStVaUPH0OhVjBQl51hK3kmNSE3vP16gJfsyeBUu37KmLcuwvFW9t8bABI+VYRYR7CU/frFr1hjLB2cgLpZO0byH8y0vw==; 3:DbnkJd6zAaCx18KjfJDFRe0+s0Xt1OkN4/HtWTzm8yzOlrDWHNWoXwud3MkKXi0Jspzyb+enIImqgJCvDDhSZ4oaeCLkUHT0sQw7Wq/R9Yd2M/Ea/FmYSEYsVuu+5UIO; 25:uGKbVuuM6ZQOllrk9xgtmQ01al7TRT9u5N8mawUq9gJ/CiZ21Ww5gCwl+7rtGy1RQi2mY5IFUYjxQE6xFO2YzYiAywhM4vnI2xcZUZIbwxjnkvNxicmyUB4fkH44GHFWZiO6c+7LZSOkR2g8oysEnaOHnjMleluYwQSfn3cxayrrGeJ61wZvXGOVhq7xh0tOtIE+Sd7YAgem0/jtGPdASXOTTHJfaaDY9OFf5g7XEVgRc0Md/H8NwPYEfvy20U2xly1nYMS5N5yuko7G1FN+kGEDNK8eqLir3Lpt+fOnEkq+HbLFWYRlcCuPm/mwRQwp7l5NclODrD063F9f21i82Q== X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0144; X-MS-Office365-Filtering-Correlation-Id: 9c6a42e9-c310-4746-cdde-08d3417b67af X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:TY1PR01MB0144; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0144; X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 4:SxqwTwPMYM3VpMnNM5Md0b2XlhrETmSgsZzgNDBiBCXCqJGuHqh1mkzv/z8P+PcaBq6OGq4KrDFXTWIPhxr2XHVrhJE5g4uGOOtjuXLGBvQZ5WG2OgtSjzLoqD2h08gmna9XgSh8k3pC5eCFESFH18+uyOOqq/SgX0swFVQlH2CqIM3U9H7sOaqODjuCBdYTyz81+VOTWpBeVUoRVQ5HCBfAj83UwERQmRg9Q5yBcJzYdaz2jO9I8Efp3pKuw/X6cl0NwrLbULHFamNKUipWW8J8d3P6yUSWDijbYs0huvNvbMcciaNDoEOKygCOsbjbR6jfFxlvz3Qgzvp/DDDKev9R1jWQ8jjCXCwAhC9IZOM= X-Forefront-PRVS: 086831DFB4 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(6049001)(479174004)(71364002)(24454002)(2906002)(122386002)(2501003)(19580395003)(66066001)(1096002)(92566002)(33656002)(74482002)(40100003)(50466002)(64126003)(4326007)(77096005)(6116002)(586003)(80316001)(2950100001)(83506001)(3846002)(15975445007)(2870700001)(5004730100002)(87266999)(189998001)(5008740100001)(50986999)(5001770100001)(54356999)(86362001)(76176999)(23676002)(4001350100001)(42186005)(230783001)(59896002)(87976001)(81156008)(5001960100003)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0144; H:[133.2.210.64]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwMTQ0OzIzOnZEVTNVUVpQZGZVMVpna0tFK2t0RFlXbFNY?= =?utf-8?B?eWpYak1wN21uTUsySm4ybVRKdmdmZFlRZGEyeWFkeUlJU3lESVBXQVM2TUti?= =?utf-8?B?YURFQjFrTmNUY292QmVJNmxMbStUOUFSbzhCdC85R01qSk8ySnVEcUZJMHVD?= =?utf-8?B?Rm5VQnpaZlJSTjE4K21kb0YySGNzdFpqajEyNmxOeURjMGdwTXl1VWdEVkJj?= =?utf-8?B?aDlJTVBUNjZMRlh5Qk5rVHZGNGQ1ZlpUaHFyeGNuWk5nR0laSHRTSWdQYy9y?= =?utf-8?B?NEhVd0N3c296RzB5U0dRSGdUWHRMZEJxNlNmeVFjR3Qram9FNEs1S282QzZJ?= =?utf-8?B?elgvUmpyV1FqY0NZV1ZseDVLQVZ1SHl3cnZPcFJLbUc4RTZqTDdlRDM0WHNB?= =?utf-8?B?c3lUYVZFdnlWZXhxako3UnRkSzc5SzI2eUVXNHR5VytyT1RRU0Z3a28yUS9B?= =?utf-8?B?VnRjS1JDZEZpYkR1RlQ5UmJmQTZvRFhBL2Q0bDBOSHRDRThJRFUwSG9lVVlB?= =?utf-8?B?SFc0ZDR0MjdMTjZsdE8wY2RhL081ZHV0MUUzSnl0T093MklFYjdUcTdpTFcz?= =?utf-8?B?SEJvRk91Snk4OExKNW9za0k0Y2dIUWsrVy9kR3loRGpBVTJtZTVsUHFUZDI3?= =?utf-8?B?MlVoQlBPclpzR0JjMjdGM05CdFUwdG5Ca3A3cUZNeE4zeTVHUFcxV1E0a0Zo?= =?utf-8?B?QmVyOTNodnlrdUY3dnBJVmIwc3ZKbXptY014QlBxQTloYTVDUDVxWk15UXYr?= =?utf-8?B?M1ZwVmFRbmtSQmE4WVUxUjgzeEtFdk1sR3hxbWh5SktBVW5uZ2tmOVA3TS9Z?= =?utf-8?B?a0VQNGhHdXYzWE5qSWhOSE0xM1J6RkJvcjdpdjd5VzFtRzRGclJ3eHVUWC8y?= =?utf-8?B?dmYyWHFJSGJ4Yk1mQUljUFZjWGxONXM0RzVPVjVZTW1nREY5bFdpV0NZaDVv?= =?utf-8?B?cWdFUFJQRVZjcURBYnZxMFpHa2plajlVZmJiUXJadTVOdlUvQmU3VmpGbGFM?= =?utf-8?B?cnNhMkxMWGJ6bm53L2JXQzVTNXREOHFCb09jNi9sMFlOc1dJandYcmw4VFRt?= =?utf-8?B?aUVBckhsS2ZUL3IwSXJmTkdzckVzNXhNWjdMMFovREJZTWppaG9LZXUxbGo3?= =?utf-8?B?T0tHQXNnQ2cxR1RESVVjYXRsQk5EYkNkTHhoYVBTU1c3WUR3Sy9lcU1TcE1m?= =?utf-8?B?TXBjanFPU3JlRHJZUFlsb09ha3l1Q3VpZ2xYTk9GQnErZ000dGplcW8wMFht?= =?utf-8?B?SWhLZEVXcHU0clNTa3RXeUFIczY3SkNuVzFRdWtFN1RvVjFSeXNBblFPS1dw?= =?utf-8?B?ZWY5OEhHNjJtcWNabXB1RFBWR0NmYlB2eVUyQXNmcWdrQldsZG42S21HSWZj?= =?utf-8?B?RmN0NzFTR2dzTWNmV2JPdE5yYUJ3UTFEMnI0dnpBWHJDMEVwcXhtcitNWHVo?= =?utf-8?B?a1dNQkNsTFQ5SG4vdE1CU3NVK1RwcDdBUEpUZE5nRy9FNzZtZ1gwUSt4Z1dX?= =?utf-8?B?TG83VGVqeEtJL3FLMlNQdlRIMmFIYzVLMm8zOG9YR1RrSkVWalZndEk1WnVN?= =?utf-8?B?WjU5WWdoT20veVkvMklZNk9wUTFNaSttTHNtQ1VlK3h4Qzc0RHRYUlhRcVJx?= =?utf-8?B?NVRMTS8xTTU3T1F4b2VRZ1hzUm13ZEJ2Q2lMcVJEbjMrQmpDZm1UOVZBPT0=?= X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 5:hgFViylShNpmY3h/WmuSCpmpHxfDRiUm65589rKSgqQTmC+cqo9EXleXIWb36pPBb2ttUV+c3RmsW4Dzbl+wfas08YC10lVanYFzOQJt9edltG9Ub/RE8SIwzSQF3QHAB9hgdHx5bxdHHk3x52j8ww==; 24:L4iGEtLqJwT5kYnDMttLNISlyyHPESQq6B4+8zz6PaTvNb/sIIxx0dik8q0xK5EzjAp99nNqGFO1I0VnKppMBjFTFVvYk6Ml3I1s6T4ReuU= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: it.aoyama.ac.jp X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Mar 2016 02:44:26.4948 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0144 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Tue, 01 Mar 2016 02:44:50 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Tue, 01 Mar 2016 08:08:41 -0800 Cc: "Henderickx, Wim \(Nokia - BE\)" , "Simpson, Adam 1. \(Nokia - CA\)" Subject: Re: [media-types] Request for "first come first serve" codepoint allocation for draft-ietf-idr-flowspec-redirect-ip X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2016 02:44:54 -0000 Hello Gunter, Based on experience, pasting the actual registration template into the mail to this list significantly increases the chance of getting constructive comments. Regards, Martin. On 2016/02/29 19:56, Van De Velde, Gunter (Nokia - BE) wrote: > Dear IANA, > > In support of the authors of draft-ietf-idr-flowspec-redirect-ip please find this allocation request. > The draft is in such a progressed stage that there is need to obtain a codepoint allocation > for a new BGP transitive extended community sub-type (for both IPv4-address-specific > or IPv6-address-specific) form the “First Come First Served” policy. > > Requesting IETF IDR WG Document: > https://tools.ietf.org/html/draft-ietf-idr-flowspec-redirect-ip > > References: > IPv4-address-specific subtype URL Location: http://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml#trans-ipv4 > IPv6-address-specific subtype URL Location: http://www.iana.org/assignments/bgp-extended-communities/bgp-extended-communities.xhtml#trans-ipv6 > > I hope to have provided the correct info and followed correctly the procedures as documented in rfc5226 and rfc7153. > Please advice on suggested next steps if this request was made incorrectly. > > Kind Regards, > G/ > > -- > Gunter Van de Velde > > > > > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types > From nobody Tue Mar 1 19:33:18 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789881B3FAA for ; Tue, 1 Mar 2016 10:40:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.235 X-Spam-Level: X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no 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 RSD7lp5jE38C for ; Tue, 1 Mar 2016 10:40:12 -0800 (PST) Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A29911B3FA8 for ; Tue, 1 Mar 2016 10:40:12 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id u21IdpAG029007 for ; Tue, 1 Mar 2016 18:40:11 GMT Received: from [206.123.31.194] (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 29B5C476C3; Tue, 1 Mar 2016 13:39:51 -0500 (EST) From: "Marc Blanchet" To: media-types@iana.org Date: Tue, 01 Mar 2016 13:39:50 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.3r5187) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [IPv6:2620:0:2830:201::1:73]); Tue, 01 Mar 2016 18:40:11 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Tue, 01 Mar 2016 19:33:17 -0800 Cc: draft-ietf-lager-specification@ietf.org, lager WG Subject: [media-types] media-type registration request review X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2016 18:40:13 -0000 Hello, draft-ietf-lager-specification requests the registration of a new media-type. The document has passed WGLC and we would like to have a review of the request. Herein the extract of the media-type form from the draft. Thanks in advance for the review Marc, lager wg co-chair 11.1. Media Type Registration The media type "application/lgr+xml" should be registered to denote transmission of label generation rulesets that are compliant with this specification, in accordance with [RFC6838]. Type name: application Subtype name: lgr+xml Required parameters: None. Optional parameters: charset (as for application/xml per [RFC7303]) Security considerations: As for application/xml per [RFC7303] Interoperability considerations: As for application/xml per [RFC7303] Published specification: This document. Applications which use this media type: Software using label generation rulesets, including registry applications and client validators. Additional information: None. Magic number: None. File extension: .lgr or .xml Macintosh file-type code: None. Object Identifiers: None. Intended Usage: Common Personal and email address for further information: See the Authors of this document. Change Controller: IESG From nobody Fri Mar 4 11:24:02 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB2891A886D for ; Fri, 4 Mar 2016 11:23:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.621 X-Spam-Level: X-Spam-Status: No, score=0.621 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622] autolearn=no 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 HMPsPoe0U5S2 for ; Fri, 4 Mar 2016 11:23:52 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C35C91A8864 for ; Fri, 4 Mar 2016 11:23:51 -0800 (PST) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id u24JNVnX013821 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 4 Mar 2016 19:23:51 GMT Received: by mail-ig0-x230.google.com with SMTP id hb3so2664549igb.0 for ; Fri, 04 Mar 2016 11:23:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coactus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=efeFP8ek/USvXmHC5F6cq6U6ekXK3EI+p1294U8ND0g=; b=q635H+KqLOlKQVUjokNShGw7ZWSSW/0MxAgKvjAk5zl91ef2EEO8FbYlbzJWnV1nSO G7nemYck78QLcEj6HZkjbAM9P1E1fv7yfFs/KRcohwNk2JTO868FQdGGQsbQ6+03qFKN PI/Xf2tCcNJ9BLcnBxpIJgLrhB8ZSEw9d/k3UTb6hKzFhK42BiGDelzKDbH3kAC4Ljst STWjd0fJLBlwcvGEbCo6D0h0CFtO+nFiZpoGyc71QMCOc5uSSZuyluxEk9K7KWTYaG8I UotjIqeUPLS5yDRs+BHXYHFHgf19XevnUFYjloMzsusw+WBk5WIZLsdhe2p5wyAMGrY9 6Y4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=efeFP8ek/USvXmHC5F6cq6U6ekXK3EI+p1294U8ND0g=; b=hD8191I/31GiJooa0qfCdnf9SG3YpWy11rGEYBRFO86AVd+OssGBpSEWXZ5SfjaGpG vA1L7hWpsAOQLa/vBAvlr9VIi+Os6MkSGtoYLBDDDHSWwlXGHCJ9oM3Y31M0n1oWH3hQ wrbOrYg6WyU373iNruMMf2FqQywfPV0oc+wdAMljvorBWJXpvambn3cdmEEHmPl9oiIv rwXn8mvT3HxG8Mv4PbPFd2OyU+W2bmMq4K1RVmKxbWb4amEssJWeOR4KjbZYm8mGgGpI OloFxZoDAOnepePVY7pkwFyKd0RJwIDw3EPKKcq820L2b/mUfLyIRHvEJ9gJWoza66OQ kYEg== X-Gm-Message-State: AD7BkJLuC/ZK24OnGs5+FdsTe4AvzxzCdpqmr2cFKoZIbFQEPCsgYPQGhRj9z6m0970I7Awua//qZX2Ufxl/Ag== MIME-Version: 1.0 X-Received: by 10.50.61.147 with SMTP id p19mr658501igr.10.1457119410839; Fri, 04 Mar 2016 11:23:30 -0800 (PST) Sender: mark@coactus.com Received: by 10.64.167.171 with HTTP; Fri, 4 Mar 2016 11:23:30 -0800 (PST) X-Originating-IP: [24.246.8.190] In-Reply-To: References: Date: Fri, 4 Mar 2016 14:23:30 -0500 X-Google-Sender-Auth: xsFSlAxR_zlke7fAcI6qeb_SINQ Message-ID: From: Mark Baker To: Marc Blanchet Content-Type: text/plain; charset=UTF-8 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [IPv6:2620:0:2d0:201::1:74]); Fri, 04 Mar 2016 19:23:51 +0000 (UTC) Archived-At: Cc: draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG Subject: Re: [media-types] media-type registration request review X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2016 19:23:52 -0000 Hi, On Tue, Mar 1, 2016 at 1:39 PM, Marc Blanchet wrote: > Hello, > draft-ietf-lager-specification requests the registration of a new > media-type. The document has passed WGLC and we would like to have a review > of the request. Herein the extract of the media-type form from the draft. > Thanks in advance for the review > > Marc, lager wg co-chair > > > 11.1. Media Type Registration > > The media type "application/lgr+xml" should be registered to denote > transmission of label generation rulesets that are compliant with > this specification, in accordance with [RFC6838]. > > Type name: application > > Subtype name: lgr+xml > > Required parameters: None. > > Optional parameters: charset (as for application/xml per [RFC7303]) > > Security considerations: As for application/xml per [RFC7303] I suggesting moving section 12 of the draft here. > > Interoperability considerations: As for application/xml per [RFC7303] > > Published specification: This document. > > Applications which use this media type: Software using label > generation rulesets, including registry applications and client > validators. Can you be more specific, as the registry information will be stored and viewed out of the context of the LAGER WG. Maybe "Software using IDNA label generation rulesets"? That's just a guess on my part, as I'm not very familiar with nomenclature in that space. > Additional information: None. > > Magic number: None. > > File extension: .lgr or .xml .xml is associated with application/xml so I'd just stick with .lgr. Looks good otherwise. From nobody Fri Mar 4 12:07:05 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6361A8927 for ; Fri, 4 Mar 2016 12:07:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.221 X-Spam-Level: * X-Spam-Status: No, score=1.221 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_44=0.6] autolearn=no 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 psnZ5nEsDCvp for ; Fri, 4 Mar 2016 12:07:02 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3B41A8935 for ; Fri, 4 Mar 2016 12:07:00 -0800 (PST) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id u24K6dXc017000 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 4 Mar 2016 20:06:59 GMT Received: by mail-ig0-x232.google.com with SMTP id ir4so8570239igb.1 for ; Fri, 04 Mar 2016 12:06:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coactus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=hD8cVuUUSfvN7DfJK0+EM96sXAb/+AH3XFWcaswqg4k=; b=ZSnCOuoTPPHRph75QcvAKtCZP81JCzWiqbYDzbuN6VRCPdAA4XWjftr5zHqcfba6X7 dePU695pHBGysoIApty5cSuRUGx1MpeTPjJu6RtjrTTuzsfVS6lapd/ruJfI478VlKJb 3iRfx5dZLWWIyaCdOX7tzqetmZeoonQxQ/AvagPZOZVupD98ng3yo8TNAUgRflw6c8H7 wec2S8kSRDeAacJzMggbeq99ZPfPNedMMdwqyzHolO5oTfT5ReDSmUczEfPGy0u9MXEJ AoDK2TQmeTGUk8Bgj7n+7LG4BcNLTCgXufqotHBGA7SNtF4f8diAxWR5f+oDVYjbSOhQ wwBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=hD8cVuUUSfvN7DfJK0+EM96sXAb/+AH3XFWcaswqg4k=; b=hxuF85qsRMNrZkl/UUml3UxeHm8KinPbAneyW3e3LXxvFcgMCeftglkppDGADC02xE 0kWwRAdCpTd4vyst+9YMqS1sAt6/VGkGzVKFSXf5/fdREcMQ975S0aaeAXhOBcggJ5YI +ZP/TrL99aOu/k+BGIJUHVVmofvyTYJapBYQdUlzZOFKhdLWTNpExQwSMgwTdqNhUWea Pohfdkvd5I5u8fDCPkf2Ojitlfa3frouM18XLz4IgqimbX0/jtjYsYd8waUHD7XBQrh1 dWeXfsH3g3MQdXLvZGz+QLr0h7U7cDX7ylGu8Tp5nsIvfUWIPa8tDetvwsmvb2qF5td9 MWFQ== X-Gm-Message-State: AD7BkJIdkn9yX9LS8LfBfw9sFghxzJBdOaOZ8yXPbHeikJ9FvdIbJ3TaWwlHiWFekyPG08RlESD1a/gJ/8AhFA== MIME-Version: 1.0 X-Received: by 10.50.50.201 with SMTP id e9mr840684igo.10.1457121999206; Fri, 04 Mar 2016 12:06:39 -0800 (PST) Sender: mark@coactus.com Received: by 10.64.167.171 with HTTP; Fri, 4 Mar 2016 12:06:39 -0800 (PST) X-Originating-IP: [24.246.8.190] In-Reply-To: <56D9E56E.1090301@ix.netcom.com> References: <56D9E56E.1090301@ix.netcom.com> Date: Fri, 4 Mar 2016 15:06:39 -0500 X-Google-Sender-Auth: B1Im1EHoQc990xN8x3Kn2qNfatI Message-ID: From: Mark Baker To: Asmus Freytag Content-Type: text/plain; charset=UTF-8 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [IPv6:2620:0:2d0:201::1:74]); Fri, 04 Mar 2016 20:06:59 +0000 (UTC) Archived-At: Cc: Marc Blanchet , draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG Subject: Re: [media-types] media-type registration request review X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2016 20:07:03 -0000 On Fri, Mar 4, 2016 at 2:43 PM, Asmus Freytag wrote: > The label generation rulesets specification is not limited to IDNA. > > Software using label generation rulesets for internationalized identifiers, > such IDNs, including... Fair enough, but there's still a fairly specific scope there that isn't reflected in the description. >> .xml is associated with application/xml so I'd just stick with .lgr. > > > Apparently there are some other media types that use .xml., so what are the > conventions? Hopefully not in the IANA registry, as that would make a file extension to media type mapping ambiguous. I wouldn't be surprised if some snuck through, but I hope to save you from the pain that would ensue if these files were ever needed to be served from a file system through a Web server. In practice, curators of mime.type files like Apache's (hand curated by Roy Fielding) would ensure that any ambiguity was removed, and you can see in this case that 'xml' is associated only with 'application/xml'; https://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types nginx unfortunately defaults to text/xml but at least it's a unique mapping; https://github.com/nginx/nginx/blob/master/conf/mime.types From nobody Sat Mar 5 18:10:06 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556201A88C5 for ; Fri, 4 Mar 2016 11:44:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=unavailable 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 puuEZ0ONnNxO for ; Fri, 4 Mar 2016 11:44:27 -0800 (PST) Received: from pechora3.lax.icann.org (pechora3.icann.org [IPv6:2620:0:2d0:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6690C1A88BD for ; Fri, 4 Mar 2016 11:44:27 -0800 (PST) Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id u24Ji6PH022157 for ; Fri, 4 Mar 2016 19:44:27 GMT DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=UseGiLDa3OkNN+ShtNL9w6lrGpYEK7yhEA1VGF1KoqCaDNY3UOaO8NCVlve6ab41; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [71.35.115.182] (helo=[192.168.1.104]) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1abvdJ-0003wI-TK; Fri, 04 Mar 2016 14:43:29 -0500 To: Mark Baker , Marc Blanchet References: From: Asmus Freytag Message-ID: <56D9E56E.1090301@ix.netcom.com> Date: Fri, 4 Mar 2016 11:43:42 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: 464f085de979d7246f36dc87813833b2857e9f10d2205ddc6075354744af6abe3217137c15219439350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 71.35.115.182 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Fri, 04 Mar 2016 19:44:27 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Sat, 05 Mar 2016 18:10:05 -0800 Cc: draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG Subject: Re: [media-types] media-type registration request review X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2016 19:44:28 -0000 On 3/4/2016 11:23 AM, Mark Baker wrote: > Hi, > > On Tue, Mar 1, 2016 at 1:39 PM, Marc Blanchet wrote: >> Hello, >> draft-ietf-lager-specification requests the registration of a new >> media-type. The document has passed WGLC and we would like to have a review >> of the request. Herein the extract of the media-type form from the draft. >> Thanks in advance for the review >> >> Marc, lager wg co-chair >> >> >> 11.1. Media Type Registration >> >> The media type "application/lgr+xml" should be registered to denote >> transmission of label generation rulesets that are compliant with >> this specification, in accordance with [RFC6838]. >> >> Type name: application >> >> Subtype name: lgr+xml >> >> Required parameters: None. >> >> Optional parameters: charset (as for application/xml per [RFC7303]) >> >> Security considerations: As for application/xml per [RFC7303] > I suggesting moving section 12 of the draft here. > >> Interoperability considerations: As for application/xml per [RFC7303] >> >> Published specification: This document. >> >> Applications which use this media type: Software using label >> generation rulesets, including registry applications and client >> validators. > Can you be more specific, as the registry information will be stored > and viewed out of the context of the LAGER WG. Maybe "Software using > IDNA label generation rulesets"? That's just a guess on my part, as > I'm not very familiar with nomenclature in that space. The label generation rulesets specification is not limited to IDNA. Software using label generation rulesets for internationalized identifiers, such IDNs, including... > >> Additional information: None. >> >> Magic number: None. >> >> File extension: .lgr or .xml > .xml is associated with application/xml so I'd just stick with .lgr. Apparently there are some other media types that use .xml., so what are the conventions? A./ > > Looks good otherwise. > From nobody Mon Mar 7 02:44:07 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149771B3E78 for ; Mon, 7 Mar 2016 02:44:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.875 X-Spam-Level: * X-Spam-Status: No, score=1.875 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, MIME_8BIT_HEADER=0.3, SPF_SOFTFAIL=0.665, T_DKIM_INVALID=0.01] autolearn=no 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 XbMRS9KwYooL for ; Mon, 7 Mar 2016 02:44:05 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1B631B3E77 for ; Mon, 7 Mar 2016 02:44:04 -0800 (PST) Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0130.outbound.protection.outlook.com [104.47.126.130]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id u27Ahg5O011797 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 7 Mar 2016 10:44:04 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=/nkYa2bmI28qT+duxWRhLP9lPb9BH9fE3ebhiHMtez8=; b=k6RR0dRBD7ive7+2l9Zxf5tjWVXTnGC+P7KNGdZXxkh/QYDKD8cYQde6oshCAgp0234uK5xoaJWZQRCz11yTNSbBxhDGA2Z814lYk1o7UMkRZrJd2Myh0SgwKaAUH2ZfwkkFMKXpDZwSX/nnHjN/zPYatOlC2scL9X/2rKDhx8o= Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=it.aoyama.ac.jp; Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0142.jpnprd01.prod.outlook.com (10.161.134.14) with Microsoft SMTP Server (TLS) id 15.1.415.20; Mon, 7 Mar 2016 05:07:10 +0000 To: Mark Baker , Marc Blanchet References: From: "=?UTF-8?Q?Martin_J._D=c3=bcrst?=" Organization: Aoyama Gakuin University Message-ID: <56DD0C7C.20102@it.aoyama.ac.jp> Date: Mon, 7 Mar 2016 14:07:08 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [133.2.210.64] X-ClientProxiedBy: KAWPR01CA0015.jpnprd01.prod.outlook.com (25.161.24.25) To TY1PR01MB0142.jpnprd01.prod.outlook.com (25.161.134.14) X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 2:4itS8CMI6E0bZQfuTydiJBvsGS7vXnFtYfQbn+UBGpteUKGXmmNRXb5/IiK3fKXTSg2N/iev9qd+PwXGfP01so8Ry75fwt/eBFoAT5ysxKwyaCNIKXLyBnidtVkn96JgULaxJBXEx83es8egLD4C5w==; 3:acfst1pmYS0iH+nhpKHjxiCM2grXCKHHHwBzyD7w/ys4e7rSPZQUsgM8lZv6Xg/2zQ/jq9uJ+ULRzy4UJfAOuZzxGnFTpqm0qsDdvgdZVM5v5hJOI8aGG/ba0ZL7ktqa; 25:qGZWjRNVv2kGETx0rfRh1ShFoeeFhliqNkJDu64rORHlt9NRGbhEijPuO0Alc56d2O2/irEvaeh9lva8i0GHpeKtEwabHk3pMmHxVMqdwRRKsLxz6zO0uvHVd9HkxV5uXxU8I47U5zlhl3Pvg7OACNigdDYaf/qLBqb9d8M4AQps6tK4srz1zOPmdjv2VI19X1nUQXhhA77aCroQBoyfk7U+Mb3xZnaBlw4eRd2TZA1rAubX7Y/nGSdnWsdtGHu2EkxRFWSP7R6HZBDX979soFRb+7xqYlnBdVoZes2dbIwdw7Xwa7meoCM2GqBs4HxdyfpzkoshpwW4hxv1xEdprQ== X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0142; X-MS-Office365-Filtering-Correlation-Id: 4fd214d6-041a-48c3-6006-08d346465697 X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:TY1PR01MB0142; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0142; X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 4:Nn6SAA2XNiXnFz7SUv9eD6fJ606w84Vb06OpD1eDWazyn5gNTS1RZ08SfOhlfebOhqz5SIj7obwh4Rdxx+uJ5XuxbiUeHyXniopECglcsW8UWVO6PhpBzt/ShSXbJHCNst4B6WzBTDNknc6QTwEV36300bWd1KfyhZyh22wzvxavwH90rV5fAS0RUOOb2ItrvTGHV71XsMXh8m8HXpTwrvrB0JULnIy3k+pMUu9yES7sT/iuHcoR99j8ROUc7rSGUBBdkgKmFf9orEqkPX+zcnVgK4bXcgAP42TBOul4Hl0OA2H0ZvIbL+vg+8xr+xECzJD4T5/wvFFH5xKdcITF1iaXCzNqLdipq+aO3QEifz0= X-Forefront-PRVS: 087474FBFA X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(6049001)(479174004)(377454003)(24454002)(51874003)(230700001)(23676002)(15975445007)(77096005)(42186005)(50466002)(5008740100001)(74482002)(19580395003)(19580405001)(5001770100001)(83506001)(122386002)(86362001)(81166005)(4001350100001)(54356999)(50986999)(76176999)(65816999)(33656002)(87976001)(92566002)(4326007)(47776003)(65806001)(2950100001)(40100003)(65956001)(189998001)(66066001)(6116002)(3846002)(586003)(1096002)(64126003)(2906002)(5004730100002)(3940600001); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0142; H:[133.2.210.64]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwMTQyOzIzOjZyR3FoMkZuVzFmY1hTcnFTelRPbjJISWhR?= =?utf-8?B?MHBlT1AwRTRXRTFBOUdTZ1o2emowdkNNcGZYWnkwekswc0FXRGVHRklwUG1i?= =?utf-8?B?Nlh5cVNKN1V4ZU1hdTd0ZldvZTFIMnh1T0V3Qm81aWF0bml3VHFwaWFBeGJD?= =?utf-8?B?VjVqWHFCeEdmTHFNbGJKaGR6eGNCZ2VBUG10ZW4zT1lPMDNMTDZtellNUTA3?= =?utf-8?B?YlErRk1Hd1ZlMHVtWTQ5QlhXQVlxM1poNlpFM2M5clpweDBmL2Jpc1N5bk4y?= =?utf-8?B?MXdFRVA3ZjJacTYwUXVzY1hRaXhCUmdBOVh1d05lc1dQK0h1bzFCcXIyZW5P?= =?utf-8?B?SXJrZE04amJKajlEYWtrV2dxdkowaWdFU2xDZ3I1eC9oUHJmSjRVdzB6dmRM?= =?utf-8?B?OTRlM2RlMXZhbThWbWpsaTFwZUdtTmlBV0VrdG9nUnRTQ202eFVsSjNib3hC?= =?utf-8?B?VTUwUzJlNFVGR0lMU0ZRcy90L1NxSmtWS3NVMGpLR2dEZXl6TmpMMEJFcnlk?= =?utf-8?B?SU0yYnJyWXlnZFQrOXVKclZ0S29sWHk2L2xqVzNERGM3SHZGZmdXaXdxa0tS?= =?utf-8?B?VlBGU3FEYnJuT21HallYUzdJcHc2WjNCbVdZWHV0VmEweUFwNHFWdmNZL2sw?= =?utf-8?B?d1Z4anNod1h4dUw0N21mdUswZURwZ3hpRnZtaTVkSktROWdKODdKMHlxOFht?= =?utf-8?B?OWJyaVd1eGk4MjhVMXQrNVNrYzY1aURxNlVUTFVnK05qbktZdXQxV0FXaE95?= =?utf-8?B?M3NHRklGdDlFOTJJMkI3YytidHNvOHNSeXNCT3p2cnZBQVI5MW5JVVoySWE3?= =?utf-8?B?TzVRZWRBdHZHalBpTkpxTGxSdDRIbjF4RXNnWkpIc0Y3Z3pZZVdzTFVwMEJR?= =?utf-8?B?T1RTK2hvVkk1dlV1dkVKQmNqODEybnJDTDUzdStFaG90aVlFZ0hhdkRYNzZI?= =?utf-8?B?VUN6ajRnV2F1d0tKMW9CNnFNTmNOcXVCVlhZNDFVOWpHd3htTFhudnZKN0RS?= =?utf-8?B?SkFodGcyUDJpb2lWV0cyUnhteTdOcExidUgzVnZoTFgyaUVDWjVxOFVZWVh3?= =?utf-8?B?VkUrVTJSUVZWY3Z4UkMrQlc4d1dEM2FrSUF5enk0YVN3ZjRFa0ZOVERhODZo?= =?utf-8?B?Z28rVFhjamtYbmMvR3c2eW92ZUJZUEdjNEJBem55K2lwVGFDcXo1MTdWY3do?= =?utf-8?B?Uk1HeWV2bzJOODRtVk9ScnpEOEQzdE9DazI0ZXBMcE90M0hXcVQ5NlFJY0pr?= =?utf-8?B?WDZlbTBZay9udDhWdisvNVRreHFoTjBlUDBOdloreVRUR3EvVWZHNklkcUtS?= =?utf-8?B?WDVDQ2Frb2FGL1lYckkvYmJoZ2FhSXI2WXp5YmM3cGlWaEtMd2lVREExZWRv?= =?utf-8?B?ZTBHZmhiRW5kUk0rbksrUy8wcnBuclFzeFdiaVIzVWJPaGdVL3VpbGZRSEcz?= =?utf-8?B?VThhbTV2QlI5SmdzOEc3V2hzRmFEbURGRlZ1R01YTlNLOEdoZnJ1ZTBvYUZy?= =?utf-8?B?S3MxdHV4aEk0SFQxR21VV3Jvc1NKTGNDOFNqYWZxV1RVbU9odG14Rm83WHhZ?= =?utf-8?B?NE9yTEFneUc3YklDd0p2bnNsd1ZXVjlWK0JENDRuVGxwK1AvOTdBUW8zaytr?= =?utf-8?Q?7PDO+CFNVuRihWY+lvwu?= X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0142; 5:bwv4Po4lP+J8ZOpHJLTxmCPVqD1z9VfBQssEXgK+DYuer/+pBRAwRc8NkXNlauFK/3V72ZYm4hRK0x7fUsgK64Sgn5uHQxq525wZVQUrVt9VvuxqLPnnV3XdbDtmktlmsPaa/peWekZKOanRvYtaZw==; 24:nMRI+vJY91p0zbZCtPn+N0C4ffjE2ckCFqvxFqaCKkNMmvidP8UxfeuAKiv4w5volaH6JDJ1gH+trgcmzVuAXKB4nFbOw23aRTOa4rLZ46A= SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: it.aoyama.ac.jp X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Mar 2016 05:07:10.1600 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0142 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Mon, 07 Mar 2016 10:44:04 +0000 (UTC) Archived-At: Cc: draft-ietf-lager-specification@ietf.org, media-types@iana.org, lager WG Subject: Re: [media-types] media-type registration request review X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 10:44:07 -0000 On 2016/03/05 04:23, Mark Baker wrote: > Hi, > > On Tue, Mar 1, 2016 at 1:39 PM, Marc Blanchet wrote: >> Hello, >> draft-ietf-lager-specification requests the registration of a new >> media-type. The document has passed WGLC and we would like to have a review >> of the request. Herein the extract of the media-type form from the draft. >> Thanks in advance for the review >> >> Marc, lager wg co-chair >> >> >> 11.1. Media Type Registration >> >> The media type "application/lgr+xml" should be registered to denote >> transmission of label generation rulesets that are compliant with >> this specification, in accordance with [RFC6838]. >> >> Type name: application >> >> Subtype name: lgr+xml >> >> Required parameters: None. >> >> Optional parameters: charset (as for application/xml per [RFC7303]) >> >> Security considerations: As for application/xml per [RFC7303] > > I suggesting moving section 12 of the draft here. I don't think that's necessary, and it would remove the "Security Considerations" section that's needed in every RFC. I'd suggest to replace "As for application/xml per [RFC7303]" with something such as "See the security considerations for application/xml in [RFC7303] and the specific security considerations for Label Generation Rulesets in XML in RFC XXXX (RFC Editor/IANA, please replace XXXX with the final number of this document)". >> Interoperability considerations: As for application/xml per [RFC7303] >> >> Published specification: This document. The template will be stored independently of the containing RFC, so instead of "This document", use something like "RFC XXXX (RFC Editor/IANA, please replace XXXX with the final number of this document) Regards, Martin. >> Applications which use this media type: Software using label >> generation rulesets, including registry applications and client >> validators. > > Can you be more specific, as the registry information will be stored > and viewed out of the context of the LAGER WG. Maybe "Software using > IDNA label generation rulesets"? That's just a guess on my part, as > I'm not very familiar with nomenclature in that space. > >> Additional information: None. >> >> Magic number: None. >> >> File extension: .lgr or .xml > > .xml is associated with application/xml so I'd just stick with .lgr. > > Looks good otherwise. > > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types > . > From nobody Mon Mar 7 17:40:50 2016 Return-Path: X-Original-To: media-types@ietfc.amsl.com Delivered-To: media-types@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9249E1CD808 for ; Mon, 7 Mar 2016 17:40:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.41]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IjW8sEE0mli for ; Mon, 7 Mar 2016 17:40:47 -0800 (PST) Received: from pechora3.lax.icann.org (pechora3.icann.org [IPv6:2620:0:2d0:201::1:73]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfc.amsl.com (Postfix) with ESMTPS id 8EE7E1CD807 for ; Mon, 7 Mar 2016 17:40:47 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) by pechora3.lax.icann.org (8.13.8/8.13.8) with ESMTP id u281eQd2001543 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Tue, 8 Mar 2016 01:40:47 GMT Received: from mail.hotmail.com ([157.56.172.59]) by mrelay.perfora.net (mreueus003) with ESMTPSA (Nemesis) id 0MeRTt-1aDbhX2xhP-00QD2B for ; Tue, 08 Mar 2016 02:40:24 +0100 Received: from SNT405-EAS138 ([157.56.172.55]) by SNT004-WSS1S4.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 7 Mar 2016 17:40:23 -0800 X-TMN: [t7jPcx6JiRzJFftYEU5ESuKrAPJXdhMn] Message-ID: From: Darrel Miller To: Date: Mon, 7 Mar 2016 17:40:18 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdF421QrDE24cvsoRBGDUNbkypm7Gg== Content-Language: en-us X-OriginalArrivalTime: 08 Mar 2016 01:40:23.0171 (UTC) FILETIME=[7B447530:01D178DB] X-Provags-ID: V03:K0:IgA4Bl+bxDGN0tKfDNIAg8AsBpj5SJLvqo8j226hcMUB7LAsMZW ga9yaWAvX+lia7Y82l4gQUJ6NIRaiayEjI2odJIZwYN4kk7mcRFikgmnsoGcywVY/1t9ZRE DC/HLOiJtLEFEUQZIrt7iXjLM19rKSIXM3Dc+Z+opv95GeoqWUhimLkL7a4/DhYHe/6MLmO 0MG2l3svbb0FhRmU743xg== X-UI-Out-Filterresults: notjunk:1;V01:K0:pEE4aP/kNwU=:ICIxBgZPjKimsC722Rkr3m Td54Fu2hH74TDI/Hz4N1elF6jtVTFc2CASp/FaqHUnl9RM59t5QNSTFgWDFJR5oTNNtTw7kWp gDaf4IRgjwh4iieTEkRfDGcvGKgfRrCGJi9e+vI/SqwlTOAd5nviub8W/3foiCGFxhWcEpb7u 6AWUk5GOizvJEs8X6olK3wQ+oroQXbFWQep6DQ/gfmLcmWBbTlgaFvdjvYLUn9MzmysKAzIEZ G+ZYUd7pdgWg139lI1QMwMlbYoMbNoHYsh7NkIUCxCfhlcpI0gSMGRTHjUetKoUsVpLyrfk+4 r5Np6FkxUAhp08+GVOxZvDPpcZiA6PH/6Wii/2oSJl43f/S8xBpdrSobgvGVDiph+jeWH25PU xoZ80LTdGXNSXkJv2/G/WStz3RdeeAwITEfZRwVKiSXETeMxHvFYedERXlE+hoZLTufaU1xM9 +bu3IaiQjAoE1hAmB9/tCBG1CTHt7lLt0lWQxkngub+N64n2yLAkqzBy0PLLt97/ZvyStBqGo tFwJQrcKvnaPqEXHnF5/zWjOzkLeeO1fdxkIV0YC2W42jPkqEpSlpzal8P6YNlf3LP+0IIiDn Wvu5XeGOq2ueb0NpuGhbVHw5FHokXr40Y/HSwaYrDbJqiLo6tnhV+fsz5MNandBZDc2yIhP5p tAy6IVzIcXUHrJWfiNTUW3Twq4YViSpTnKVjAnAF8whCfido993nfY5RIX9ZGkuVUd8hmsviS gyoSo4i2Rl0EuDMR X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora3.lax.icann.org [192.0.33.73]); Tue, 08 Mar 2016 01:40:47 +0000 (UTC) Archived-At: Subject: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 01:40:48 -0000 As a member of the Technical Developer Community of the Open APIs Initiative ( https://openapis.org/governance ), I am exploring options for registering media types for the Open API specification (previously Swagger) https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md . Currently this document format is in its second major revision and we are working towards a third that is likely going to have breaking changes. The document itself has a version property within it so there is no need for that to appear in the media type. There are also two distinct representations of the OpenAPI document. One uses the JSON format and the other uses the YAML format. It would be desirable to distinguish between these two representations and we believe the best approach would be to follow the precedent set by RFC 6839 and use a +json and +yaml suffix. As +yaml is not defined with RFC 6839 and there is no registry defined in which to add this new suffix, I am assuming a new RFC would be needed to register this. As we see it, there are two different subtypes that are potentials homes for these registrations. There is the vendor subtree and the Standards subtree. Considering the current support and fairly broad adoption of this format and its new home in the Linux Foundation, I would think the standards tree would be the more appropriate place. However, any guidance on this would be appreciated. I would like to submit registrations for: application/openapi+json application/openapi+yaml Other than the need for +yaml RFC does anyone have any objections to these? One final question is related to the fact that these formats are a form of documentation for an API and may be read directly by humans. Is it recommended to also register text/ versions of these media types to allow servers to communicate this intent? Thanks for any info/opinions/guidance you can provide. Darrel Miller From nobody Mon Mar 7 21:27:05 2016 Return-Path: X-Original-To: media-types@ietfc.amsl.com Delivered-To: media-types@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id A0D851CDF23 for ; Mon, 7 Mar 2016 21:27:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.41]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcNIQPA-cPlo for ; Mon, 7 Mar 2016 21:27:03 -0800 (PST) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfc.amsl.com (Postfix) with ESMTPS id 33AC31CDF21 for ; Mon, 7 Mar 2016 21:27:03 -0800 (PST) Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 202AF22E253 for ; Tue, 8 Mar 2016 00:27:01 -0500 (EST) To: media-types@ietf.org References: From: Sean Leonard Message-ID: <56DE624C.6020700@seantek.com> Date: Mon, 7 Mar 2016 21:25:32 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 05:27:04 -0000 On 3/7/2016 5:40 PM, Darrel Miller wrote: > As a member of the Technical Developer Community of the Open APIs Initi= ative > ( https://openapis.org/governance ), I am exploring options for registe= ring > media types for the Open API specification (previously Swagger) > https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.m= d . > > Currently this document format is in its second major revision and we a= re > working towards a third that is likely going to have breaking changes. = The > document itself has a version property within it so there is no need fo= r > that to appear in the media type. > > There are also two distinct representations of the OpenAPI document. O= ne > uses the JSON format and the other uses the YAML format. It would be > desirable to distinguish between these two representations and we belie= ve > the best approach would be to follow the precedent set by RFC 6839 and = use a > +json and +yaml suffix. As +yaml is not defined with RFC 6839 and ther= e is > no registry defined in which to add this new suffix, I am assuming a ne= w RFC > would be needed to register this. > > As we see it, there are two different subtypes that are potentials home= s for > these registrations. There is the vendor subtree and the Standards sub= tree. > Considering the current support and fairly broad adoption of this forma= t and > its new home in the Linux Foundation, I would think the standards tree = would > be the more appropriate place. However, any guidance on this would be > appreciated. You can put it in the Standards subtree if you want. It is slightly more = work, but you can jettison the ".vnd" part. To get it in the Standards subtree, either the registration has to be=20 based on a specification by a recognized Standards Development=20 Organization (SDO), or published as an RFC at least at Informational=20 level. Only the format specification has to be by a a recognized=20 SDO--the format specification document does not have to incorporate the=20 media type registration template. So if you already have the format in a = published document, you can write the media type registration template=20 yourself. However, it sounds like you need to publish an RFC in this case=20 (assuming that you don't want ".vnd"). The RFC can go through IETF=20 Consensus (i.e., go through a working group), or can go through the=20 Independent Submission Editor as an Independent document. > > I would like to submit registrations for: > > application/openapi+json > application/openapi+yaml > =20 > Other than the need for +yaml RFC does anyone have any objections to th= ese? No objections, just further comments. > > One final question is related to the fact that these formats are a form= of > documentation for an API and may be read directly by humans. Is it > recommended to also register text/ versions of these media types to all= ow > servers to communicate this intent? Regarding +yaml, adding a new structured syntax registration requires=20 Expert Review. This means that an RFC is not required. Just fill out the = template and get it reviewed and approved. Under the circumstances, however, I would recommend that a discrete YAML = media type be defined if you want the structured syntax suffix. This is=20 mainly because it seems to make sense to have a generic way to=20 interchange YAML that is not specific to OpenAPI. I would recommend=20 text/yaml. The distinction between text/yaml and application/yaml boils=20 down to a few considerations: 1. Whether you want to preserve the bytes exactly "as-is", versus have=20 media type aware processors "massage it" on the way down (e.g.,=20 manipulate or canonicalize LF <-> CRLF). 2. Whether you want media type handlers to fall back to text/plain or=20 application/octet-stream. The former will behave like a plain text file=20 or stream (because it is). The latter will look like an opaque blob or=20 opaque file (because it is). 3. Whether the format itself declares the charset. In (for example) XML, = declares the charset, so text/xm= l;=20 charset=3DYYY can get out-of-sync. 3. Whether you want charset conversion services. text/yaml;=20 charset=3D"iso-8859-15" can get converted to (any) Unicode encoding=20 "automagically". Per RFC 6657, the registration of the text-based media=20 type is supposed to declare the default or preferred charset. So even if = you assume YAML is "always" in Unicode, that alone is not a reason to go = to application/yaml (because in text/yaml you can just declare that YAML = is always in one of the Unicode encodings). Overall my opinion is on the side of text/yaml, if you register the=20 generic type at all. You do not have to. I am not familiar with the=20 history of YAML, but I suppose there is probably some reason why it has=20 not been registered yet. Perhaps implementers found that text/plain=20 worked fine for them, or for computer-to-computer interchange it was=20 easier to exchange JSON or XML. Sean From nobody Wed Mar 9 16:29:32 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5988312DC5D for ; Wed, 9 Mar 2016 16:29:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.8 X-Spam-Level: X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no 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 cqvomfF7Uce3 for ; Wed, 9 Mar 2016 16:29:28 -0800 (PST) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D62912DC68 for ; Wed, 9 Mar 2016 16:29:28 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id u2A0T6qT007851 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 10 Mar 2016 00:29:27 GMT Received: from mail.hotmail.com ([157.56.172.56]) by mrelay.perfora.net (mreueus003) with ESMTPSA (Nemesis) id 0M5ehC-1ZtWLR22WW-00xbzf for ; Thu, 10 Mar 2016 01:29:05 +0100 Received: from SNT405-EAS234 ([157.56.172.55]) by SNT004-WSS1S1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 9 Mar 2016 16:29:04 -0800 X-TMN: [nZT27WX5EmXma0PWOVeBb09kCO1+vXfR] Message-ID: From: Darrel Miller To: References: <56DE624C.6020700@seantek.com> In-Reply-To: <56DE624C.6020700@seantek.com> Date: Wed, 9 Mar 2016 16:29:02 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQABAgMEzSZ6Rh+AKFQcQMzx/iigIwAHaGUJovJ/jPA= Content-Language: en-us X-OriginalArrivalTime: 10 Mar 2016 00:29:04.0409 (UTC) FILETIME=[D9C0B090:01D17A63] X-Provags-ID: V03:K0:7axx5E72ZlhHFelvAWUNV6X6OPuvod2cJ0rOK3ZEZogA6isol8o s23RphUzgsq+Hgw7oXcgfKucrEnLyHIBhrG8cJN4y2QG+UeI7idmLhTlOwkNlSe7Qpje1aw ke6Dr9uMlTOGDG0g9TutILEE31xyBfmYwoGmu58BZ0FuvA9t/LDASGuaN0WZhNQiesfvZ/4 nCyeD/q1xgH912LKXTcJg== X-UI-Out-Filterresults: notjunk:1;V01:K0:jTPMoNVD+Ug=:XrAdrApvUeg7wQacMhGNNF EnDXpn0pTzQ26JOwmrqnPpKnvdrPUFSBtxf7rL0tqtiwC9KiUS4CHl/5qsu8hS5+X2CO4v3ps rpg+GY1TCIkTXjKfd8o/HE3HlFTU7MWobpBvxTI9Io19XWOZUil/4Tlih666JIC9AGhGhEU/Z Dm/xmx5pTxkNWjUAenSt5cl2Mc9+DJl2nA2WD7SM+/VmmMOuTCB26An7ftz8zCwcVQgp2e+GT 9XzJgU+6rMFnHEPeLFYOD2PkdX8ovnPCv9lAn4xS/u1j5fmklqwZLC7PP9TF1o5hxuspS9kBy 1Glc0ZVt8XEafZx9movAA1X88nYoyVlIAyy5dLGTVvfJwm2mlGNOyOdMsOCLBlVABaJp0ZAx1 6bGwWLc6qvpgymOQFO3boeAgD04trCMZg/ghdEIFxUauP7aXYMTy661Ms4rbGCDgufEZNpXX0 jhDNBc47UDAkw2AW3B+xZ/93bugYmaBKWFs0UxwsA5t4SbUdFENz6SR0sQ12P9KGoVtEYeLxr XrN4O38EH0E9jWtsfCWaiirDIzAP9r9mtO8r62atJT3GEcgYdp+iR2aTgK+Kro32fsITAcUph IAVY3inOp1xAKlTtLetRW3Svj75mWLZkUqbzyWNMFCRYxp9Jxxw5yE72KERCwyqlrgnc/2DfH 4VgEQfux9+QxtmYBEqTp3NmQKZg7yK3SYUTIWNR92lO1UTnr0M29vOFeJ3l5gnhYyzhWAglFc 38DD/mXdgsckPalo X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Thu, 10 Mar 2016 00:29:28 +0000 (UTC) Archived-At: Subject: Re: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 00:29:31 -0000 Thanks for your feedback Sean. > -----Original Message----- > From: media-types [mailto:media-types-bounces@ietf.org] On Behalf Of > Sean Leonard > To get it in the Standards subtree, either the registration has to be based on > a specification by a recognized Standards Development Organization (SDO), > or published as an RFC at least at Informational level. Only the format > specification has to be by a a recognized SDO--the format specification > document does not have to incorporate the media type registration > template. So if you already have the format in a published document, you > can write the media type registration template yourself. I'm just guessing, but I don't believe there is going to be any appetite for republishing the existing specification as an IETF document. I will find out. > > However, it sounds like you need to publish an RFC in this case (assuming > that you don't want ".vnd"). The RFC can go through IETF Consensus (i.e., go > through a working group), or can go through the Independent Submission > Editor as an Independent document. > As there is an existing "working group" managed via the Linux Foundation infrastructure, an independent submission would probably be the appropriate route to take, assuming the group decide it is worth publishing an IETF version of the spec to remove the vnd. > > Regarding +yaml, adding a new structured syntax registration requires Expert > Review. This means that an RFC is not required. Just fill out the template and > get it reviewed and approved. > I'm not sure I follow. Where would I find this template to fill out that allows me to register a new suffix? I don't see any reference to this process in RFC 6839. > Under the circumstances, however, I would recommend that a discrete YAML > media type be defined if you want the structured syntax suffix. This is mainly > because it seems to make sense to have a generic way to interchange YAML > that is not specific to OpenAPI. I would recommend text/yaml. I had not considered the fact that someone had never got around to registering a YAML media type. > The > distinction between text/yaml and application/yaml boils down to a few > considerations: > snip Thanks for enumerating these. It was never really clear to me when to use one versus the other. > > Overall my opinion is on the side of text/yaml, if you register the generic type > at all. You do not have to. I am not familiar with the history of YAML, but I > suppose there is probably some reason why it has not been registered yet. > Perhaps implementers found that text/plain worked fine for them, or for > computer-to-computer interchange it was easier to exchange JSON or XML. > I think YAML sees more usage as a file format than a message format and therefore the need for a media type has been less pressing. Thanks again for your assistance. Darrel From nobody Wed Mar 9 16:45:48 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3793E12DBCC for ; Wed, 9 Mar 2016 16:45:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no 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 oGetOsBwqPCY for ; Wed, 9 Mar 2016 16:45:45 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (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 8F4F812DC03 for ; Wed, 9 Mar 2016 16:45:41 -0800 (PST) Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9D98850A84 for ; Wed, 9 Mar 2016 19:45:40 -0500 (EST) To: media-types@ietf.org References: <56DE624C.6020700@seantek.com> From: Sean Leonard Message-ID: <56E0C35B.9@seantek.com> Date: Wed, 9 Mar 2016 16:44:11 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 00:45:47 -0000 On 3/9/2016 4:29 PM, Darrel Miller wrote: > Thanks for your feedback Sean. > >> Regarding +yaml, adding a new structured syntax registration requires > Expert >> Review. This means that an RFC is not required. Just fill out the template > and >> get it reviewed and approved. >> > I'm not sure I follow. Where would I find this template to fill out that > allows me to register a new suffix? I don't see any reference to this > process in RFC 6839. RFC 6838 Section 6 https://tools.ietf.org/html/rfc6838#section-6 RFC 6839 has examples of the template actually instantiated in the text. > Thanks again for your assistance. You are welcome! Sean From nobody Wed Mar 9 17:20:25 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451AC12DA28 for ; Wed, 9 Mar 2016 17:20:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.921 X-Spam-Level: X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no 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 rdV9R9P7ZIsR for ; Wed, 9 Mar 2016 17:20:21 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3567312D8C4 for ; Wed, 9 Mar 2016 17:20:21 -0800 (PST) Received: from mail.hotmail.com ([157.56.172.60]) by mrelay.perfora.net (mreueus002) with ESMTPSA (Nemesis) id 0Lebto-1a3zA42knu-00qQwT; Thu, 10 Mar 2016 02:20:18 +0100 Received: from SNT405-EAS34 ([157.56.172.55]) by SNT004-WSS1S5.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 9 Mar 2016 17:20:16 -0800 X-TMN: [C/yVbG3WvwGCLYBle7fBW3MzzVhPTu6H] Message-ID: From: Darrel Miller To: "'Sean Leonard'" , References: <56DE624C.6020700@seantek.com> <56E0C35B.9@seantek.com> In-Reply-To: <56E0C35B.9@seantek.com> Date: Wed, 9 Mar 2016 17:20:14 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQABAgMEzSZ6Rh+AKFQcQMzx/iigIwAHaGUJAAWVq/4AhbAZQKLuOLXw Content-Language: en-us X-OriginalArrivalTime: 10 Mar 2016 01:20:16.0625 (UTC) FILETIME=[00EFA610:01D17A6B] X-Provags-ID: V03:K0:2TQ/L7vMrr5ep4jkTZ16fX7VaTq/RdxBdxA6Uucf9ZrCe/YnuDL F7mrv4SCl3etPuZHoPQfRq6kmY5bxKHueXKlWpeNHeQiLR/bRpEa63zzTvuKacqC5eRhiMP PklfkA8IxMpTyoRd4z7DepdgJQnztHRG7ywJliB9K2l9eFKDssGP/ghvRQx1lfXaV47q75t K5pt5hMA7B+4XOyva2Zfw== X-UI-Out-Filterresults: notjunk:1;V01:K0:YDfyU+DS78Q=:mF1RVGPR4w/1nm1EEP6rqE ugaMc1rzVyjdDwZSqHH49fRqJEVSheMd5IM8GIW+8wMZ7q7Bg5QnLZugE99c2Cd+7w5IznVxx m7tVP3FA61uSD8RyssChJghIfY96iP+vXfE/rDxPdQ6asHLefFj8O6oqBsv92a84jI4lgpHrh 2WgKe34JDwMuWtBod8iVEKYLa5+vpIp7SAR7/ilXsSh6jU/HNCQehTIh1G7qeA3k8IWkoarQ8 gvtDQsiC40zcLMyS2CuAGJ508hnNv/ri6j+FKXQSPyt6izLNB2qpTsQEKwNZfldO9jdK97BPu 7nqajuEpRW0d+Ia7EZbu/NMMONmD+0wXUIgUAT0WCRiU2XRETFVAyflqihismyS/pW7dGblFt 2tabBMZQLeg3azLYswpNFPPjXzFAlMCLHSJXCIsQjl7PMFoL1CcLjmuZBaAAwdTntagXj640e bzsORInJO+QHt1woqhY1riB5tK+WHcy5JQnNt9HjGN6Y6Emgvj1DsVT5bAUnIwHncdusZC9vX 3X/B7JJA8RZGqXQdZ02EvXl3RcGVIYaHS8LcXGaowK8wtkHOXY79zUVczM32qMbcEBO3i6/xF 2F2BOULNKDQ0TfBMSHus+/hC2KbPZRyMEqLWzU46vAQZZMvmiad8TaIzcZPQBmIiBB9xu9Xe1 2hSiv1LD4/z53y/FYAZzBE4OIp77Kz3ERBzETABeiusF9MUysglZdXkgKgCmzeLhLyDcEZn4O ie7u1gXRDXektWC+ Archived-At: Subject: Re: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 01:20:23 -0000 Sean, > -----Original Message----- > From: media-types [mailto:media-types-bounces@ietf.org] On Behalf Of > Sean Leonard > RFC 6838 Section 6 > https://tools.ietf.org/html/rfc6838#section-6 > > RFC 6839 has examples of the template actually instantiated in the text. > Thanks. So this is where I find myself in a catch-22 situation. In order to register the +yaml suffix, it needs to there a reference to a specification for YAML. However, there is no such specification that is managed by a SDO. I searched in the YAML Core mailing list and back in 2003 they discussed their plan to use text/yaml as the media type. There has been no further discussion of registering a media type since then on the list. So it seems that, without a spec under an SDO, it would not be possible to register text/yaml or register the suffix. It seems that the only option available would be for someone to convince the YAML team to allow a variant of their spec (it has images in it) to be created as an IETF spec. Does that reasoning appear sound? Darrel From nobody Wed Mar 9 17:30:03 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6358A12D6B0; Wed, 9 Mar 2016 17:29:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.602 X-Spam-Level: X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no 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 jGvVWRFCYER5; Wed, 9 Mar 2016 17:29:57 -0800 (PST) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (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 481AF12D6AA; Wed, 9 Mar 2016 17:29:57 -0800 (PST) Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id E30D9509B8; Wed, 9 Mar 2016 20:29:55 -0500 (EST) To: Darrel Miller , media-types@ietf.org References: <56DE624C.6020700@seantek.com> <56E0C35B.9@seantek.com> From: Sean Leonard Message-ID: <56E0CDBA.3050301@seantek.com> Date: Wed, 9 Mar 2016 17:28:26 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Archived-At: Cc: dispatch@ietf.org, "apps-discuss@ietf.org" Subject: [media-types] text/yaml Re: OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 01:29:59 -0000 [adding apps-discuss and dispatch] On 3/9/2016 5:20 PM, Darrel Miller wrote: > Sean, > >> -----Original Message----- >> From: media-types [mailto:media-types-bounces@ietf.org] On Behalf Of >> Sean Leonard >> RFC 6838 Section 6 >> https://tools.ietf.org/html/rfc6838#section-6 >> >> RFC 6839 has examples of the template actually instantiated in the tex= t. >> > Thanks. So this is where I find myself in a catch-22 situation. In ord= er to > register the +yaml suffix, it needs to there a reference to a specifica= tion > for YAML. However, there is no such specification that is managed by a= SDO. > I searched in the YAML Core mailing list and back in 2003 they discusse= d > their plan to use text/yaml as the media type. There has been no furth= er > discussion of registering a media type since then on the list. > > So it seems that, without a spec under an SDO, it would not be possible= to > register text/yaml or register the suffix. > > It seems that the only option available would be for someone to convinc= e the > YAML team to allow a variant of their spec (it has images in it) to be > created as an IETF spec. > > Does that reasoning appear sound? Not exactly. First of all, it's the same situation as Markdown (see the text/markdown = discussion over time on the apps-discuss mailing list). The most important hurdle has been passed: some people actually *want*=20 text/yaml. The second hurdle has also (likely) been passed: people are actually=20 using text/yaml for YAML stuff. This turns out to be more useful than=20 the registration itself. Deploy first, register later. ;-) The next hurdle is overcoming developer laziness, since it requires some = modicum of effort to do the registration. Sounds like we have a willing=20 victim...er...volunteer. ;-) Getting text/yaml just requires an Informational independent-stream or=20 IETF stream RFC. First write an Internet-Draft. The Internet-Draft can=20 reference the yaml.org specification, without changing control over the=20 specification to the IETF. Then submit the draft to the dispatch mailing = list. (Maybe also a couple of other mailing lists, for places in IETF=20 that use YAML.) Depending on the outcome of the discussion, either the IETF will take it = up, or not. If they do, then the media type registration will be=20 published with IETF Consensus (see text/markdown). If not, then it can=20 still be published an the independent stream by submitting it to the=20 Independent Submissions Editor (see image/bmp, aka=20 draft-seantek-windows-image)=20 . I have not tried to register a structured syntax suffix before.=20 Superficially, the process appears to be simpler, as it only needs=20 Expert Review. For that, just follow what RFC 6838 Section 6 says. Best of luck! Sean From nobody Wed Mar 9 18:33:33 2016 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CE9212D965 for ; Wed, 9 Mar 2016 18:33:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=coactus-com.20150623.gappssmtp.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 gKwIqSHjb7Wh for ; Wed, 9 Mar 2016 18:33:30 -0800 (PST) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6CA812D6A8 for ; Wed, 9 Mar 2016 18:33:30 -0800 (PST) Received: by mail-ig0-x22c.google.com with SMTP id vs8so7162361igb.1 for ; Wed, 09 Mar 2016 18:33:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coactus-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=tCfAT3eb9KlJiSlAgU3fzkgL0CAPEIo/12P+/WY6PmE=; b=YFV2IEe6d28+D8FzFTSJvIKFMlbeG4sDjrRssAL6rxrTPSZpBdaoku5g464lGjAMOC +Lr79NFiOuC7MzpeMVQPHo5OSpSQJhnN3TDGVnHTx3PBpMSHgHcGDGRX3bhCNKNgtq0z UpUIJqkz32ti0VRZlvvIPBATKakTx6u0Pu6OKZrwkG+VUx2t4VyVNLTdBHfCU1LUtXaA pg2V/GAttpPaitkN0HaASO9Qj5h1Z/QtKgcoo0hiCGqCuUGGBraMLd65h3MHW6VJUfox rq3xsY31z0H4zTAamn8rc4mt0iX2livCx29H+yuKLbBPou3N+0xfvelJrBTYW9WvJVFo Oo+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=tCfAT3eb9KlJiSlAgU3fzkgL0CAPEIo/12P+/WY6PmE=; b=a0qQzitb5FkFWQsoSk7T39QkzFIAx1Faf0r8XqlYz6KaXF/e5vaAfCqP3dzG/xQPPd 2DrYfbe6BkDOKQGanMSEaJ6ldHjA4RiXO9DkbIx5VHxvvqKgq5qm/14rbkNjdkQxXxTM fdHmTpK1KuNXjfPASQOzIjwfXFvCb+mtPeUL8AitLPfxmfqSFuQMy5465RIAJuMpKxyH 5G1D2JTSAhvSiI8O8nGaWi0llccRv0A10v8uD0H1FklvDdOAwkjSeDqh9fxfOyfAMHQc UyYiI4L+u67San3u9tfvg1d2tm6Vv6AzaiLgiCG3jbUtUKDFlPZTFrPHaQPMeRsMyfCd qz7w== X-Gm-Message-State: AD7BkJL/fHqX6tCNZPu9KSPAMho5gi5QNorjGXJFh9ASn1Wctf/XzrzxbTBAGxFTOnlEwqO6U0F2gDOW7wFQ3Q== MIME-Version: 1.0 X-Received: by 10.50.143.4 with SMTP id sa4mr1145119igb.26.1457577209970; Wed, 09 Mar 2016 18:33:29 -0800 (PST) Sender: mark@coactus.com Received: by 10.64.167.171 with HTTP; Wed, 9 Mar 2016 18:33:29 -0800 (PST) X-Originating-IP: [24.246.8.190] In-Reply-To: References: <56DE624C.6020700@seantek.com> <56E0C35B.9@seantek.com> Date: Wed, 9 Mar 2016 21:33:29 -0500 X-Google-Sender-Auth: 9Ne56QNOZpYwWXBcQpJJFgJ95jM Message-ID: From: Mark Baker To: Darrel Miller Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: media-types@ietf.org, Sean Leonard Subject: Re: [media-types] OpenApi media type registration questions X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 02:33:32 -0000 FYI, an attempt was made to register a YAML media type last year. See; https://mailarchive.ietf.org/arch/search/?email_list=media-types&f_from=bjh21%40cam.ac.uk