[MMUSIC] Comments to draft-ietf-mmusic-media-path-middleboxes

Ivo Sedlacek <ivo.sedlacek@ericsson.com> Thu, 30 May 2013 14:11 UTC

Return-Path: <prvs=0862b76666=ivo.sedlacek@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117A121F84D8 for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 07:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level:
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G7o4J-E9XGSY for <mmusic@ietfa.amsl.com>; Thu, 30 May 2013 07:11:38 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0742421F871C for <mmusic@ietf.org>; Thu, 30 May 2013 07:11:29 -0700 (PDT)
X-AuditID: c1b4fb30-b7f9e6d000002643-f9-51a75e10144e
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 26.5F.09795.01E57A15; Thu, 30 May 2013 16:11:29 +0200 (CEST)
Received: from ESESSMB301.ericsson.se ([169.254.1.55]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.02.0328.009; Thu, 30 May 2013 16:11:28 +0200
From: Ivo Sedlacek <ivo.sedlacek@ericsson.com>
To: "Hannes.Tschofenig@gmx.net" <Hannes.Tschofenig@gmx.net>, "obsidian97@gmail.com" <obsidian97@gmail.com>, "gsalguei@cisco.com" <gsalguei@cisco.com>
Thread-Topic: Comments to draft-ietf-mmusic-media-path-middleboxes
Thread-Index: Ac5dP2U9MUhBukL4S/y9NZuXA5zr2Q==
Date: Thu, 30 May 2013 14:11:27 +0000
Message-ID: <39B5E4D390E9BD4890E2B310790061010D72D7@ESESSMB301.ericsson.se>
Accept-Language: en-US, cs-CZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_39B5E4D390E9BD4890E2B310790061010D72D7ESESSMB301ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyM+Jvra5g3PJAg9lLOSzmTvGzWLrzHqvF 1OWPWSyWzXnE7MDiMeX3RlaPnbPusnss3rSfzWPJkp9MASxR3DZJiSVlwZnpefp2CdwZx3fy FazvZ6poutnI0sC4+iNjFyMHh4SAicTzXTZdjJxAppjEhXvr2boYuTiEBA4zSiz5vYUdwlnM KPH36gV2kCo2AT2JiVuOsIIkRARmMkpsvbGZCWQSs4C6xNXFQSA1wgK2Ej0TO9hAbBEBJ4mv 1z4wQdh6EndausDmsAioSmzfNJcVxOYV8Jb4uGcDM4jNKCArcfVPLyOIzSwgLnHryXwmiOsE JJbsOc8MYYtKvHz8jxXCVpT4+GofVH2+xKmdTcwQMwUlTs58wjKBUXgWklGzkJTNQlIGEdeR WLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGy5yZm5qSXm29iBEbTwS2/DXYwbrovdohRmoNF SZxXn3dxoJBAemJJanZqakFqUXxRaU5q8SFGJg5OEMEl1cB4sutZzuxJEt8P5ZydrMj/eVJd uNjxC7O2uwVf+R8RLHRig0TGaTk3k4fFe3f+t73589fBl/+vbmRnEfRuMXt7Q0pE1kX+nM6r 6b9V/iZedFrd8SiyKGrBxUhLk4XZGTaenefXTjzbGtz6TDRtnoqfTrhzenTMFvEmyQ3dny58 8Prc2X0v/fk1JZbijERDLeai4kQA2lC7pHkCAAA=
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: [MMUSIC] Comments to draft-ietf-mmusic-media-path-middleboxes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 14:11:43 -0000

Hello,

Comments to draft-ietf-mmusic-media-path-middleboxes-06:

Comment 1:

ISSUE:

http://tools.ietf.org/html/draft-ietf-mmusic-media-path-middleboxes-06 states:
-------------------

3.  Architecture



   Figure 1 shows the architecture that is being considered in this

   document with respect to firewall and NAT traversal using media

   relaying.  The timing and directionality with which media packets are

   allowed to traverse a particular edge device is the subject of this

   investigation.  The MIDCOM agent thereby pushes policy rules to the

   middlebox that allow or deny certain flows to >>bypass<<.  Additionally,

   in case of media relaying it is important for the MIDCOM agent to

   adjust the signaling messages.





                     SIP     +-----------------+     SIP

         +-----+  Signaling  |     SIP ALG     |  Signaling  +-----+

         | UAC |<----------->+-----------------+<----------->| UAS |

         +-----+             |   MIDCOM Agent  |             +-----+

            ^                +-----------------+                ^

            |                         ^                         |

            |          Policy rule(s) | and NAT bindings        |

            |                         v                         |

            |      Media       +-------------+       Media      |

            +----------------->|  Middlebox  |<-----------------+

                               +-------------+



                Figure 1: Analysed Firewalling Architecture



   The aspects of packet filtering are described in Section 4 whereas

   NAT traversal is illustrated in Section 5.
-------------------

The word "bypass" does not seem to be correct.

"bypass" is defined by http://dictionary.cambridge.org/ as: "to avoid something by going around it" or " to ignore a rule or official authority".

However, the figure 1 shows media of the flows passing through/via the middlebox, not around the middlebox.


PROPOSAL:
-------------------

3.  Architecture



   Figure 1 shows the architecture that is being considered in this

   document with respect to firewall and NAT traversal using media

   relaying.  The timing and directionality with which media packets are

   allowed to traverse a particular edge device is the subject of this

   investigation.  The MIDCOM agent thereby pushes policy rules to the

   middlebox that allow or deny certain flows to >>pass through<<.  Additionally,

   in case of media relaying it is important for the MIDCOM agent to

   adjust the signaling messages.





                     SIP     +-----------------+     SIP

         +-----+  Signaling  |     SIP ALG     |  Signaling  +-----+

         | UAC |<----------->+-----------------+<----------->| UAS |

         +-----+             |   MIDCOM Agent  |             +-----+

            ^                +-----------------+                ^

            |                         ^                         |

            |          Policy rule(s) | and NAT bindings        |

            |                         v                         |

            |      Media       +-------------+       Media      |

            +----------------->|  Middlebox  |<-----------------+

                               +-------------+



                Figure 1: Analysed Firewalling Architecture



   The aspects of packet filtering are described in Section 4 whereas

   NAT traversal is illustrated in Section 5.
-------------------

Comment 2:

ISSUE:

http://tools.ietf.org/html/draft-ietf-mmusic-media-path-middleboxes-06 states:
-------------------
   REC #4:  If signaling on the media path is required before media can
      flow, the >>answer<< should send the SDP answer as soon as possible,
      for example within a provisional SIP response, to allow the media
      path signaling to bypass middleboxes and therefore to avoid
      clipping.
-------------------
I believe there is an error.

PROPOSAL:
-------------------
   REC #4:  If signaling on the media path is required before media can
      flow, the >>answerer<< should send the SDP answer as soon as possible,
      for example within a provisional SIP response, to allow the media
      path signaling to bypass middleboxes and therefore to avoid
      clipping.
-------------------

Comment 3:

ISSUE:

http://tools.ietf.org/html/draft-ietf-mmusic-media-path-middleboxes-06 states:
-------------------
   REC #4:  If signaling on the media path is required before media can
      flow, the answer should send the SDP answer as soon as possible,
      for example within a provisional SIP response, to allow the media
      path signaling to >>bypass<< middleboxes and therefore to avoid
      clipping.
-------------------
Same issue as in Comment 1.

PROPOSAL:
-------------------
   REC #4:  If signaling on the media path is required before media can
      flow, the answer should send the SDP answer as soon as possible,
      for example within a provisional SIP response, to allow the media
      path signaling to >>pass through<< middleboxes and therefore to avoid
      clipping.
-------------------


Kind regards

Ivo Sedlacek

Ericsson
Mobile +420 608 234 709
ivo.sedlacek@ericsson.com<mailto:ivo.sedlacek@ericsson.com>
www.ericsson.com<http://www.ericsson.com>

This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>