Re: [IPFIX] templateLifePacket on IPFIX collector

--===============3219094799264689127==
Content-Type: multipart/signed;
 boundary="Apple-Mail=_8F0D05E2-5A70-4957-ABD2-CCF437660961";
 protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_8F0D05E2-5A70-4957-ABD2-CCF437660961
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Petr,

This is specified in section 8.4 of RFC 7011 for UDP:

   Since UDP provides no method for reliable transmission of Templates,
   Exporting Processes using UDP as the transport protocol MUST
   periodically retransmit each active Template at regular intervals.
   The Template retransmission interval MUST be configurable via, for
   example, the templateRefreshTimeout and optionsTemplateRefreshTimeout
   parameters as defined in [RFC6728].  Default settings for these
   values are deployment- and application-specific.

For transports with reliable template lifetimes (TCP, SCTP), templates =
require no refresh, since template state remains synchronized between =
exporter and collector.

Cheers,

Brian


> On 2 Oct 2017, at 09:37, Petr Velan <[email protected]> wrote:
>=20
> Hello IPFIX masters,
>=20
> we are implementing an IPFIX collector and a question came up whether =
to support templateLifePacket configuration as specified in RFC 6728 =
(https://tools.ietf.org/html/rfc6728#section-4.5.2). It seems, that the =
*LifePacket options are not mentioned anywhere else in the IPFIX related =
documents and that the IPFIX protocol specifies only time based timeout =
expiration. Therefore, my question is why the *LifePacket options are =
even present in the RFC 6728 and whether it is necessary to implement =
them for the collector (and exporter as well) to be compliant with the =
IPFIX standard.
>=20
> I think that the whole *LifePacket option came from NetFlow v9 where =
the informational RFC 3954 states that:
>       On a regular basis, the Exporter MUST send all the Template
>       Records and Options Template Records to refresh the Collector.
>       Template IDs have a limited lifetime at the Collector and MUST =
be
>       periodically refreshed.  Two approaches are taken to make sure
>       that Templates get refreshed at the Collector:
>             * Every N number of Export Packets.
>             * On a time basis, so every N number of minutes.
>       Both options MUST be configurable by the user on the Exporter.
>       When one of these expiry conditions is met, the Exporter MUST =
send
>       the Template FlowSet and Options Template.
>=20
>=20
> If that is the case, should the IPFIX standard specify something =
similar as well? Otherwise, it would seem that removing the *LifePacket =
options from the RFC 6728 would prevent further confusion.
>=20
> Kind regards,
> Petr Velan
>=20
> _______________________________________________
> IPFIX mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix


--Apple-Mail=_8F0D05E2-5A70-4957-ABD2-CCF437660961
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlnR80IACgkQihK3vwvq
RqNnxRAAm9M0XKMWWhp8HhTMLNWJa9o09fPqA14S34lDL2yICk6mFsy4ktPg1Fgt
o3ASZv0hLQYbSKnEMZbTf6XZ++h++Ky+ycyNXScu1fK9GdgXKmBC0qfbJv0Y3UMG
fvTlUiGvmlKFP7FkBFz8NjjKp2aetlZaZqAb4Uuo3L+N6c1PCME71XBPBW1X4dK5
JRJoMtZSrUX8+0TNrQxIt1q0PAzRFKAtLdRtnQXUWQzMnVsXDwDde5Oae0HKlCfQ
PUT+hARpp7nj/c35DQauZuvX5BYvaIjGlUTsluT6VE/IG/GArsEWJdRXQDAfeETl
rjnPWcVFBlK3Keo4RkySGdpXm2KtnGAtmONLAQJz9jKJBgCH143M260CM5GMBeSm
PYH+PKB5EDPZI7xQJUt9sVVX9V9E0vaBx66qivqVrmP+8IHuAqhxFCnUhp6bYSGu
gJyITb2se1TH3BZWqY60DUjV63m7BQu8Wsi1tkMM8GxtTXt5LxHs9Y+XyeYNAcyP
d8gGXqwbcI/gS23bF8aeUOxXapImilWmNyL2eCL+Z7a719nrtCC5+hH/neUbodgZ
A21CVf3htikQbiUQlO9zokhtg6Bxi54SZlt986PRaI7/g55wtWtcKLgCqbWJhrCv
5rKic5eoAfTWtoL1Ic2lXA1alIvI3CbRX1PNHU6kgYDp1XSv3aA=
=LQaS
-----END PGP SIGNATURE-----

--Apple-Mail=_8F0D05E2-5A70-4957-ABD2-CCF437660961--


--===============3219094799264689127==
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

--===============3219094799264689127==--