The pattern for matching the fmtp attribute expects a semicolon after every parameter entry, and the examples included in this project match that pattern, but the specification contradicts this:
Section 7.1 states:
IETF RFC 4566 section “SDP Attributes” specifies the a=fmtp clause including . The section shall consist of a sequence of media
type parameter entries, separated by the semicolon (“;”) character followed by whitespace. There is no
semicolon character after the last item. The a=fmtp clause shall be terminated by a carriage return.
Is this an oversight, intentional, or a versioning issue?
I can make a pull request if this is a simple bug, but since there is specific code to handle a trailing whitespace, I'm assuming that something has changed, and there needs to be a update to handle SDP's that follow this specification.
The pattern for matching the fmtp attribute expects a semicolon after every parameter entry, and the examples included in this project match that pattern, but the specification contradicts this:
Section 7.1 states:
Is this an oversight, intentional, or a versioning issue?
I can make a pull request if this is a simple bug, but since there is specific code to handle a trailing whitespace, I'm assuming that something has changed, and there needs to be a update to handle SDP's that follow this specification.