IETF Logo Mail Archive

Re: [Int-area] Jumbograms [was: Call for WG adoption of draft-templin-intarea-parcels-10]

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 03 July 2022 20:44 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9344C159492 for <int-area@ietfa.amsl.com>; Sun, 3 Jul 2022 13:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.981
X-Spam-Level:
X-Spam-Status: No, score=-8.981 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, NICE_REPLY_A=-1.876, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 hWpRICQqVZqH for <int-area@ietfa.amsl.com>; Sun, 3 Jul 2022 13:44:17 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 BDC75C14F740 for <int-area@ietf.org>; Sun, 3 Jul 2022 13:44:17 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id e132so7217969pgc.5 for <int-area@ietf.org>; Sun, 03 Jul 2022 13:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=ucMgyzESa6rgOPH3EYqa/pwYKt8mqB13AQpqAiaqmy0=; b=Bu0Jr4hi+MNuPK73ZHHDDhAhuqx9nQwBG91OX5HtNJtA1E+nHXzl41l3OhvXE4Tk1Q x685BlYQPkq7xSBJLqTkUtJpaiXu2yvbgwSxwABuNdfEh+n88meDrEtBO2xUeWdIxF7G xYrnSWJ0Ww9INn19sa+4ngQtxVg9sZ4czV/8VErpCW51dJe/n+ZSY+WV7XK6RsUePLlT xUAX1Cbjtk91Yz96CC9tm4QL6OReTd7K5p9m/iTF2ShKsX9k17pLnpZyGsbZhyOZJPsW h5nGQEKcu/GOGsQo5Q0ZYZfvulxtg+cPUyB550pS/D2xpF2AHMC0DGAyXMt8idw55jLS JD7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=ucMgyzESa6rgOPH3EYqa/pwYKt8mqB13AQpqAiaqmy0=; b=gm22gxy0ZcYxiK/rtD3rH0snwIw0thNz4IvlC2QU9sTFWrPSd2do8DtTEKIs2AKqs+ dmWp/MWUvavEguyo1o6t/owIOpWqu7qKnDdvhWMXCBOX4hohGSw372/ps6Cgy2m7Ucm5 9ZSF+mDNoMFvYeP5TVieNuQewwK8WBKVmLvs7yzi0TsnVfBiOQKsxW7gHbw42nN07IUS 8S2h09Y7Hwm/VM3AWc/asZE9tQ2iRt0aPut6JdQmjHbdnZbTe0Ua+RNQUsZVOPrB62h1 eJBQk7VkR0Ee3ztfpamDVyf26hjKcF7MuT8/WXonModebAb4Ky1Y6Wsq2xYa/QbV3/Ca 1eqg==
X-Gm-Message-State: AJIora/G98MkPlifnxAolnMgZ1FOdYzdL30Qffg63G/jQ1Vtuii1mNwV GAfggwmNIhMPaZmnEeSVijg=
X-Google-Smtp-Source: AGRyM1sZpOhVv7u4oNEtWH3O7aViOTzyIBOHj2/yewa3iuP9QWw/fln741YInUT2n1wRmPTyjt/USw==
X-Received: by 2002:a05:6a00:c92:b0:525:8782:71f2 with SMTP id a18-20020a056a000c9200b00525878271f2mr32276528pfv.50.1656881056764; Sun, 03 Jul 2022 13:44:16 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id z11-20020a1709027e8b00b0016b865ea2ddsm13260150pla.85.2022.07.03.13.44.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 03 Jul 2022 13:44:15 -0700 (PDT)
Message-ID: <4f39aa98-0911-4441-0181-4cc1c222727c@gmail.com>
Date: Mon, 04 Jul 2022 08:44:10 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Gyan Mishra <hayabusagsm@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Juan Carlos Zuniga (juzuniga)" <juzuniga@cisco.com>, Tommy Pauly <tpauly@apple.com>, "int-area@ietf.org" <int-area@ietf.org>
References: <SJ0PR11MB57692D589B130307F4C9C823D1B29@SJ0PR11MB5769.namprd11.prod.outlook.com> <CALx6S37r-JuUpSHwJCQK6dU_L4PY5PdQCYiM+iZH6V7uukJRfA@mail.gmail.com> <6F2C276E-5310-403E-B3CE-EE3496BC13A1@apple.com> <0BCD8D15-184B-41ED-8A37-E52A1D6851C2@gmail.com> <CABNhwV2LobWkAaP0pKGUQTdKD3n7x=3v+JOhX5=KAP-hfN_YHA@mail.gmail.com> <cea6403d-3151-652b-7e3a-a984794d9027@gmail.com> <CABNhwV38a3aWC1+qpYxe6AjpKAp9k8nuCCbbmmaBQsKArtUWBQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CABNhwV38a3aWC1+qpYxe6AjpKAp9k8nuCCbbmmaBQsKArtUWBQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/_5nRJX1kot1_HMrqMbx6sDVrXXU>
Subject: Re: [Int-area] Jumbograms [was: Call for WG adoption of draft-templin-intarea-parcels-10]
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jul 2022 20:44:21 -0000

Gyan,

https://mailarchive.ietf.org/arch/msg/int-area/gNA1peWM46q1upmSybUkcd9MUtY

There was also this report sometime last year (look for slide 8):

https://netdevconf.info/0x15/session.html?BIG-TCP

Regards
    Brian Carpenter

On 04-Jul-22 00:42, Gyan Mishra wrote:
> 
> Thanks Brian for 6MAN clarification on RFC 2365 that it has been implemented for very specialized environments.
> 
> I agree it does no harm to anyone who doesn’t use it.
> 
> What is the application where it was implemented if you have a link would be greatly appreciated.
> 
> Thanks
> 
> Gyan
> 
> On Sun, Jul 3, 2022 at 1:08 AM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     Hi Gyan,
> 
>     On 03-Jul-22 16:25, Gyan Mishra wrote:
>     ...
>      > So bottom line is RFC 2675 would never come to fruition and should really be deprecated or made obsolete.
> 
>     Why? Firstly, it has come to fruition, as an earlier message in this thread said. Secondly, it was intentionally designed for very special environments with unusual hardware, rather than for any commodity environment. Thirdly, it does no harm whatever to anyone that doesn't use it, so there is no reason whatever to deprecate it.
> 
>      > I believe this was discussed on 6MAN.
> 
>     I believe the conclusion was to leave it as is.
> 
>          Brian
> 
> -- 
> 
> <http://www.verizon.com/>
> 
> *Gyan Mishra*
> 
> /Network Solutions A//rchitect /
> 
> /Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>//
> /
> 
> /M 301 502-1347
> 
> /
> 
>

v2.23.0 | Report a Bug | By Email