[sipcore] 4244bis-05: Multiple forks from the UA

"Worley, Dale R (Dale)" <dworley@avaya.com> Wed, 22 June 2011 20:53 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4BA7121F85AA for <sipcore@ietfa.amsl.com>; Wed, 22 Jun 2011 13:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.425
X-Spam-Status: No, score=-103.425 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MCOd+-xnEJbq for <sipcore@ietfa.amsl.com>; Wed, 22 Jun 2011 13:53:02 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com []) by ietfa.amsl.com (Postfix) with ESMTP id 78D7821F8583 for <sipcore@ietf.org>; Wed, 22 Jun 2011 13:53:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsGABZVAk6HCzI1/2dsb2JhbABTpxFwB6okg2wCm2OGLQSWbIsm
X-IronPort-AV: E=Sophos;i="4.65,407,1304308800"; d="scan'208";a="252826201"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([]) by de307622-de-outbound.net.avaya.com with ESMTP; 22 Jun 2011 16:53:00 -0400
X-IronPort-AV: E=Sophos;i="4.65,407,1304308800"; d="scan'208";a="669025165"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Jun 2011 16:53:00 -0400
Received: from DC-US1MBEX4.global.avaya.com ([]) by DC-US1HCEX3.global.avaya.com ([]) with mapi; Wed, 22 Jun 2011 16:52:59 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Wed, 22 Jun 2011 16:52:59 -0400
Thread-Topic: 4244bis-05: Multiple forks from the UA
Thread-Index: AQHMMR5e3kUkvCmI9kWt/lfYmZTAIg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F56DF@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sipcore] 4244bis-05: Multiple forks from the UA
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2011 20:53:03 -0000

In regard to the "root" of the History-Info tree, as the draft is written, we are already
requiring the possibility of H-I entries with indexes "2", "3", etc., that is, siblings of
the entry "1" that the phone creates.

How?  The phone may receive a 3xx response to its first request.  Per the rules
of the draft, the new requests generated due to a 3xx response to request "1"
are siblings of request "1", and so are numbered "2", "3", etc.

One consequence of this is that if we consider the H-I entries as nodes in a
tree, we have to allow that the root of the tree is *not* represented by an H-I entry,
and that the H-I entries with single integer index-vals are children of the root.

Another consequence is that this technical problem is solved:

    [Also need to take care of the case where the UAC generates several
    requests as forks of a theoretical ancestral request, as is used in
    draft-ietf-bliss-call-completion.  It seems like they should have
    index=1, index=2, index=3, etc.]

Since entries "1", "2", "3", etc. can be generated by normal redirection, H-I processing
software should not get confused when a UA generates more than one initial fork.