IETF Logo Mail Archive

[dhcwg] regarding the relay agents, VPN Devices and broadcast bit

Vivek Dadu <vdadu@microsoft.com> Mon, 20 January 2014 13:54 UTC

Return-Path: <vdadu@microsoft.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A061A0166 for <dhcwg@ietfa.amsl.com>; Mon, 20 Jan 2014 05:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 XMACdVhZuYSq for <dhcwg@ietfa.amsl.com>; Mon, 20 Jan 2014 05:53:58 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id D4CD61A0162 for <dhcwg@ietf.org>; Mon, 20 Jan 2014 05:53:57 -0800 (PST)
Received: from BY2PR03CA033.namprd03.prod.outlook.com (10.242.234.154) by BY2PR03MB208.namprd03.prod.outlook.com (10.242.36.156) with Microsoft SMTP Server (TLS) id 15.0.847.13; Mon, 20 Jan 2014 13:53:50 +0000
Received: from BN1BFFO11FD023.protection.gbl (2a01:111:f400:7c10::1:143) by BY2PR03CA033.outlook.office365.com (2a01:111:e400:2c2c::26) with Microsoft SMTP Server (TLS) id 15.0.847.13 via Frontend Transport; Mon, 20 Jan 2014 13:53:50 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1BFFO11FD023.mail.protection.outlook.com (10.58.144.86) with Microsoft SMTP Server (TLS) id 15.0.847.12 via Frontend Transport; Mon, 20 Jan 2014 13:53:50 +0000
Received: from SINEX14HUBC502.southpacific.corp.microsoft.com (157.60.220.61) by TK5EX14HUBC105.redmond.corp.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.3.174.2; Mon, 20 Jan 2014 13:53:10 +0000
Received: from SINEX14MBXC417.southpacific.corp.microsoft.com ([169.254.1.13]) by SINEX14HUBC502.southpacific.corp.microsoft.com ([fe80::df3:7769:8d99:21e5%13]) with mapi id 14.03.0174.002; Mon, 20 Jan 2014 13:53:08 +0000
From: Vivek Dadu <vdadu@microsoft.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: regarding the relay agents, VPN Devices and broadcast bit
Thread-Index: Ac8V5S6N2v3d0hNeTH6fzFDmG+SRRw==
Date: Mon, 20 Jan 2014 13:53:07 +0000
Message-ID: <2D833948ADBB574BAB0A4AD8CF32A8991B488FBD@SINEX14MBXC417.southpacific.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.3.94]
Content-Type: multipart/alternative; boundary="_000_2D833948ADBB574BAB0A4AD8CF32A8991B488FBDSINEX14MBXC417s_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(53754006)(199002)(189002)(33656001)(16236675002)(59766001)(69226001)(74502001)(92566001)(81342001)(74366001)(49866001)(55846006)(77982001)(51856001)(46102001)(65816001)(76482001)(80022001)(86362001)(54356001)(63696002)(81816001)(71186001)(15202345003)(93136001)(80976001)(74662001)(93516002)(81686001)(15975445006)(31966008)(20776003)(16796002)(74706001)(87266001)(74876001)(47736001)(53806001)(85306002)(76176001)(87936001)(85806002)(83322001)(2656002)(84326002)(56816005)(90146001)(19580395003)(85852003)(6806004)(54316002)(44976005)(83072002)(50986001)(92726001)(47976001)(4396001)(47446002)(81542001)(76796001)(19300405004)(76786001)(512954002)(79102001)(56776001)(77096001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR03MB208; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 00979FCB3A
X-OriginatorOrg: microsoft.com
X-Mailman-Approved-At: Mon, 20 Jan 2014 05:59:05 -0800
Subject: [dhcwg] regarding the relay agents, VPN Devices and broadcast bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 13:54:01 -0000

Hi All
I have a query regarding a scenario concerning option 118. Here it goes

"Say a VPN device acting as a dhcp proxy on behalf of its VPN clients has an ip address 10.0.0.2 and belongs to subnet 10.0.0.0/24, however it wants to assign the ip address belonging to subnet 172.1.1.0/24 to one of its VPN clients, so it sends the subnet selection option 118 filled with the data 172.1.1.0 and subnet mask filled with data 255.255.255.0 as a result a relay agent receives it and forwards to dhcpserver, the dhcp server unicasts the packet to the relay agent, now will the relay agent need a special setting to tell it that packets destined to 172.1.1.0/24 subnet will be sent on 10.0.0.0/24 interface"
Also would like to know that will the broadcast bit on packet based on which the server decides to broadcast or unicast a response packet have any impact on the way relay agent processes the packet.

Regards
Vivek

v2.23.0 | Report a Bug | By Email