Re: [IPFIX] [QUAR] Re: RFC 6728 IETF IPFIX Yang Discussion
"Wayne Tackabury" <[email protected]> Mon, 15 Jan 2018 21:10:01 +0000
| Newsgroups | gmane.ietf.ipfix |
|---|---|
| Message-ID | <OF39D57ECE.E528A80C-ON00258216.00736598-00258216.00744614@notes.na.collabserv.com> |
--===============6924686962517377148== Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <div class=3D"socmaildefaultfont" dir=3D"ltr" style=3D"font-family:Arial, H= elvetica, sans-serif;font-size:10.5pt" ><div dir=3D"ltr" >Regarding SCTP, a= s of this writing, it is not and can not be mandatory. Not many comme= rcial collectors support it. I've found this to be a bit of an "eleph= ant in the room" on the RFC directions.</div> <div dir=3D"ltr" > </div> <div dir=3D"ltr" >To be perfectly practical, as things have emerged since t= he days of RFC[s] 510x, SCTP has not been made sufficiently stable in linux= kernel and user interfaces that it could support carrier-grade flow convey= ance dependencies. There are probably other nontechnical barriers to = acceptance. To be sure, this is unfortunate, since SCTP still admirably mee= ts the original design goals.</div> <div dir=3D"ltr" > </div> <div dir=3D"ltr" >Without getting into it, where I'm aware of implementatio= ns that meed tp make use of the "messaging" benefits of SCTP over UDP, the = less-than-standard path of TCP over some defacto standard port has be= en used. Others may know of different implementations, but this is ba= sed on subjective, but voluminous, input from implementations I've seen at = customer sites and discussions with colleagues at different vendor enterpri= ses. Again, this is not an editorial on technical merit.</div> <div dir=3D"ltr" > </div> <div dir=3D"ltr" >Regards,</div> <div dir=3D"ltr" >Wayne</div> <div dir=3D"ltr" > </div> <div dir=3D"ltr" > </div> <blockquote data-history-content-modified=3D"1" dir=3D"ltr" style=3D"border= -left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; = margin-right:0px" >----- Original message -----<br>From: Juergen Schoenwael= der <[email protected]><br>Sent by: "IPFIX" <ip= [email protected]><br>To: Andrew Feren <[email protected]>= ;<br>Cc: 'Marta Seda' <[email protected]>, "Aitken, Paul" <paul= [email protected]>, "'[email protected]'" <[email protected]><br>Subj= ect: Re: [IPFIX] [QUAR] Re: RFC 6728 IETF IPFIX Yang Discussion<br>Date: Mo= n, Jan 15, 2018 1:51 PM<br> <div><font size=3D"2" face=3D"Default Monospace,Courier New,Courier,monospa= ce" >I fail to see why this would be the case. (But I agree that renaming<b= r>identifiers for the sake of renaming them is having little value.)<br><br= >/js<br><br>On Mon, Jan 15, 2018 at 06:09:20PM +0000, Andrew Feren wrote:<b= r>> In particular renaming identifiers would break any implementations o= f RFC 7373 "Textual Representation of IP Flow Information Export (IPFIX) Ab= stract Data Types".<br>><br>> -Andrew<br>><br>> =5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F<br>> From: IPFIX [[email protected]] on behalf of Gerhard Mu= enz [[email protected]]<br>> Sent: Saturday, January 13, 2018 4:43 AM<= br>> To: Benoit Claise; Aitken, Paul; 'Marta Seda'<br>> Cc: 'ipfix@ie= tf.org'<br>> Subject: [QUAR] Re: [IPFIX] RFC 6728 IETF IPFIX Yang Discus= sion<br>><br>><br>> Marta, all,<br>><br>> A few additional t= houghts regarding your questions:<br>><br>> 1) I would not expect tha= t not following current naming convention hinders implementation of RFC 672= 8. On the other hand, if we change just the names of the identifiers, we lo= se interoperability with older implementations that may exist.<br>><br>&= gt; 2) I think that it is reasonable that destinationIPAddress is mandatory= because network management systems should be able to query the IP address = to which an Exporting Process sends data. As Paul stated, RFC 6728 does not= say how the destination IP address is set.<br>><br>> 3) SCTP is stil= l a mandatory transport for a compliant implementation of an IPFIX device, = not a feature. See: <a href=3D"https://urldefense.proofpoint.com/v2/url?u= =3Dhttps-3A=5F=5Ftools.ietf.org=5Fhtml=5Frfc7011-23section-2D10.1&d=3DD= wIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW= =5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8= &s=3DqunYBh7bv5ABGGsiP6-CjGVRw8xFMTnuuwuibkkNfBE&e=3D" target=3D"= =5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Ftools= .ietf.org=5Fhtml=5Frfc7011-23section-2D10.1&d=3DDwIGaQ&c=3Djf=5FiaS= HvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5Fk= E&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DqunYBh7bv5ABG= GsiP6-CjGVRw8xFMTnuuwuibkkNfBE&e=3D</a><<a href=3D"https://urldefens= e.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa= -3Dhttps-3A=5F=5Ftools.ietf.org=5Fhtml=5Frfc7011-2523section-2D10.1-26c-3DE= -2C1-2Cr3o6fj1SXot8TQIPgevXNx5yfL8QvlF982Ch9DX27MByjz7bAdEaF9tjDoDzj1XgWtTX= YfN1Z9mXiFy81bK1Aq33fYFzGl5W-2D2Dh-5F-2DxePoq9GNzzaPGdYj0o-26typo-3D1&d= =3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw= 4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOL= L3H8&s=3DM0CgR7V3IlBqkpQDo2Brx-bewHWnHX=5Fa5l7YChB32BI&e=3D" target= =3D"=5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fl= inkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Ftools.ietf.org=5Fhtml=5Frf= c7011-2523section-2D10.1-26c-3DE-2C1-2Cr3o6fj1SXot8TQIPgevXNx5yfL8QvlF982Ch= 9DX27MByjz7bAdEaF9tjDoDzj1XgWtTXYfN1Z9mXiFy81bK1Aq33fYFzGl5W-2D2Dh-5F-2DxeP= oq9GNzzaPGdYj0o-26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&= amp;r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94EL= pPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DM0CgR7V3IlBqkpQDo2Brx-bewHWnHX= =5Fa5l7YChB32BI&e=3D</a>><br>><br>> Best regards,<br>> Gerh= ard<br>><br>><br>><br>> On 10.01.2018 08:33, Benoit Claise wrot= e:<br>> Hi,<br>> Marta, Benoit,<br>><br>> 1. Are there efforts = to update other RFCs to meet the latest YANG best practices?<br>> Yes. E= x: <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fda= tatracker.ietf.org=5Fdoc=5Fdraft-2Dietf-2Dnetmod-2Drfc7223bis=5F&d=3DDw= IGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW= =5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8= &s=3DDml5zgSWzeUBwS1XyKmCG-y3bWePHxpzt3PCej4w=5Fzw&e=3D" target=3D"= =5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fdatat= racker.ietf.org=5Fdoc=5Fdraft-2Dietf-2Dnetmod-2Drfc7223bis=5F&d=3DDwIGa= Q&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F= =5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&am= p;s=3DDml5zgSWzeUBwS1XyKmCG-y3bWePHxpzt3PCej4w=5Fzw&e=3D</a><<a href= =3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Flinkprotect.= cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Fdatatracker.ietf.org=5Fdoc=5Fdraft-2D= ietf-2Dnetmod-2Drfc7223bis=5F-26c-3DE-2C1-2C990HtCyvSKBHwQOS7jpHkeSpsvC2M7i= KDlI-5FbfqIgW2gpaEOYhngASoi8LRRhuM67bRdHS2Hyi7cVHyXDuiheARWFxSpap-5FiznZ68Z= knJgFbizFJolgU-26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&a= mp;r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELp= Pz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DwhhuVEyPDEyPYoboty-rb0h=5FRQBoH= KqNmiQoGwpLBlw&e=3D" target=3D"=5Fblank" >https://urldefense.proofpoint= .com/v2/url?u=3Dhttps-3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A= =5F=5Fdatatracker.ietf.org=5Fdoc=5Fdraft-2Dietf-2Dnetmod-2Drfc7223bis=5F-26= c-3DE-2C1-2C990HtCyvSKBHwQOS7jpHkeSpsvC2M7iKDlI-5FbfqIgW2gpaEOYhngASoi8LRRh= uM67bRdHS2Hyi7cVHyXDuiheARWFxSpap-5FiznZ68ZknJgFbizFJolgU-26typo-3D1&d= =3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw= 4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOL= L3H8&s=3DwhhuVEyPDEyPYoboty-rb0h=5FRQBoHKqNmiQoGwpLBlw&e=3D</a>>= <br>> The goal is to specify NMDA-compliant (draft-ietf-netmod-revised-d= atastores-09<<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhtt= ps-3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Fdatatracker.ie= tf.org=5Fdoc=5Fdraft-2Dietf-2Dnetmod-2Drevised-2Ddatastores=5F-26c-3DE-2C1-= 2CByKxVFeHf8k0Yb1kzzkQnQg33VfrR12Hy6dJzQTbkgStXZt3NzfCi7l981VvXCCM3L3iwQ3FF= 8lz77mT4C5yuZEfVe-2D78uXEs5xDZql2y-2D-2D4iDlmOUQ-2C-26typo-3D1&d=3DDwIG= aQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F= =5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&am= p;s=3DgGNMKyVcGZrZBCbVl5XjjnnyJnRDUxt8jU3e24fcQBU&e=3D" target=3D"=5Fbl= ank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Flinkprotec= t.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Fdatatracker.ietf.org=5Fdoc=5Fdraft-= 2Dietf-2Dnetmod-2Drevised-2Ddatastores=5F-26c-3DE-2C1-2CByKxVFeHf8k0Yb1kzzk= QnQg33VfrR12Hy6dJzQTbkgStXZt3NzfCi7l981VvXCCM3L3iwQ3FF8lz77mT4C5yuZEfVe-2D7= 8uXEs5xDZql2y-2D-2D4iDlmOUQ-2C-26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHv= JObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&= amp;m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DgGNMKyVcGZrZBCb= Vl5XjjnnyJnRDUxt8jU3e24fcQBU&e=3D</a>>) YANG modules<br>><br>>= 2. Since the IPFIX WG closed, there has been little ongoing IPFIX work in = the IETF. Is there a specific need to update RFC 6728 rather than just reco= gnising it as a product of it's time?<br>> This type of feedback should = come from implementation experience.<br>><br>> Regards, Benoit<br>>= ; Note that it's > 5 years old.<br>><br>> Also see @PJ inline:<br>= ><br>><br>> On 09/01/2018 16:01, Benoit Claise wrote:<br>> Hi M= arta,<br>> Hello,<br>> I am reaching out to the IETF IPFIX mailing li= st on some issues I have run into with respect to RFC 6728 =E2=80=9CC= onfiguration Data Model for the IP Flow Information Export (IPFIX) an= d Packet Sampling (PSAMP) Protocols=E2=80=9D<br>><br>><br>> = 1. RFC 6728 doesn=E2=80=99t meet the latest Yang Best Practices (<a = href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Ftools.ie= tf.org=5Fhtml=5Fdraft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.3.1&a= mp;d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5F= UtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5B= voOLL3H8&s=3DSSYo4WM-xFfyPgrSh-cja-jQFQEucW4daULPdwg2zSI&e=3D" targ= et=3D"=5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F= =5Ftools.ietf.org=5Fhtml=5Fdraft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23sectio= n-2D4.3.1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9= l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWh= v6uxVZ5pB5BvoOLL3H8&s=3DSSYo4WM-xFfyPgrSh-cja-jQFQEucW4daULPdwg2zSI&= ;e=3D</a><<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-= 3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Furldefense.proofp= oint.com=5Fv2=5Furl-253fu-253dhttps-2D3A-5F-5Ftools.ietf.org-5Fhtml-5Fdraft= -2D2Dietf-2D2Dnetmod-2D2Drfc6087bis-2D2D15-2D23section-2D2D4.3.1-2526d-253d= DwMD-2Dg-2526c-253dLFYZ-2Do9-5FHUMeMTSQicvjIg-2526r-253df8F8yzrqBTw6EPtR1rb= ibO-5FVFIc-2DcdnjIJ9he-5Fqu7xs-2526m-253d0c5ATjuT0-2D4IlDzLYM9h-5FRbPjCBQUv= -5F6aExRL-5Ffl-2D5M-2526s-253dHhi7V6njCFNBbSsjC6sPgNfVu5DA8iQzdzsnA-5FiQBzQ= -2526e-253d-26c-3DE-2C1-2C5Zsm8llhIef-5FjTZU2aAY2fj-5FKvmJs-2DzBz2HIfVEkrhY= 7UwWsg3UnykcCPzCUM7b-5FL6CTmk-5FVY1-2DTo7t8aTM7RBz2ayGhe3OrxbBk7-5FOy6I7gQS= kKDC8Eig-2C-2C-26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&a= mp;r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELp= Pz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3Doj6Kq-4SRjuodk73yxC5K1cDKw8XP95= L=5FH=5Fm3ErUuQM&e=3D" target=3D"=5Fblank" >https://urldefense.proofpoi= nt.com/v2/url?u=3Dhttps-3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3= A=5F=5Furldefense.proofpoint.com=5Fv2=5Furl-253fu-253dhttps-2D3A-5F-5Ftools= .ietf.org-5Fhtml-5Fdraft-2D2Dietf-2D2Dnetmod-2D2Drfc6087bis-2D2D15-2D23sect= ion-2D2D4.3.1-2526d-253dDwMD-2Dg-2526c-253dLFYZ-2Do9-5FHUMeMTSQicvjIg-2526r= -253df8F8yzrqBTw6EPtR1rbibO-5FVFIc-2DcdnjIJ9he-5Fqu7xs-2526m-253d0c5ATjuT0-= 2D4IlDzLYM9h-5FRbPjCBQUv-5F6aExRL-5Ffl-2D5M-2526s-253dHhi7V6njCFNBbSsjC6sPg= NfVu5DA8iQzdzsnA-5FiQBzQ-2526e-253d-26c-3DE-2C1-2C5Zsm8llhIef-5FjTZU2aAY2fj= -5FKvmJs-2DzBz2HIfVEkrhY7UwWsg3UnykcCPzCUM7b-5FL6CTmk-5FVY1-2DTo7t8aTM7RBz2= ayGhe3OrxbBk7-5FOy6I7gQSkKDC8Eig-2C-2C-26typo-3D1&d=3DDwIGaQ&c=3Djf= =5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6= Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3Doj6Kq-4= SRjuodk73yxC5K1cDKw8XP95L=5FH=5Fm3ErUuQM&e=3D</a>>). Leaf ide= ntifiers are camel case (e.g., destinationAddress instead of destination-ad= dress). Are there any ongoing efforts to update RFC 6728 to meet the = latest best practices?<br>> Not as far as I know.<br>><br>> Regard= s, Benoit<br>><br>><br>> 1.<br>><br>> Id= entifiers SHOULD follow a consistent naming pattern throughout the<br>> = module. Only lower-case letters, numbers, and dashes SHO= ULD be used<br>> in identifier names. Upper-case char= acters and the underscore<br>> character MAY be used if the= identifier represents a well-known value<br>> that uses th= ese characters.<br>><br>> Identifiers SHOULD include com= plete words and/or well-known acronyms<br>> or abbreviation= s. Child nodes within a container or list SHOULD NOT<br>> &= nbsp;replicate the parent identifier. YANG identifiers are hierarchic= al<br>> and are only meant to be unique within the the set = of sibling nodes<br>> defined in the same module namespace.= <br>><br>> It is permissible to use common identifiers s= uch as "name" or "id" in<br>> data definition statements, e= specially if these data nodes share a<br>> common data type= .<br>><br>> Identifiers SHOULD NOT carry any special sem= antics that identify data<br>> modelling properties. = Only YANG statements and YANG extension<br>> statements are= designed to convey machine readable data modelling<br>> pr= operties. For example, naming an object "config" or "state" does<br>&= gt; not change whether it is configuration data or state data.= Only<br>> defined YANG statements or YANG extension = statements can be used to<br>> assign semantics in a machin= e readable format in YANG.<br>><br>><br>> 1. I genera= ted the RFC 6728 yang tree (see attached). The tcp and udp exporting = processes support a destinationIPAddress (line 400, 455) which is mandatory= . The type is inet:ip-address.<br>><br>> * = A collector may be doing load balancing. Rather than managing = ip-addresses, the collector may be using DNS (an exporter could resolve fro= m the domain name where the collector is located).<br>><br>> @PJ: Loa= d balancing and DNS are independent. Load balancing IPFIX is probably a bad= idea since templates need to be available on all collectors, and out of st= ep sequence numbers in the data records would cause spurious reports of los= t data. If DNS is used to obtain the collector's address, arguably it shoul= d be a one-time lookup rather than incurring a DNS lookup per export packet= .<br>><br>><br>><br>> 1.<br>><br>> &= nbsp;*<br>> * The collector address may be le= arnt via other methods (e.g., through DHCP options)<br>> &= nbsp;* A choice statement to select what method to use seems more ap= propriate than what is presently in RFC 6728. For example (use some s= horthand)<br>><br>> choice destination-method{<br>> = case destination-address{<br>>= &nbs= p; leaf destination-address// rw with ty= pe inet:host<br>>  = ; }<br>> case dh= cp-acquired-address{<br>> &nbs= p; container= dcp-acquired-address{<br>> &n= bsp; = leaf destination-ip-addres= s inet-address //ro<br>>  = ; }<br>> }<br>><br>> &nb= sp; H= owever I can=E2=80=99t augment to ietf-ipfix because destinationIPAddress i= s mandatory. Can the group suggest methods to (a) change the destinat= ionIPAddress type and (b) allow a choice?<br>><br>> @PJ: The selectio= n could also be done out of band so the exporter need not know how the addr= ess is determined. eg a configuration system could determine the address by= any of these methods or otherwise, and impose that address using the curre= nt model.<br>><br>><br>><br>> 1. RFC 6728 mandates= SCTP transport. I understand the logic behind this (IETF prefers use= of SCTP). There are situations where sctp is unnecessary and not sup= ported (e.g., point to point connection). During netconf negotiations= you can announce your feature set (currently sctptransport is not a featur= e). Is there ongoing work in updating RFC 6728 to include sctptranspo= rt as a feature (so that the device can announce whether or not it supports= sctptransport)?<br>><br>> @PJ Same answer as point (2) above, ie is = this necessary and useful?<br>><br>> P.<br>><br>><br>><br>&g= t;<br>> =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F<br>> IPFIX mailing list<br>> [email protected]<<a href=3D"mailto:= [email protected]" target=3D"=5Fblank" >mailto:[email protected]</a>><br>> = <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fwww.i= etf.org=5Fmailman=5Flistinfo=5Fipfix&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTb= x-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m= =3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DzSpyB0Ig1-hgDSYsX7hH= 1qdwzy0nZuWAMrFjAY3q02U&e=3D" target=3D"=5Fblank" >https://urldefense.p= roofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fwww.ietf.org=5Fmailman=5Flistinfo=5F= ipfix&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y= 0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6ux= VZ5pB5BvoOLL3H8&s=3DzSpyB0Ig1-hgDSYsX7hH1qdwzy0nZuWAMrFjAY3q02U&e= =3D</a><<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A= =5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Fwww.ietf.org=5Fmail= man=5Flistinfo=5Fipfix-26c-3DE-2C1-2CQcSaORG4ENECojkXawtykKdqqGaKdIQCAXU-5F= k7DUoimbxp4p9KhoEppQlQ1LswK1E5yY5kvIL8XYyqMbCphIEyv8aBgtyyQbbN31fnbrx9I-2C-= 26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU= 9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaW= hv6uxVZ5pB5BvoOLL3H8&s=3DcQFI-IsxLhklEI0w-JcCksB=5FYNvx9v06CpqsjQys0N8&= amp;e=3D" target=3D"=5Fblank" >https://urldefense.proofpoint.com/v2/url?u= =3Dhttps-3A=5F=5Flinkprotect.cudasvc.com=5Furl-3Fa-3Dhttps-3A=5F=5Fwww.ietf= .org=5Fmailman=5Flistinfo=5Fipfix-26c-3DE-2C1-2CQcSaORG4ENECojkXawtykKdqqGa= KdIQCAXU-5Fk7DUoimbxp4p9KhoEppQlQ1LswK1E5yY5kvIL8XYyqMbCphIEyv8aBgtyyQbbN31= fnbrx9I-2C-26typo-3D1&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r= =3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5B= moxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DcQFI-IsxLhklEI0w-JcCksB=5FYNvx9v06C= pqsjQys0N8&e=3D</a>><br>><br>><br><br>> =5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>> IPFIX mailing list= <br>> [email protected]<br>> <a href=3D"https://urldefense.proofpoint.co= m/v2/url?u=3Dhttps-3A=5F=5Fwww.ietf.org=5Fmailman=5Flistinfo=5Fipfix&d= =3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw= 4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOL= L3H8&s=3DzSpyB0Ig1-hgDSYsX7hH1qdwzy0nZuWAMrFjAY3q02U&e=3D" target= =3D"=5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fw= ww.ietf.org=5Fmailman=5Flistinfo=5Fipfix&d=3DDwIGaQ&c=3Djf=5FiaSHvJ= ObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&a= mp;m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DzSpyB0Ig1-hgDSYs= X7hH1qdwzy0nZuWAMrFjAY3q02U&e=3D</a><br><br><br>--<br>Juergen Schoenwae= lder Jacobs University Bremen gGmbH<br>P= hone: +49 421 200 3587 Campus Ring 1 | 28759 Br= emen | Germany<br>Fax: +49 421 200 3103 = <<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=5F=5Fw= ww.jacobs-2Duniversity.de=5F&d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZO= g&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94= ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DcC8C3QfrkIEC1Vo-QLwKrh955-ev= z=5FTr3MYoFDTmD1A&e=3D" target=3D"=5Fblank" >https://urldefense.proofpo= int.com/v2/url?u=3Dhttps-3A=5F=5Fwww.jacobs-2Duniversity.de=5F&d=3DDwIG= aQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F= =5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&am= p;s=3DcC8C3QfrkIEC1Vo-QLwKrh955-evz=5FTr3MYoFDTmD1A&e=3D</a>><br><br= >=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>IP= FIX mailing list<br>[email protected]<br><a href=3D"https://urldefense.proofpo= int.com/v2/url?u=3Dhttps-3A=5F=5Fwww.ietf.org=5Fmailman=5Flistinfo=5Fipfix&= amp;d=3DDwIGaQ&c=3Djf=5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR= =5FUtUw4WaW=5F=5FJt3CBhpQR6Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5p= B5BvoOLL3H8&s=3DzSpyB0Ig1-hgDSYsX7hH1qdwzy0nZuWAMrFjAY3q02U&e=3D" t= arget=3D"=5Fblank" >https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A= =5F=5Fwww.ietf.org=5Fmailman=5Flistinfo=5Fipfix&d=3DDwIGaQ&c=3Djf= =5FiaSHvJObTbx-siA1ZOg&r=3DeSiUkUZU9l60y0gvR=5FUtUw4WaW=5F=5FJt3CBhpQR6= Qa=5FkE&m=3DAqj94ELpPz5BmoxxBT4zFaWhv6uxVZ5pB5BvoOLL3H8&s=3DzSpyB0I= g1-hgDSYsX7hH1qdwzy0nZuWAMrFjAY3q02U&e=3D</a></font><br> </div></b= lockquote> <div dir=3D"ltr" > </div></div><BR> --===============6924686962517377148== 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 --===============6924686962517377148==--