Return-Path: X-Original-To: mif@ietfa.amsl.com Delivered-To: mif@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EAD1B2B1A for ; Tue, 3 Nov 2015 23:58:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.388 X-Spam-Level: X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 kESFfZlusCuF for ; Tue, 3 Nov 2015 23:58:20 -0800 (PST) Received: from mail-yk0-x236.google.com (mail-yk0-x236.google.com [IPv6:2607:f8b0:4002:c07::236]) (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 237451B2B20 for ; Tue, 3 Nov 2015 23:58:20 -0800 (PST) Received: by ykek133 with SMTP id k133so59175167yke.2 for ; Tue, 03 Nov 2015 23:58:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=r6oVUxs74DIpNDdMQkg88Gn7BcKpVGEY9mtUBOj/iJ0=; b=krg52Cl4wRhP2T5f+/dLcvGBW7h21qT1g2xjFpL89ntdAB7RQp1D5NxLx8OlwJO6p3 Yo53zMFs+7cbaRIvEXUJfEH8EiaWwKzRfUG3SMl5rD8VCiOyfNRvQuOSA9Gj4TXZMZR5 XJ5FncwUIsKsaMrKljnE4gwCtPjP22dNOyPEvanZUXyCZI17qZVPu53BVtTdEMJb/IGN q9SSYfMRBgnnra/4PM/2aQC2kS1Wlsx74Po/IIuvWlBeebiDAMr8aE1yOp0p8WKCRrNb XJsXOUu7c7VG51v818sfJTUH5X9K+exJ+8Ky3U6E55zziaJz3itya5MPoQbV7R2O6gqy mfKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=r6oVUxs74DIpNDdMQkg88Gn7BcKpVGEY9mtUBOj/iJ0=; b=crJOxVp6fkchcGHi0DUATc1VnYa7wlX14K8Lw8G0RHEv0i2/9K33htHtEHdBHLFC/W dxDf8usJE1nJc3Fchhh2rS6STCMaT7GqLxSLpS63a0v8IbueX8aFdNv87HATEUols+g8 QPECzK32sQEq7//9PEoWW5XdCyx1vQHDMzD6Ie+P5SkBp1jmhMsEKBtZEYZmUhlKF+/L Ba4GOVGUIgdQFR51a3ZvqIFB23DH9I94hl/Wj7/NPbX1PRk3TWaQgXefm0DPNQ0GIjo7 EdAWEjVV0JADV4ZNABr8/MOLk5vz0aBkbQZ8ozELTTPegbK+7qBNhDYDnKTktDIPQmWw zsnA== X-Gm-Message-State: ALoCoQkoC7bYSHdWbIXds0mkMBjdZhYawkfUKBshv9x3NI9bSyJaCbaUq1tFyxBf+F4xZHQMKnHz X-Received: by 10.129.44.3 with SMTP id s3mr88612yws.141.1446623899299; Tue, 03 Nov 2015 23:58:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.87.197 with HTTP; Tue, 3 Nov 2015 23:57:59 -0800 (PST) In-Reply-To: References: <79C18793-758C-421A-A0C6-2F5625F1E17E@gmx.com> <55AD3922.8090009@gmail.com> <69E5A45D-C11A-4383-A4EE-AEF05675E718@gmx.com> <55AE2288.5070509@gmail.com> <74F2D07D-4FB2-4FB6-B482-EF202B4D533F@gmx.com> <55AF625B.5040506@gmail.com> <352EAA2D-0D69-40F6-8C6B-8980DD780AEA@gmx.com> From: Lorenzo Colitti Date: Wed, 4 Nov 2015 16:57:59 +0900 Message-ID: To: Tommy Pauly Content-Type: multipart/alternative; boundary=001a114278dea49c240523b25fbb Archived-At: Cc: Hui Deng , "mif@ietf.org" Subject: Re: [mif] WGLC for draft-ietf-mif-mpvd-id X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 07:58:21 -0000 --001a114278dea49c240523b25fbb Content-Type: text/plain; charset=UTF-8 On Wed, Nov 4, 2015 at 3:11 PM, Tommy Pauly wrote: > Concerns with the many types of ID described in draft-ietf-mif-mpvd-id > include: > - The size of the ID, although bounded in the draft to 255 bytes, may be > far too large for RAs, etc. A fixed, small number of bytes is much more > usable > - The content of the ID if it is a richer type (string, FQDN, etc) will be > opaque to client devices, and essentially useless. If there is no added > information, having more types and more lengths only adds processing > overhead. > +1. A fixed-length ID (64 or 128 bits) would be much easier to support. --001a114278dea49c240523b25fbb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, Nov 4, 2015 at 3:11 PM, Tommy Pauly <tpauly@apple.com> wr= ote:
=
Concerns with the many types of ID described in=C2=A0draft-ietf-mif-mp= vd-id include:
- The size of the ID, although bounded in the = draft to 255 bytes, may be far too large for RAs, etc. A fixed, small numbe= r of bytes is much more usable
- The content of the ID if it is a= richer type (string, FQDN, etc) will be opaque to client devices, and esse= ntially useless. If there is no added information, having more types and mo= re lengths only adds processing overhead.

=
+1. A fixed-length ID (64 or 128 bits) would be much easier to s= upport.=C2=A0
--001a114278dea49c240523b25fbb--