p4-apps@lists.p4.org

P4 Applications Working Group

View all threads

INT v2.0 released!

LJ
Lee, Jeongkeun
Wed, Feb 26, 2020 2:42 AM

Dear members,

We're glad to announce INT v2.0 was cut and is available at:

https://github.com/p4lang/p4-applications/blob/master/docs/INT_v2_0.pdf

The major changes in v2.0 include

  • Domain specific extension
    *  Provides a lot of flexibility, adopted by IETF IOAM as well
    *  in INT it also allows 'source-only' metadata for Edge-to-Edge use cases
  • New transports
    *  IPv4/GRE
    *  new UDP encap using a new UDP destination port
    *  VXLAN <-> VXLAN GPE conversion
  • Metadata
    *  Timestamps in 8B
    *  Level 2 Port ID (e.g., virtual interface)
    *  shared buffer occupancy
  • Introduced XD, MD, MX application modes

Next steps:

  • Telemetry report spec 2.0
  • INT v2.1
    *  define MX-type header
    *  define CL (Closed Loop) type for NIC closed-loop control use cases
    *  define Destination header, if needed
    *  (all three has a commonality: no header addition by transit nodes)
    *  ipv6 hop-by-hop extension

Thanks a lot for all your great inputs.
We will soon announce the next meeting schedule.

JK Lee
Mukesh Hira

Dear members, We're glad to announce INT v2.0 was cut and is available at: https://github.com/p4lang/p4-applications/blob/master/docs/INT_v2_0.pdf The major changes in v2.0 include * Domain specific extension * Provides a lot of flexibility, adopted by IETF IOAM as well * in INT it also allows 'source-only' metadata for Edge-to-Edge use cases * New transports * IPv4/GRE * new UDP encap using a new UDP destination port * VXLAN <-> VXLAN GPE conversion * Metadata * Timestamps in 8B * Level 2 Port ID (e.g., virtual interface) * shared buffer occupancy * Introduced XD, MD, MX application modes Next steps: * Telemetry report spec 2.0 * INT v2.1 * define MX-type header * define CL (Closed Loop) type for NIC closed-loop control use cases * define Destination header, if needed * (all three has a commonality: no header addition by transit nodes) * ipv6 hop-by-hop extension Thanks a lot for all your great inputs. We will soon announce the next meeting schedule. JK Lee Mukesh Hira
NM
Nick McKeown
Wed, Feb 26, 2020 4:22 AM

Great job team - this is a big milestone for INT. It is really super to see
it evolve and mature as more people use it.

Nick

On Tue, Feb 25, 2020 at 6:43 PM Lee, Jeongkeun jk.lee@intel.com wrote:

Dear members,

We're glad to announce INT v2.0 was cut and is available at:

https://github.com/p4lang/p4-applications/blob/master/docs/INT_v2_0.pdf

The major changes in v2.0 include

- Domain specific extension
   - Provides a lot of flexibility, adopted by IETF IOAM as well
   - in INT it also allows 'source-only' metadata for Edge-to-Edge use
   cases
- New transports
   - IPv4/GRE
   - new UDP encap using a new UDP destination port
   - VXLAN <-> VXLAN GPE conversion
- Metadata
   - Timestamps in 8B
   - Level 2 Port ID (e.g., virtual interface)
   - shared buffer occupancy
   - Introduced XD, MD, MX application modes

Next steps:

- Telemetry report spec 2.0
- INT v2.1
   - define MX-type header
   - define CL (Closed Loop) type for NIC closed-loop control use cases
   - define Destination header, if needed
   - (all three has a commonality: no header addition by transit nodes)
   - ipv6 hop-by-hop extension

Thanks a lot for all your great inputs.
We will soon announce the next meeting schedule.

JK Lee
Mukesh Hira


P4-apps mailing list
P4-apps@lists.p4.org
http://lists.p4.org/mailman/listinfo/p4-apps_lists.p4.org

--
Nick McKeown 马格理
Professor of Computer Science and Electrical Engineering
Stanford University, CA 94305-9030
https://www.stanford.edu/~nickm

Great job team - this is a big milestone for INT. It is really super to see it evolve and mature as more people use it. Nick On Tue, Feb 25, 2020 at 6:43 PM Lee, Jeongkeun <jk.lee@intel.com> wrote: > Dear members, > > We're glad to announce INT v2.0 was cut and is available at: > > https://github.com/p4lang/p4-applications/blob/master/docs/INT_v2_0.pdf > > The major changes in v2.0 include > > - Domain specific extension > - Provides a lot of flexibility, adopted by IETF IOAM as well > - in INT it also allows 'source-only' metadata for Edge-to-Edge use > cases > - New transports > - IPv4/GRE > - new UDP encap using a new UDP destination port > - VXLAN <-> VXLAN GPE conversion > - Metadata > - Timestamps in 8B > - Level 2 Port ID (e.g., virtual interface) > - shared buffer occupancy > - Introduced XD, MD, MX application modes > > Next steps: > > - Telemetry report spec 2.0 > - INT v2.1 > - define MX-type header > - define CL (Closed Loop) type for NIC closed-loop control use cases > - define Destination header, if needed > - (all three has a commonality: no header addition by transit nodes) > - ipv6 hop-by-hop extension > > Thanks a lot for all your great inputs. > We will soon announce the next meeting schedule. > > JK Lee > Mukesh Hira > > _______________________________________________ > P4-apps mailing list > P4-apps@lists.p4.org > http://lists.p4.org/mailman/listinfo/p4-apps_lists.p4.org > -- Nick McKeown 马格理 Professor of Computer Science and Electrical Engineering Stanford University, CA 94305-9030 https://www.stanford.edu/~nickm