Skip to content

Protocol version / backward compatibility #113

@pawel-kow

Description

@pawel-kow
  • Protocol version / backward compatibility: are the any anticipatory measures to account for a revision of Domain Connect, e.g., via a protocol version field? If not, why not?

-- jwk – Have a protocol version field seems like it should be necessary for this, but I’d like to hear from the others.

Metadata

Metadata

Assignees

No one assigned

    Labels

    IETFIssues reported from IETF process

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions