Re: [Bier] clarification in https://tools.ietf.org/html/draft-ietf-bier-architecture-08

I suggest to add a mention/reference on AUTH48 since I got the question 2-3
times already from different parties.

Network byte order is normally specified up to 32 and 64 bits (well, maybe
128 if one dealt with SIMD) but BIER takes it into a much longer space so
it's not necessarily evident.

--- tony

On Mon, Oct 30, 2017 at 7:31 AM, Alia Atlas <akatlas@gmail.com> wrote:

> Hi Csaba,
>
> Thanks for letting us know that you are developing bier for
> freerouter.nop.hu.
> I am expecting a number of other relevant drafts to be progressing out of
> the
> BIER WG soon - so this would be a really excellent time to read through and
> provide feedback.
>
> As Acee's email indicated, we always assume Network Byte Order.  This
> particular
> draft is already to the RFC Editor for publication, but during Auth48 it
> may be possible
> to add a brief mention that it is in Network Byte Order.
>
> Regards,
> Alia
>
> On Mon, Oct 30, 2017 at 1:38 AM, matecs <matecs@niif.hu> wrote:
>
>> hi,
>> i'm developing bier for freerouter.nop.hu, and during this process,
>> i found that bitstring encoding is not fully clarified in the drafts.
>> especially, the byte order of bitstring is not specified anywhere.
>> so allow me to suggest a small addition to the arch draft
>> to section 3, below the current two bullets, a third one:
>>
>> * BitString encoding is big endian (msb) on the wire. It means that
>>   if you have to send to BFR-id 1, then you have to set the lowest
>>   bit in the last byte in the BitString.
>>
>> thanks,
>> csaba mate
>> niif/hungarnet
>>
>> _______________________________________________
>> BIER mailing list
>> BIER@ietf.org
>> https://www.ietf.org/mailman/listinfo/bier
>>
>
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>
>