Re: [sidr] Endianness of RTR

Alberto Leiva <ydahhrk@gmail.com> Fri, 10 August 2018 18:49 UTC

Return-Path: <ydahhrk@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D87631310AF for <sidr@ietfa.amsl.com>; Fri, 10 Aug 2018 11:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJhLp2mCMs3e for <sidr@ietfa.amsl.com>; Fri, 10 Aug 2018 11:49:57 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 DA12013106E for <sidr@ietf.org>; Fri, 10 Aug 2018 11:49:56 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id v14-v6so9118778wro.5 for <sidr@ietf.org>; Fri, 10 Aug 2018 11:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Fy7o9nznSkcVeKwuKitVVUYojXgc24XxL32rwThRiMI=; b=Y/g6aGB4QzD3zih4kb2KhcEVwOPt/RyAElPgUtYSmCil8Uvex+ecsx3gZCwTxXeN6a tRO6nkUv6AhzDptPHxkvGMvvVhjpEPhP80Q+GaX65hqu5lo0Ik2mIT1rk2CSEbc7Ct3C QFSC9UQz9DR2YM5xgSso3PwTffO+sSTmafELanreFuERKDG4qPjL3l73mLOO3TrpdoVt jNCa+ZQF9V/i/cozitPgJZA3C0mNHCx1erO0uAMXGlfOk+ekVL8cniJ0vaTzW520QYyX KLpA//XSQvrVn4HRNMlGBTo0pvcYUiM05jEhKodbQCyawzrINHt4ZqK+e1pt8+o8iAct QH4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Fy7o9nznSkcVeKwuKitVVUYojXgc24XxL32rwThRiMI=; b=JX2snWOxO7WBRub7qt7gLDvadMrBPauJxsIHIH51IOU0MkMhbG71lszPYlwmWkPHwI xbI3OfaZxwPPG35xR07Wtjo5G4Fu+jt83VjSXHpaDKCvKjG0duTPUhMHez0WexyJzl5X kMmJIyrMIyEcmaaR3Bz29BBQ73g0nIN59KYVhQ9lu2YfnD03rA/UGOfA5rLNHOJjEpac id6xCRlpW7L5ERKGpnt1Q1nK17bOylulAdWt2Lfm6ec10Jn9z3yInZV9TdqrtDPOSZJw PVewfQ6gNuBhVKRUKLU+MGBGfveTX8HRp1tJJkmdni9yrzBTOO2BWF8PoiXwVUGqjFd3 1C0g==
X-Gm-Message-State: AOUpUlHrLGDjv9EWspN++0PxSMqNjinHQ1jizRueCOg3iAyLzgWKiA6j K5bWr0WPPVntUxbnaPfVtFIJ5q03XEXH+OM6UFYYKo+J
X-Google-Smtp-Source: AA+uWPzUHUgl8H3gWdK5Q7ZNxQH4nk++m13R2YWL1nC20TR3GR/SEiRwDfmJEh2pPk8q/8r5vRr5r67wK6A82lQrtPQ=
X-Received: by 2002:adf:b642:: with SMTP id i2-v6mr4724851wre.54.1533926995444; Fri, 10 Aug 2018 11:49:55 -0700 (PDT)
MIME-Version: 1.0
References: <CAA0dE=W3K3-fAP6dNEyRBbkWVKiJK=BK43Q4iUwVh_Z7r_YxPw@mail.gmail.com> <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com>
In-Reply-To: <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com>
From: Alberto Leiva <ydahhrk@gmail.com>
Date: Fri, 10 Aug 2018 13:49:44 -0500
Message-ID: <CAA0dE=Wuh_RC2FCfxsZdVCwy-XRQFs9ZWS6ceXB+en-JbB-gPg@mail.gmail.com>
To: jheitz@cisco.com
Cc: sidr@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/KZP8E3LW2q_SM6koRntvEwiAG4E>
Subject: Re: [sidr] Endianness of RTR
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2018 18:50:00 -0000

Thank you!

"Expires August 1999"
Oops.

Though the problem might be a tad more broad than just byte order. I
actually came up with another question since yesterday:
What is the unit of the "Length of Error Text" field from the Error
Report PDU? 8-bit bytes or code points? or perhaps graphemes?
On Fri, Aug 10, 2018 at 1:12 PM Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
>
> It's actually a good question, because it highlights that we don't even think about this anymore.
> Perhaps https://tools.ietf.org/html/draft-newman-network-byte-order-01
> should be advanced to RFC.
> A: Big Endian.
>
> Regards,
> Jakob.
>
>
> -----Original Message-----
> From: sidr <sidr-bounces@ietf.org> On Behalf Of Alberto Leiva
> Sent: Thursday, August 9, 2018 2:40 PM
> To: sidr@ietf.org
> Subject: [sidr] Endianness of RTR
>
> Hi
>
> Please forgive me if this is a stupid question, but
>
> What is the endianness of the RTR protocol? (RFCs 6810 and 8210)
> And why does it seem like it's not specified in the RFCs?
>
> Thanks
> Alberto
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr