Changes between Version 3 and Version 4 of tsvart-common-issues


Ignore:
Timestamp:
28/01/21 15:36:49 (17 months ago)
Author:
magnus.westerlund@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tsvart-common-issues

    v3 v4  
    1212can check the checklist to make sure they considered the relevant
    1313issues.
    14 
    15 == TSVART guideline regarding use of _tcp and _udp in SRV ==
    16 
    17 The first label of the pair is an underscore character followed by the Application Protocol Name, and the second label is either "_tcp" or "_udp".
    18 
    19 For applications using transport protocols other than TCP, such as SCTP, DCCP, Adobe's RTMFP, etc., the second label of <service> portion of its DNS-SD name should be "_udp"."
    20 
    21 This method is to discover the service, and we want to keep the barrier low for using new transports ... creating new DNS entries for each would create a problem in introducing new transports - they would rely on new DNS provision, and mDNS support.
    22 
    23 DBH advice to TSVART reviewers:
    24 Please flag any document that deals with service assignment and discovery. There is debate in the community about which is the right way to do assignments for new services. Currently, only _tcp and _udp should be used, but that guideline could change, so please make the AD aware there is an assignment.
    2514
    2615== Use of UDP ==
     
    7261== Port Number Use ==
    7362
    74 See BCP165, composed of RFC6335 and RFC7605. In particular, it is useful to avoid multiple ports for a single service, avoid deploying new insecure services (i.e., all services really ought to have security or at least optional security when deployed), etc.
     63See BCP165, composed of RFC6335 and RFC7605. In particular, it is useful to avoid multiple ports for a single service, avoid deploying new insecure services (i.e., all services really ought to have security or at least optional security when deployed), etc.
     64
     65If one during protocol design phase thinks one have a need for assigned port, it is recommended to request early feedback on this aspect.
     66
     67== TSVART guideline regarding use of _tcp and _udp in SRV ==
     68
     69The first label of the pair is an underscore character followed by the Application Protocol Name, and the second label is either "_tcp" or "_udp".
     70
     71For applications using transport protocols other than TCP, such as SCTP, DCCP, Adobe's RTMFP, etc., the second label of <service> portion of its DNS-SD name should be "_udp"."
     72
     73This method is to discover the service, and we want to keep the barrier low for using new transports ... creating new DNS entries for each would create a problem in introducing new transports - they would rely on new DNS provision, and mDNS support.
     74
     75DBH advice to TSVART reviewers:
     76Please flag any document that deals with service assignment and discovery. There is debate in the community about which is the right way to do assignments for new services. Currently, only _tcp and _udp should be used, but that guideline could change, so please make the AD aware there is an assignment.
     77
    7578
    7679