Re: [IPFIX] [Technical Errata Reported] RFC5102 (4984)

--===============6104362707648535086==
Content-Type: multipart/signed;
 boundary="Apple-Mail=_E19A3EF6-02C4-4ECD-B6CF-17CCA49DFE3D";
 protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_E19A3EF6-02C4-4ECD-B6CF-17CCA49DFE3D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi, all,

You can't raise an erratum against the registry, but 7013 provides for =
interoperable revisions to Information Elements to correct errors =
(section 5.2 criterion 2 holds).

Cheers,

Brian


> On 06 Apr 2017, at 15:45, Stewart Bryant <[email protected]> =
wrote:
>=20
> It depends on what IANA think, but it's only about an hour to write =
and the reviews will all go though on the nod.
>=20
> Of course as an AD Benoit may just be able to direct that that this =
obvious correction happens.
>=20
> Stewart
>=20
>=20
> On 06/04/2017 14:23, Andrew Feren wrote:
>> What about an errata on 5102 with a note that that the definitions =
have moved to the registry?  Seems like an odd end run, but if it solves =
the problem...
>>=20
>> -Andrew
>>=20
>> ________________________________________
>> From: IPFIX [[email protected]] on behalf of PJ Aitken =
[[email protected]]
>> Sent: Thursday, April 06, 2017 5:37 AM
>> To: Stewart Bryant; [email protected]; [email protected]; =
[email protected]; [email protected]; [email protected]; =
[email protected]; [email protected]; [email protected]
>> Cc: [email protected]
>> Subject: Re: [IPFIX] [Technical Errata Reported] RFC5102 (4984)
>>=20
>> That would be possible, though it seems like a lot of effort for the
>> addition of two clarifying words, "least significant" ?
>>=20
>> P.
>>=20
>>=20
>> On 06/04/17 10:29, Stewart Bryant wrote:
>>> Paul
>>>=20
>>> If necessary you could write a one page RFC asking IANA to add a =
note
>>> to the registry.
>>>=20
>>> Stewart
>>>=20
>>>=20
>>> On 05/04/2017 19:16, PJ Aitken wrote:
>>>> I should point out that although RFC 5102 has been obsoleted by RFC
>>>> 7012, 7012 doesn't actually contain any Information Element
>>>> definitions; it simply points to IANA's IPFIX registry as the
>>>> normative reference for Element definitions.
>>>>=20
>>>> So the issue doesn't arise in 7012, and I suspect it's not possible
>>>> to raise an errata against the registry.
>>>>=20
>>>> P.
>>>>=20
>>>>=20
>>>> On 30/03/17 13:45, RFC Errata System wrote:
>>>>> The following errata report has been submitted for RFC5102,
>>>>> "Information Model for IP Flow Information Export".
>>>>>=20
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> =
https://linkprotect.cudasvc.com/url?a=3Dhttps://urldefense.proofpoint.com/=
v2/url%3fu%3dhttps-3A__www.rfc-2Deditor.org_errata-5Fsearch.php-3Frfc-3D51=
02-26eid-3D4984%26d%3dDwIC-g%26c%3dIL_XqQWOjubgfqINi2jTzg%26r%3dl3qN-NVkUT=
PhhRxKVpFXRDjrG3WNcj_6aGqXB9E7JYU%26m%3dlbHlVRM8W9dbZUz-UVd1z1hzVa3rIiNL-6=
zIIFo8oMo%26s%3dqFdcGTGJe09BgcdUjB6EszW7hMzekalZnfj8wx5JlNw%26e%3d&c=3DE,1=
,POSFjbIcmfzya-gNUP5rX4D4UfQQg4AwYC59vms0nF1wQWLNUVnaAiF5ob6Uae9OGK7KJmApL=
2_YmgpwUhW4gYwEcADORoaJSQoTSL3CL1vf&typo=3D1
>>>>>=20
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Paul Aitken <[email protected]>
>>>>>=20
>>>>> Section: 5.2.10, appA
>>>>>=20
>>>>> Original Text
>>>>> -------------
>>>>> Each bit represents an Information Element in the Data Record
>>>>> with the n-th bit
>>>>> representing the n-th Information Element.
>>>>>=20
>>>>> Corrected Text
>>>>> --------------
>>>>> Each bit represents an Information Element in the Data Record,
>>>>> with the n-th least significant bit
>>>>> representing the n-th Information Element.
>>>>>=20
>>>>> Notes
>>>>> -----
>>>>> A misunderstand arose as to whether bits were assigned in host =
order
>>>>> or network order - so clarify that the bits are assigned from the
>>>>> least significant to the most significant, ie right-to-left rather
>>>>> than left-to-right.
>>>>>=20
>>>>> Moreover, this clarification applies to IANA's IPFIX registry.
>>>>>=20
>>>>> NB RFC 8038 re-uses this definition for mibIndexIndicator.
>>>>> Consistency between the definitions is desirable.
>>>>>=20
>>>>> Instructions:
>>>>> -------------
>>>>> This erratum is currently posted as "Reported". If necessary, =
please
>>>>> use "Reply All" to discuss whether it should be verified or
>>>>> rejected. When a decision is reached, the verifying party
>>>>> can log in to change the status and edit the report, if necessary.
>>>>>=20
>>>>> --------------------------------------
>>>>> RFC5102 (draft-ietf-ipfix-info-15)
>>>>> --------------------------------------
>>>>> Title               : Information Model for IP Flow Information =
Export
>>>>> Publication Date    : January 2008
>>>>> Author(s)           : J. Quittek, S. Bryant, B. Claise, P. Aitken,
>>>>> J. Meyer
>>>>> Category            : PROPOSED STANDARD
>>>>> Source              : IP Flow Information Export
>>>>> Area                : Operations and Management
>>>>> Stream              : IETF
>>>>> Verifying Party     : IESG
>>>>>=20
>>>>> _______________________________________________
>>>>> IPFIX mailing list
>>>>> [email protected]
>>>> _______________________________________________
>>>> IPFIX mailing list
>>>> [email protected]
>>>> =
https://linkprotect.cudasvc.com/url?a=3Dhttps://urldefense.proofpoint.com/=
v2/url%3fu%3dhttps-3A__www.ietf.org_mailman_listinfo_ipfix%26d%3dDwIC-g%26=
c%3dIL_XqQWOjubgfqINi2jTzg%26r%3dl3qN-NVkUTPhhRxKVpFXRDjrG3WNcj_6aGqXB9E7J=
YU%26m%3dlbHlVRM8W9dbZUz-UVd1z1hzVa3rIiNL-6zIIFo8oMo%26s%3d2CAUPZ9aGFiHyUV=
Utn2cZFp3fcwj4DUALHp38x4XnC8%26e%3d&c=3DE,1,pcYrfKgiAK5NJHIqb30BLQrXBHi8Lo=
8-mgP6pHj3ho1uiEqr0t_tIoUPPm2W5esu67hb-exkoIxDnLvptn6Fk1XN_eXkMZbhZslQnOte=
FYgZtZG7_ZC0ruA,&typo=3D1
>>>=20
>> _______________________________________________
>> IPFIX mailing list
>> [email protected]
>> =
https://linkprotect.cudasvc.com/url?a=3Dhttps://www.ietf.org/mailman/listi=
nfo/ipfix&c=3DE,1,usIqknq8V3E9Vc_Br3gQ45teOaNlF3LfzLHNrQfB4rcp1FD80k14Pk3J=
Vl_c5gVkoOA2yrwp8SRtE_kUr0YLtIlWtEs33OppFfZ7Xp_6PNt-XItuFw,,&typo=3D1
>=20
> _______________________________________________
> IPFIX mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix


--Apple-Mail=_E19A3EF6-02C4-4ECD-B6CF-17CCA49DFE3D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJY9ipkAAoJEIoSt78L6kaj+sQQAL1uHKSnypHiclkJ8NQm94lx
dSVAC/cp9Vl+AmXFJl8JsKQw4826ysMoEG+xLSLF5+0iaPfLd4Yn+Ggh1Zmig7dS
HzfGwW8jWZzKGJYyoXef04D/n0xQhzbU1/ss9lO/J8AkgqfNHmkOsBFO++5UKGXu
hoN9Zt2ad+4JrTM70u9G2XbJkg6vMqjQRhjDRmHo/2WqkDThBfhxWatrW1EC4mt5
zWLYRiPPhvr62OkX/k8HohFS2zQvHFizLxpo8JcQ5qnqOj4H6rIVSv2DrQa/WMJs
duw+f9HZWEIOyvSzc0KiXf1nS9DIC7p00jF5KWh27K2NwtBYeUiyRfOX/IZ/xzbm
4/ZRDB3zS7+ZwED8O1nItiRu3DcuAoP9KuqDQ5q3DHHdH6mhPL9FNDqpanJ5QAzV
QkbWZG5lkEo+W6UzrPqUuN5ZG1G0zXhp5RY5XOZrQY2Q8WqmOgPmGGxKpuXL6FUl
g31J4hwctbStv5Sv1MQeboDhY+tOy3alWavW8lJKPo5fLibzK3UhPjRj/VMYo/9g
xs3Td960GtfswJgFDsUo3bUm9E6wSlWF7C+stdbp7g0NWx2/TsD7Y/7/+uI8dTfG
3fpV3jfL4XKIGZJRxwzDFQErfUgOcK7u+PMbNaPlNjRtVc9xkUMaVvR//J+b/THw
mvbBcTbgqRg+Y8cTYzFW
=uSUs
-----END PGP SIGNATURE-----

--Apple-Mail=_E19A3EF6-02C4-4ECD-B6CF-17CCA49DFE3D--


--===============6104362707648535086==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix

--===============6104362707648535086==--