IETF Logo Mail Archive

Re: [quicwg/base-drafts] Why is ipAddress variable length (#2158)

ekr <notifications@github.com> Fri, 14 December 2018 00:52 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B3E12E036 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level:
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 Ly21VoZojlfx for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:52:58 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6211286E7 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 16:52:58 -0800 (PST)
Date: Thu, 13 Dec 2018 16:52:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544748777; bh=1Rdf+a2d0wpmcf0zoLQPUWElXAMdfjscmA/l4wstttU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0xhHu5VdRfQGz5F6ehPsxOrjYn5PDZkSZoLJKcIjSuiRm1paTP6t8cGBhvYr+nliG zoL9+HKp5pf2FOiBtS2YOC45fTe9dqBBQTcN+POSJhi7AANB7+AzunghFBUe32j6VZ tCXHUpCV9TMi8jaq2hYmFdY9XjvZ9kUque2WinZw=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4aba0a9b0d930a075abad63a19e0e70fff4c4fb950092cf00000001182ac0e992a169ce174c0707@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2158/447175001@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2158@github.com>
References: <quicwg/base-drafts/issues/2158@github.com>
Subject: Re: [quicwg/base-drafts] Why is ipAddress variable length (#2158)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12fee9297e6_36cb3faa648d45c063847"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/vTkB39j8uabAOG8t3fLPHSaNGkY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2018 00:53:00 -0000

On Thu, Dec 13, 2018 at 4:50 PM Kazuho Oku <notifications@github.com> wrote:

> Doesn't that have the same encoding as the following? Assuming that they
> are identical, I do not mind either ways.
>
> struct Address {
>     enum { ... } ipVersion;
>     opaque ipAddress<0..2^8-1>;
>     uint16 port;
> }
>
>
Unfortunately, it does not, because the version I proposed would include
the size of the port in the length.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2158#issuecomment-447175001

v2.23.0 | Report a Bug | By Email