RE: Header Insertion and TI-FA
"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Tue, 12 May 2020 15:26 UTC
Return-Path: <pcamaril@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F327B3A0B96 for <ipv6@ietfa.amsl.com>; Tue, 12 May 2020 08:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level:
X-Spam-Status: No, score=-9.596 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=V7N84th5; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=zD0SXVPB
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UftzFf3cz9Yc for <ipv6@ietfa.amsl.com>; Tue, 12 May 2020 08:26:31 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C24E3A0B81 for <6man@ietf.org>; Tue, 12 May 2020 08:26:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=24614; q=dns/txt; s=iport; t=1589297181; x=1590506781; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vc7CZJWtafDF5zlhpORyGZZ8ofDCKxlhUya4vCmZkts=; b=V7N84th54Nr0+lGDwUvs0GDRnlAfxVqTxUWH5fHywGscVKU/mHGTqdag 93dQLg08de0gc5d0YP2YU1l5i6V8sjeTsqZxwF57n4SQm7DxsNhDzy71s eIwaFBcGLEs/PXNJDeCyF/TPuKLiwkETT2adtdy+dYTNKg0/OMP4ZM0td M=;
IronPort-PHdr: 9a23:aqH41ROMNWneAPZWW4ol6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvK433lvIRJja5+5Jj+fdtKWmUmsFst6Ns3EHJZpLURJNycAbhBcpD8PND0rnZOXrYCo3EIUnNhdl8ni3PFITFJP4YFvf8Xmz9CMTFgnyMQd+IeGzEYnX3Iy70umo8MjVZANFzDO2fbJ1KkCwqgPc06tegYZrJqsrjBXTpX4dcOVNzmQuLlWWzBs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BdAQDXvrpe/4QNJK1jAxwBAQEBAQEHAQESAQEEBAEBQIE2BAEBCwGBJC8kLQVvWC8sCodgA41EiXqOPYFCgRADVAsBAQEMAQEYAQwIAgQBAYREAoIFJDcGDgIDAQELAQEFAQEBAgEFBG2FVgyFcQEBAQEBAQEBARAbEwEBLAsBBAkCAgEIEQMBAQEBFQsHBxsGBgsUCQgCBA4FCBIIgwWBfk0DDiABDqUBAoE5iGF0gTSDAQEBBYEyAYN+DQuCDgkFgTMBgmKJYRqBQT+BEAFDgU9+PoIeSQEBAQEBgRsSARIBHgUECAwGAQUHCQkIgwCCLY44EiENBYhzim+PRkoKgkqDXYQ+izuEb4JciGeFAYx2mXeCR5EJAgQCBAUCDgEBBYFoI2ZwcBU7gmkJRxgNkEAJGoNPM4RhhUJ0AgEELQMCBggBAQMJfItTgSQBMEgXAQE
X-IronPort-AV: E=Sophos;i="5.73,384,1583193600"; d="scan'208,217";a="504919837"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 May 2020 15:26:20 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 04CFQKJZ020669 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 May 2020 15:26:20 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 May 2020 10:26:20 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 May 2020 10:26:19 -0500
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 12 May 2020 11:26:19 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WG4kJOKVj81TDkhKGzylRX0dw8Ej7ZVm6sXFx+xIuQSdnTA4XlQWFODlk+7ZKXYMK1tasqLFOcLgqaW4GFoYl+5PzsV3gmQ8+buZjP8rlGriHAxYO2ofZC7C9d5rk0eLGuDcn+DnRUtRlDUz9W3DSNGkVk6qXhFvOrSnhs9mnrvs5yutLdMzsEGj/OqASIf1FoML1GtlmXpfDCH8re0y9MWjRJEr2H0qR4oeXraw5MbLpf4C+2yrvubbFiLJDOgRb6HA51FcW5ZQzqRLFaDUQS+0aSycR7/RWM2wj1h9L6YfC1hLHxDF2zx0EhyVHhmNGfkSizvRwqoqlUm1nJkgDw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Y53cnxWETdnqarZpURoDRwWS1RpY6YEaixPwM5R+sXY=; b=FAHVSk0mR1ugxqRbq4iCfL1T97xZtw0JlXa3BFvQbV675xBAHN+jOSMewZKOBS9wAgWBkYCoHnL9mJYmMB9qSOgTks9dabwW0ZtCcuGNIL1iflWiJaKoTR9u9vIYUjDAk1Tgo4OGNSO8dTbLyL/MVMOUDZ6zUO76s029hWfALwwaEZfx1qLuehYZRF72RNGF0rGx8SnvG76CMVxmJLgpmG2Tvz+xwv9xqtFup1MToTkQQKKNgp1n9oImNXBWN1mdGqH5vPZeskpo2i0Mk1nDOvWx5PeJNOzH1SbEV+H5qw88hrZ6cuN8AAlooaUG/aDXukrPBXHR43NRWDzTocPPeA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Y53cnxWETdnqarZpURoDRwWS1RpY6YEaixPwM5R+sXY=; b=zD0SXVPBImoB9evizyvZDptxhuBoaqbe/DUOx+K1h1ne2nMkvlaFRdzgYL+Hdg8v8A+La+BNhF//paiOCJYeuBFYe/4otrWYPPVRHm60NMmLXyAsfIDOWVO1cE6k8XE3usdaagEJ+FK5mSqhieNvmss6vywn43uB2pBlf6UWKak=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (2603:10b6:300:24::8) by MWHPR11MB2064.namprd11.prod.outlook.com (2603:10b6:300:27::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2979.26; Tue, 12 May 2020 15:26:18 +0000
Received: from MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::3919:ef10:f837:9efc]) by MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::3919:ef10:f837:9efc%9]) with mapi id 15.20.3000.016; Tue, 12 May 2020 15:26:18 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: Andrew Alston <Andrew.Alston@liquidtelecom.com>
CC: "6man@ietf.org" <6man@ietf.org>, Gyan Mishra <hayabusagsm@gmail.com>
Subject: RE: Header Insertion and TI-FA
Thread-Topic: Header Insertion and TI-FA
Thread-Index: AdYnknQqAO/1C9hyQECELexezObcNgABpa0AAAEH7OAAAS7FgAAA/LmAAAHloQAAAbTu8AANELAAAB0jw6A=
Date: Tue, 12 May 2020 15:26:01 +0000
Deferred-Delivery: Tue, 12 May 2020 15:25:00 +0000
Message-ID: <MWHPR11MB137441AE7513EAA1894EDB9FC9BE0@MWHPR11MB1374.namprd11.prod.outlook.com>
References: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV3-dMPg6SAAEz+uWre-rj6j5=1JgyyQyKyz_qn7f7mJwQ@mail.gmail.com> <DM6PR05MB634848D379A428372C166DD4AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMEBVA+yK9cFXSe=GVUeH01ipi++nwCRQU_nQCxsKhyvRg@mail.gmail.com> <1B1A2C98-20F0-43F8-A299-C839D14A245C@gmail.com> <CABNhwV3m+2+Wt2CHRRhznEvTZ5KQdounv0e=icfbs4VOcoU0Rw@mail.gmail.com> <MWHPR11MB13740F8547CF700EC38CE4F5C9A10@MWHPR11MB1374.namprd11.prod.outlook.com> <61DBEBF4-ACE7-40D6-B172-EF46B35BC838@liquidtelecom.com>
In-Reply-To: <61DBEBF4-ACE7-40D6-B172-EF46B35BC838@liquidtelecom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: liquidtelecom.com; dkim=none (message not signed) header.d=none;liquidtelecom.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.220.40]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e960fd20-34e4-42fe-151d-08d7f688d146
x-ms-traffictypediagnostic: MWHPR11MB2064:
x-microsoft-antispam-prvs: <MWHPR11MB2064063B65CFAAEEA8F9D33BC9BE0@MWHPR11MB2064.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0401647B7F
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Do6LDqzioajs0SR+RsHDvwR233v/DhQkNmCWtRLLZ16JDVQimRl+bmaKqZdkwKzP9IdHOs25q4bnfv7qo1rQHaNJncwR7IjbhPtq+eoLAfMI06zBBiagpvKSj82OeeCyf28UZyyzuEsVLiizHtuzCw5dGcGAFuHZTxD+Fgfl1xzbmgctNQddw3rE8bd0KVhjRJB35HsgK4NvXYv2kyQqQjht4FuAqvSpxLs3li5pOg4OU9Puy4Z/t1oOzqEO3QSvzOpPcWWZj56rI07LyHmOJvejpG9mfuv32a83KFm1nJgR2Obu1KHxcYBUpQf93H7vQWMf836pfhxTyLfUPmRt8fUvuLoEwBfy+361ZccvhAzNy4RoXMhdswp/+ne2XJj0orPUuI0vCoVuW+at/5jGtt7fov483kSrZBWQ+w31Tg4UECbTe9uTSPc/2w6ZOaJ09aptBLsFmAPUu3Iu6us/ibyoW4wsVPlft99KcBof/7rr3lz34dZ7vAtAnb0DtTYMM26TsJf7UnkAzAk6yrJ7I6fELJITy/0QKxJa8yG9P7Bgiv+2SPL//r5uJqyQYgKZfOSnsPc6zaiMNcptvYXAONW7lKGTXgeeaScU+pX0hro=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MWHPR11MB1374.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(376002)(39860400002)(136003)(396003)(366004)(33430700001)(166002)(53546011)(54906003)(7696005)(52536014)(316002)(6506007)(33440700001)(83080400001)(33656002)(26005)(4326008)(6916009)(71200400001)(6666004)(5660300002)(966005)(66946007)(66556008)(86362001)(9686003)(55016002)(186003)(76116006)(64756008)(66476007)(66446008)(478600001)(8676002)(2906002)(8936002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: XX+x+bI6/xHRXDmq/d6n8QEWllSWOzK8RqlpqIkG0K4zUyWGx7DUkk5nbhQNRXNKK0KzEY+hiJ9bs8wRlAmyei+W90O5VIlJ6zCHchUtV0ILcgloWz7cFZZIGn5yt496oAm+NjUJZBwJM1+UEKAMeK36zC8756cgIkRN0sYcT6Ooh8Q1S9CIJlk0eLbjQCvAkGr8k1t0+5V1zwXSvQfbLyD53HA/hYRpSzS5C7R2vyjRFFAeYF1e99PuzIXQujxAhxkcTYb90sFLa4IWZ6raB51bWeWMlVHfhdH1pi+uUIv6ztCsIKcEkbCiX5/NxXfYuj+ZjG3RQ2DeJYOasF+obCELz3kbyc7FRsvEv8gF5rg0/uzDLc0SBBePjmmpKbTGm75HjHWaXdAvT0x4DM1FG7QicgQZOixWiKS3coMWggq4cqlOBUXeldsm6zMGyHdxvMn28XmKHro5dqjt6MpmpAapL8OO4Qv4fl6MswiYDvI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR11MB137441AE7513EAA1894EDB9FC9BE0MWHPR11MB1374namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: e960fd20-34e4-42fe-151d-08d7f688d146
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 May 2020 15:26:18.2141 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eZO7OZJGPOInznMOpYSfDbyDVbyyeckjar4A5SsjwVX65yXhQ2sK7PL7tvsDVNiIgGpY8EsESHc7VGd9BVStiQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB2064
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rhyXUs6uihXji80M7qEEqdn-DPE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 15:26:38 -0000
Hi Andrew, Cisco has demonstrated TILFA with SRH insertion at EANTC-2019. http://www.eantc.de/fileadmin/eantc/downloads/News/2019/EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf This feature is available to all customers -supported since XR 6.6.1-. Please contact your Cisco account team if you want further details on cisco products or need assistance. Thank you, Pablo. From: Andrew Alston <Andrew.Alston@liquidtelecom.com> Sent: lunes, 11 de mayo de 2020 22:04 To: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>; Gyan Mishra <hayabusagsm@gmail.com> Cc: 6man@ietf.org Subject: Re: Header Insertion and TI-FA Hi Pablo, While I fully realize that running code is not mandatory in the IETF - there have been numerous assertions about what is harmful and not harmful etc, and coupled with the deployment draft, I presume there is running code from the perspective of the authors. Would you be prepared to disclose the release of code where SRH and this functionality is actually implemented - since I'd like to run a series of verification tests against it to test the effects on my network and I'm sure others would be interested in doing the same. I can also then test against the Juniper implementation as tested at the EANTC and run my own inter-op tests and test the real effects this has on the network in a manner that makes sense. Obviously however testing against a single vendor code is not ideal - and since the assertions are being made and in light of the deployment draft - I am figuring that you must actually have running code that is in the field? (I know on all code versions I have tested that are GA I have yet to see any SRH on any packet capture that I have done - hence I have been unable to do any verification testing myself against the claims made) Thanks Andrew From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> on behalf of "Pablo Camarillo (pcamaril)" <pcamaril=40cisco.com@dmarc.ietf.org<mailto:pcamaril=40cisco.com@dmarc.ietf.org>> Date: Monday, 11 May 2020 at 20:13 To: Gyan Mishra <hayabusagsm@gmail.com<mailto:hayabusagsm@gmail.com>> Cc: "6man@ietf.org<mailto:6man@ietf.org>" <6man@ietf.org<mailto:6man@ietf.org>> Subject: RE: Header Insertion and TI-FA Gyan, SRH insertion is NOT part of draft-ietf-spring-srv6-network-programming-15. (SRH insertion is documented in draft-filsfils-spring-srv6-net-pgm-insertion-02 with a normative reference to draft-voyer-6man-extension-header-insertion-08). > Spring - Please provide section within PGM that has the verbiage of the 6in6 encapsulation This is already in the net-pgm draft (since rev 00). Please see https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-15#section-5 . Thanks, Pablo. From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> On Behalf Of Gyan Mishra Sent: lunes, 11 de mayo de 2020 18:02 To: Krzysztof Szarkowicz <kszarkowicz@gmail.com<mailto:kszarkowicz@gmail.com>> Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>>; 6man <6man@ietf.org<mailto:6man@ietf.org>> Subject: Re: Header Insertion and TI-FA Krzysztof So you agree with what I stated as the workaround. Please read through exactly what I stated as the complete workaround. If we are all in agreement with the prepend (6in6) encap) workaround can we have the PGM draft updated to reflect. All With regards to the 6MAN appeal, the issues were PSP and this issue with TI-LFA from what I recall. Was their any other issue outside of these two mentioned in the appeal that we need to address and come up with a workaround? Thank you Gyan On Mon, May 11, 2020 at 11:09 AM Krzysztof Szarkowicz <kszarkowicz@gmail.com<mailto:kszarkowicz@gmail.com>> wrote: Hi Robert, If we have prepend, why bother with insertion at all? Prepend (6in6 encap) is much cleaner, IMHO. Regards, Krzysztof > On 2020 -May-11, at 16:38, Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>> wrote: > > Hi Ron, > > > normalizing header insertion for the special case where the PLR is a segment endpoint > > When an operator is serious about good data plane protection with TI-LFA all nodes in the network will be enabled for SR. The less overhead required for the protection the better. You may just not have a room for adding additional 40 bytes to each packet at each potential PLR without fragmentation. > > Regarding all of your other TI-LFA related questions - I am sure Krzysztof will be happy to answer them for you internally :) After all this is what your public demo was all about .... > > Best, > Robert, > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org<mailto:ipv6@ietf.org> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.org> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 -------------------------------------------------------------------- -- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>
- Header Insertion and TI-FA Ron Bonica
- Re: Header Insertion and TI-FA Gyan Mishra
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Header Insertion and TI-FA Ron Bonica
- Re: Header Insertion and TI-FA Robert Raszuk
- Other use cases for header insertion (was Re: Hea… Tom Herbert
- Re: Header Insertion and TI-FA Tom Herbert
- Re: Header Insertion and TI-FA Krzysztof Szarkowicz
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Other use cases for header insertion (was Re:… Brian E Carpenter
- Re: Other use cases for header insertion (was Re:… Mark Smith
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Header Insertion and TI-FA Gyan Mishra
- Re: Header Insertion and TI-FA Mark Smith
- Re: Other use cases for header insertion (was Re:… Nick Hilliard
- Re: Other use cases for header insertion (was Re:… Tom Herbert
- Re: Header Insertion and TI-FA Andrew Alston
- Re: Header Insertion and TI-FA Gyan Mishra
- RE: Other use cases for header insertion (was Re:… Ron Bonica
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- RE: Header Insertion and TI-FA Pablo Camarillo (pcamaril)
- RE: Header Insertion and TI-FA Andrew Alston
- Re: Other use cases for header insertion (was Re:… Toerless Eckert
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Brian E Carpenter
- Re: Header Insertion and TI-FA Brian E Carpenter
- Re: Other use cases for header insertion (was Re:… Mark Smith
- Re: Header Insertion and TI-FA Mark Smith
- Re: Header Insertion and TI-FA Robert Raszuk
- Re: Other use cases for header insertion (was Re:… S Moonesamy
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- Re: Other use cases for header insertion (was Re:… Robert Raszuk
- Re: Other use cases for header insertion (was Re:… Stewart Bryant
- Re: Other use cases for header insertion (was Re:… Tom Herbert
- Re: Other use cases for header insertion (was Re:… Uma Chunduri
- Re: Other use cases for header insertion (was Re:… Fernando Gont
- Re: Other use cases for header insertion (was Re:… Uma Chunduri
- Re: Other use cases for header insertion (was Re:… Fernando Gont