[ovs-discuss] PACKET_IN context fields

[Sebastian Spies]

Hey list,

when OVS sends frames to the controller using PACKET_IN PDUs, it looks
like [1].
The OF1.3 spec says, that the switch must support context fields like
OFB_IN_PORT - others are optional.
Do you plan to support some or all of the fields like ETH_SRC and
ETH_DST and ETHER_TYPE as a courtesy to the controller, so no additional
packet parsing is needed?
OT and wrong list, but I would also like to see the parsed context
fields being configured by the controller, as it would make no sense to
parse a whole PDU down to port numbers, when I just consume ethernet
fields. What do you think?

1:

OpenFlow 1.3
    Version: 1.3 (0x04)
    Type: OFPT_PACKET_IN (10)
    Length: 42
    Transaction ID: 0
    Buffer ID: 256
    Total length: 60
    Reason: OFPR_NO_MATCH (0)
    Table ID: 0
    Cookie: 0x0000000000000001
    Match
        Type: OFPMT_OXM (1)
        Length: 12
        OXM field
            Class: OFPXMC_OPENFLOW_BASIC (0x8000)
            0000 000. = Field: OFPXMT_OFB_IN_PORT (0)
            .... ...0 = Has mask: False
            Length: 4
            Value: 2
        Pad: 00000000
    Pad: 0000

Best regards,
Sebastian

-- 

SEBASTIAN SPIES
Computer Scientist

+49 1577 783 08 83

lnked.in/sspies
vastly.de