Re: [tram] [Tsv-art] Tsvart last call review of draft-ietf-tram-turnbis-25

["Konda, Tirumaleswar Reddy" <[e-mail]>]

Hi Joe,

The IPv4 and IPv6 fragmentation description is specific to TCP-to-UDP relaying between the client and the peer (only for TCP-to-UDP relay, the DF attribute in the TURN message will be used to set the DF bit in the outgoing UDP packet to the peer). To avoid confusion, I have added two new sub-sections:
15.1.  IP Header Fields for TCP-to-UDP relaying and 15.2 IP Header Fields for UDP-to-TCP relaying

Please see the attached updated draft.

Cheers,
-Tiru

From: Joe Touch <[e-mail]>
Sent: Wednesday, June 19, 2019 8:29 PM
To: Konda, Tirumaleswar Reddy <[e-mail]>
Cc: Magnus Westerlund <[e-mail]>; [e-mail]; Brandon Williams <[e-mail]>; [e-mail]; [e-mail]; [e-mail]
Subject: Re: [Tsv-art] [tram] Tsvart last call review of draft-ietf-tram-turnbis-25


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

________________________________
That fragmentation text is fine; the text on IPv4 and IPv6 fragmentation that appears earlier in Sec 15 is the issue.

Can you just drop that earlier text?

Joe


On Jun 19, 2019, at 7:48 AM, Konda, Tirumaleswar Reddy <[e-mail]<mailto:[e-mail]>> wrote:

Hi Joe,

Please see inline

From: Joe Touch <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, June 19, 2019 8:13 PM
To: Konda, Tirumaleswar Reddy <[e-mail]<mailto:[e-mail]>>
Cc: Magnus Westerlund <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; Brandon Williams <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Tsv-art] [tram] Tsvart last call review of draft-ietf-tram-turnbis-25

CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
________________________________
That text remains insufficient, e.g.:



On Jun 19, 2019, at 7:30 AM, Konda, Tirumaleswar Reddy <[e-mail]<mailto:[e-mail]>> wrote:

Hi Joe,

I have added the following line to address your other comment:

Note that the server does not perform per-packet translation for TCP-to-UDP relaying and vice-versa. For TCP-to-UDP relaying from client to peer, the TURN server sets the DF field in the outgoing UDP packet based on the presence of DONT-FRAGMENT attribute in the TURN message. For UDP-to-TCP relaying from peer to client, the TURN server sets IP header fields in the TCP packets on a per-connection basis for the TCP connection.

Which parameters? Based on what?

[TR] It is already discussed in section 15.

<snip>

   Differentiated Services Code Point (DSCP) field [RFC2474<https://tools.ietf.org/html/rfc2474>]

      Preferred Behavior: Set the outgoing value to the incoming value,
      unless the server includes a differentiated services classifier
      and marker [RFC2474<https://tools.ietf.org/html/rfc2474>].  Note, the TCP connection can only use a
      single DSCP code point so inter flow differentiation is not
      possible, see Section 5.1 of [RFC7657]<https://tools.ietf.org/html/rfc7657#section-5.1>.


   Fragmentation



      Preferred Behavior: Any fragmented packets are reassembled in the

      server and then forwarded to the client over the TCP connection.

      ICMP messages resulting from the UDP datagrams sent to the peer

      MUST be forwarded to the client using TURN's mechanism for

      relevant ICMP types and codes.


   IPv4 Options

      Preferred Behavior: The outgoing packet is sent without any IPv4
      options.

</snip>

-Tiru

In addition, a mere note does not undo the implication of indicating each IP parameter (option, DF) separately as if there are always configurable per-TURN message.

Joe
_______________________________________________
Tsv-art mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/tsv-art