IETF Logo Mail Archive

Re: [homenet] Zaheduzzaman Sarker's No Objection on draft-ietf-homenet-naming-architecture-dhc-options-22: (with COMMENT)

Daniel Migault <mglt.ietf@gmail.com> Thu, 20 October 2022 13:48 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A68C14CE2E; Thu, 20 Oct 2022 06:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwsVcezQKHFc; Thu, 20 Oct 2022 06:48:16 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0E54C14CE37; Thu, 20 Oct 2022 06:47:41 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id d14so10882239ilf.2; Thu, 20 Oct 2022 06:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZD6cNGxy7EsAHFFflwvR1nAN6K929GMphnZJlOzf9+g=; b=dkQaDgKoPKym2PcYRwGGYtvKBq10lDtGhMWtmCbECXqp1TJ7lmkan2zXDDrnC358qP mRO46EUrFog3PsdcjV6u7vNUkI9PUHitOpRzzfj0/4xVOv90Gvt/jB+btEwsuoYGzptB hNqEC3EQv2gc73HhjkGaSFNAt5nlZ8v39gur5wl67RMQHv1wkg/vZmo4Bna6CwS5H9BU 6C6E6pjovn222dQNr/alDTnXf14X1ndUCx2GeuGLOLYbFFLIB8cPkbFfNYP0mVkpWuKG mJw5MJkH0gw4WAD4T1YeSXHWjn74YOmT4H2EtgpYqW1dTR2ReCw0XJKLNPdc+Ij7B3Tm nUfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZD6cNGxy7EsAHFFflwvR1nAN6K929GMphnZJlOzf9+g=; b=NpwAJa9tuUfqC6FvhiEcm7HOq/zNHA93d9AT1GmyWi96XlYgi6R6KeZa2+cC16H/RN TVWvAcQS7KFBfwMz7usD9ai9+Of+WKW8aV4HYQHQdaaI43ZRuyEb/7GyYFuRHvJ+CV6+ Lf32j5FPV4H684spFFLFA9o3MUzaGjk8vTn9/1XV2mZZ3V8SMNZRsDF0/tUeYYepj+lu lxHqIzqMFXNzuWVJ5g5HbHCh19Q76QrWmsGuzkvMGG7aX35bK6EIzYCTwfY8S21Dm//A M7YD/Kvb75ctftqmPhmJyVyXPgPsHzQuNGQrEM6GoSXzpfzVyVpFz2SUdK0GYijpLUTg RXqQ==
X-Gm-Message-State: ACrzQf05gFoQXzi/mz/9AL6s9pWn7Ey5Jk9uR9ZNvJyeGRgiFqaY7+l6 kxKQKnNPoq+uUv8eK2pk/1e4jxbHjyGI9UnAvps=
X-Google-Smtp-Source: AMsMyM7ZUTsFt2pga4I7B+QkqmPpCdPHb3aG0u8CKhuM0nd2Z+hJJf4P2YT+8CyOHcGJaKSJA/tdBzLQm5s1bwuc5wY=
X-Received: by 2002:a92:c514:0:b0:2f9:2b06:6283 with SMTP id r20-20020a92c514000000b002f92b066283mr9950871ilg.287.1666273661003; Thu, 20 Oct 2022 06:47:41 -0700 (PDT)
MIME-Version: 1.0
References: <166626956413.47121.1883094486087799176@ietfa.amsl.com> <CADZyTknxMPyjozSRC=tv6FQhj2KwzYgmNTM2OtDNMeCcugLTBA@mail.gmail.com>
In-Reply-To: <CADZyTknxMPyjozSRC=tv6FQhj2KwzYgmNTM2OtDNMeCcugLTBA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Thu, 20 Oct 2022 09:47:30 -0400
Message-ID: <CADZyTknR6KA8d38S3+9cGoVu5xtLHMznYFeg1kn5X_K352BRww@mail.gmail.com>
To: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-homenet-naming-architecture-dhc-options@ietf.org, homenet-chairs@ietf.org, homenet@ietf.org, stephen.farrell@cs.tcd.ie
Content-Type: multipart/alternative; boundary="000000000000a9aabf05eb77915d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/T67K-twc7LCdzC5-juLtWb-xFrI>
Subject: Re: [homenet] Zaheduzzaman Sarker's No Objection on draft-ietf-homenet-naming-architecture-dhc-options-22: (with COMMENT)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 13:48:19 -0000

-- I clicked send to early.
Hi Zahed,

Thanks for the review. Please find my response inline as well as the
updated text below:

https://github.com/ietf-homenet-wg/front-end-naming-delegation-dhc-options/commit/c29b4ca2b6e2af4de82ba20a975f3540fc93c458

I hope it addresses your concerns.

Yours,
Daniel

>
>
> On Thu, Oct 20, 2022 at 8:39 AM Zaheduzzaman Sarker via Datatracker <
> noreply@ietf.org> wrote:
>
>> Zaheduzzaman Sarker has entered the following ballot position for
>> draft-ietf-homenet-naming-architecture-dhc-options-22: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to
>> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
>> for more information about how to handle DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Thanks for working on this document. I am supporting Lars's discuss to
>> clarify
>> the implication of a non standard port usage.
>>
>> We only chose to use the standard port. The reason we mentioned this is
> that when other transport modes will be used, a standard port will be
> defined. Either in the document defining the transport or in a document
> specifying the code point for the Supported Transport.
>
>
>> I also think this paragraph
>>
>>    It is worth noticing that the Supported Transport field does not
>> enable to
>>    specify a port and the used port is defined by a standard. In the case
>> of
>>    DNS over TLS [RFC7858], the port is defined by [RFC7858] to be 853.
>> The need
>>    for such flexibility has been balanced with the difficulty of handling
>> a
>>    list of tuples ( transport, port ) as well as the possibility to use a
>>    dedicated IP address for the DM.
>>
>> should be moved to section 4.4 if this consideration is also true for
>> section
>> 4.3.
>>
>> correct. I just copied the lines.
>
>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson

v2.23.0 | Report a Bug | By Email