IETF Logo Mail Archive

[sidr] Endianness of RTR

Alberto Leiva <ydahhrk@gmail.com> Thu, 09 August 2018 21:40 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 6742C130EF0 for <sidr@ietfa.amsl.com>; Thu, 9 Aug 2018 14:40:37 -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 snBgt9ZKIFnv for <sidr@ietfa.amsl.com>; Thu, 9 Aug 2018 14:40:36 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 9E72E130EF3 for <sidr@ietf.org>; Thu, 9 Aug 2018 14:40:35 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id y2-v6so44589wma.1 for <sidr@ietf.org>; Thu, 09 Aug 2018 14:40:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=WTnIn2MToozrEJ5A7HdvNEwkVkJ3Hw600qtapQFg8kI=; b=NtVvOCSdr143z+MYKJc7bHylPDyosN8Kp6SXD+eeGFQ3IsEJtbPGeAJTuPi/eFdxuW XJRi2yDeYFJb+PtKAGkZRO4X6XMcqG+kjM1y7cdWZOSw0rGYDcME00vozzimn/CqAbDc eT4r7298z/HAgpcL5Qk3QfjHixdXz/PAwr1N1MI6VVTKEd3Dnhn0X9lvOmaSWI/b7E71 Os4j3O9h9jeY5kdA3/c4/lh12eD2zrPA271M094M9bqsaKzrjbJsXPrFpR1yI9dblkTF B5sx6pequgS2RW1hZ7E72cijJCmBcG/xI9CZDxt8UXrxgTT3onh4OYV6DNfeoevbxthK JjcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WTnIn2MToozrEJ5A7HdvNEwkVkJ3Hw600qtapQFg8kI=; b=X4KaGwcQqpABDn7JIt/C4FkPSeMGXfChPr79Pujof8JzdU9Z2U5yvTyO1rSO0Ihf9C m7jvgC+KIWfEpRhJWnWHz4pa/wMa0Kfo3BUfwF85udgIQZhcAhN2wcYf2IzPsk6M/YBg riYkduCAZeY2uKMCNDERGbBQeNDJVaZ2kjLPABaZo9Tj+jYeWdAVX2ADDNirL+ymKX1s 6F2ZVS5/RVgAZTa/jf9joerXrbJ4DE1umyxBO4C9xI4fXGMilOfHOEyAJLia3SQK7wud AQtDPou7PiNJFIzF6PsumBx6ejzM8psKGqqIL0AASMfdpADFDpRialkBREudH6LBRrWa 51uA==
X-Gm-Message-State: AOUpUlEv5jIlcsLqu5OeOiHNez3IHWKLtH1QS75hb5xaOD3Guwv4TOZa +1WddWpMyV8Thxlbkbg8K0ePiT56joT8upGhjAvqO0px
X-Google-Smtp-Source: AA+uWPwHtO2lwaY/YG6XKilVujtJ9QGK43yHGkx6L/1LJIgyQlHAZHYWs6EW8ECWhP3K6cK9pwiqlE5SnCStcva0y84=
X-Received: by 2002:a1c:70b:: with SMTP id 11-v6mr10546wmh.151.1533850834066; Thu, 09 Aug 2018 14:40:34 -0700 (PDT)
MIME-Version: 1.0
From: Alberto Leiva <ydahhrk@gmail.com>
Date: Thu, 09 Aug 2018 16:40:23 -0500
Message-ID: <CAA0dE=W3K3-fAP6dNEyRBbkWVKiJK=BK43Q4iUwVh_Z7r_YxPw@mail.gmail.com>
To: sidr@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/0bMcSS6vDfb5PzCc8jF4_kgFxA8>
Subject: [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: Thu, 09 Aug 2018 21:40:38 -0000

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

v2.23.0 | Report a Bug | By Email