Re: [IPv6] 4-in-1

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 20 June 2023 15:33 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A7AC1519AF for <ipv6@ietfa.amsl.com>; Tue, 20 Jun 2023 08:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level:
X-Spam-Status: No, score=-1.845 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 tybvSgQWNrIy for <ipv6@ietfa.amsl.com>; Tue, 20 Jun 2023 08:33:10 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 5CFC3C1519AD for <6man@ietf.org>; Tue, 20 Jun 2023 08:33:10 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id ffacd0b85a97d-3113306a595so3619265f8f.1 for <6man@ietf.org>; Tue, 20 Jun 2023 08:33:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687275188; x=1689867188; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W0j/cKCFChUJEP2rs9idTHFItDlag57T+B2xKqNUpuc=; b=ZOumPQhH4E8UUR4jNSSdUDEGjo1a4j9zVbCFZfJCC+Rbu/YFwv6gkJ+pk2t9B+85Xl hFLAu+LBYlai+hv1VkQ6hlG0hOUWXD7IhEZehgbXdVe01HGLxaWgRAz7JZTWFTxp7FmW T97D0eUQi5CkH3wCDUAqXOKbPkPc5eyRGfMJIHhyRi8+9bsMTXwXlzDekM7GedoLe3fx y9ncvhpP70OWic4koPNRJrgJHVaeIwu5GreVibVePVBx1TkSlX9nEuXQCStsOCVV6qtl D/N1/8QNPCctSZa+1EEjeLRU1bgk7k/vyuDUcuU9XUMFnDYncUn3DRGosbaOb6p+jXYi TwCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687275188; x=1689867188; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W0j/cKCFChUJEP2rs9idTHFItDlag57T+B2xKqNUpuc=; b=eAxBi2YBn74gFcqY8hhL1RNqaPUyX4AX34pRpf45d3myvT20wfqWlbucQXxnECsZW2 If+4HNj5sGbRwoPaCyQEuGlQu3H2OeVrp0m++f1QgDlYHJqJHMvORlt/6rIVZ4YWa8YQ 4vC2COQgszpEHv8nrkmEOoEANeJSQFCjuxCEHw7hsouEQEBKTnmn15I2dsA7atNvR+tR CBJd6HmZCeeqMwnx8sT31iPG2PkkEcQGR15PFfvSTed6HPmbf7Lbiah/1Krgjdw45iSU RseCJyGhL7R3gU36TZqGyWlTY6Ll/Oh43ol8WEALsXHt7dev5jnF5tiobxEx6y02SbGo mLdw==
X-Gm-Message-State: AC+VfDymMRIwZWN5TpHQaC9RgnN0FeRj6a/g/bfvYvaSC2xTFFVD2Rdz LGiOEwenO46b+s6DVZ+HGt2sjkMaj5noBigJZBc=
X-Google-Smtp-Source: ACHHUZ4wXGGUxBAl4MnPQNtmJS+zXNwFXkFsOLZDBIHj62h/u4Bkq/lggu718iQd2rDwDqaquvyBFsnqFn0dilL6Vqk=
X-Received: by 2002:adf:e4d2:0:b0:30e:4886:425a with SMTP id v18-20020adfe4d2000000b0030e4886425amr12392674wrm.40.1687275187767; Tue, 20 Jun 2023 08:33:07 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR11MB4881F102CBE59665CB11D336D858A@CO1PR11MB4881.namprd11.prod.outlook.com> <CAC8QAcfuxb4-Wsj0T1=+EWYATU=P8JJwSj+BoxeW-V6GthB3QA@mail.gmail.com> <CO1PR11MB4881CACC20CFBB2B97FBD0BDD858A@CO1PR11MB4881.namprd11.prod.outlook.com> <CAC8QAccSn750OdOa=FuJZn6EYBCuvGMMe_-vX2Ztn8Nx=mFbkw@mail.gmail.com> <D0776136-2C68-4633-A3C7-74A04CCD4625@cisco.com>
In-Reply-To: <D0776136-2C68-4633-A3C7-74A04CCD4625@cisco.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 20 Jun 2023 10:32:55 -0500
Message-ID: <CAC8QAcdvUCzR4=3VPGAHdqURteqooySeO7NfOimNsaqv1oyjAg@mail.gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Cc: "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000348b6205fe915e19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/J9sj2uAGP_BuLHvP7DeHVLlKxIg>
Subject: Re: [IPv6] 4-in-1
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2023 15:33:14 -0000

On Mon, Jun 19, 2023 at 1:22 PM Pascal Thubert (pthubert) <
pthubert@cisco.com> wrote:

> Not that I know of, but nevertheless I’m asking you to substantiate your
> own words not to attribute them to someone else.
>
>
>

Dear Pascal,

Sorry, there was a mixup in my mails, I replied to you a little while ago
on the previous thread, so that should be a happy end to this controversy.

Behcet

> Regards,
>
> Pascal
>
> Le 19 juin 2023 à 17:11, Behcet Sarikaya <sarikaya2012@gmail.com> a
> écrit :
>
> 
>
>
> On Fri, Jun 16, 2023 at 11:14 AM Pascal Thubert (pthubert) <
> pthubert@cisco.com> wrote:
>
>> Hello Behcet:
>>
>> could you please provide an example to illustrate your meaning?
>>
>>
>
> It's not only me, Brian and Lorenzo said similar things.
>
> Behcet
>
>> regards,
>>
>> Pascal
>> ------------------------------
>> *De :* ipv6 <ipv6-bounces@ietf.org> de la part de Behcet Sarikaya <
>> sarikaya2012@gmail.com>
>> *Envoyé :* vendredi 16 juin 2023 17:41
>> *À :* Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>
>> *Cc :* 6man@ietf.org <6man@ietf.org>
>> *Objet :* Re: [IPv6] 4-in-1
>>
>> Hi Pascal,
>>
>> It think the main comment on your draft was that the language, the model
>> used was based on IEEE's link model from the 1970s, etc. used was archaic.
>> I don't think that can be fixed with a minor revision.
>>
>> Behcet
>> On Fri, Jun 16, 2023 at 10:24 AM Pascal Thubert (pthubert) <pthubert=
>> 40cisco.com@dmarc.ietf.org> wrote:
>>
>> Dear all:
>>
>> I republished draft-ietf-6man-ipv6-over-wireless to address Brian's
>> suggestion (WiND->SND), and Ted's point of mDNS references. Plus a few nits.
>>
>> Left is Lorenzo's point of too much stuff for one document. It's
>> effectively a 4-in-1, a problem statement (section 3), an
>> architecture (section 4), a solution framework (section 5), and an
>> applicability statement (section 6):
>>
>>    3.  Issues with IPv6 ND-Based Access  . . . . . . . . . . . . . .   5
>>    4.  IPv6 over Non-Broadcast Networks Architecture . . . . . . . .  14
>>    5.  IPv6 over Non-Broadcast Networks Framework for Stateful address
>>    6.  SND Applicability . . . . . . . . . . . . . . . . . . . . . .  32
>>
>> So should we split? Will reviewing and pushing 4 small docs through IESG
>> help?
>>
>> all the best
>>
>> Pascal
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>