<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px;">
<div>
<p class="MsoNoSpacing" style="font-family: 'Times New Roman', serif; margin: 0in 0in 0.0001pt; font-size: 12pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Dear All,<o:p></o:p></span></p>
<p class="MsoNoSpacing" style="font-family: 'Times New Roman', serif; margin: 0in 0in 0.0001pt; font-size: 12pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></p>
<div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Please find the attendance of the call attached to this email and the MP3 recording below for the Next-Gen RDS PDP Working group call held on Tuesday, 06 September 2016 at 16:00 UTC.<o:p></o:p></span></p>
<p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; line-height: 15.6pt;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">MP3: </span><a href="http://audio.icann.org/gnso/gnso-nextgen-rds-06sep16-en.mp3
" style="font-family: -webkit-standard; font-size: 14px;">http://audio.icann.org/gnso/gnso-nextgen-rds-06sep16-en.mp3</a></p>
<a href="http://audio.icann.org/gnso/gnso-nextgen-rds-06sep16-en.mp3
"> <br>
</a></div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://gnso.icann.org/en/group-activities/calendar#nov" style="color: purple;">http://gnso.icann.org/en/group-activities/calendar</a><o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">** Please let me know if your name has been left off the list **<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Mailing list archives:<a href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/" style="color: purple;">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/</a><o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Wiki page: </span><a href="https://community.icann.org/x/JBmsAw" style="font-family: -webkit-standard; font-size: 14px;">https://community.icann.org/x/JBmsAw</a></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Thank you.<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">Kind regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt;"><font face="Calibri">Michelle DeSmyter </font></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span style="font-size: 11pt; font-family: Calibri, sans-serif;">-------------------------------<o:p></o:p></span></p>
</div>
<div style="font-family: -webkit-standard;">
<p class="MsoNoSpacing" style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<b><span style="font-size: 11pt; font-family: Calibri, sans-serif;">Adobe Connect chat transcript for Tuesday, 06 September 2016</span></b></p>
<div>Michelle DeSmyter:Dear All, Welcome to the Next-Gen RDS PDP WG Meeting on Tuesday, 06 September 2016 at 16:00 UTC.</div>
<div> Michelle DeSmyter:If you wish to speak during the call, please either dial into the audio bridge and give the operator the password RDS, OR click on the telephone icon at the top of the AC room to activate your mics. Please remember to mute your phone
and mics when not speaking.</div>
<div> Michelle DeSmyter:Agenda page: <a href="https://community.icann.org/x/JBmsAw">https://community.icann.org/x/JBmsAw</a></div>
<div> VAIBHAV AGGARWAL::-)</div>
<div> VAIBHAV AGGARWAL:10 & counting :-)</div>
<div> Chuck Gomes:Hello all.</div>
<div> VAIBHAV AGGARWAL::-)</div>
<div> Alex Deacon:Helllo all...</div>
<div> Greg Shatan:Hello all. I will need to leave at the bottom of the hour due to a conflicting ICANN-related meeting.</div>
<div> Ayden Férdeline:hi all</div>
<div> Michele Neylon:afternoon all</div>
<div> Maxim Alzoba (FAITID):Hi All</div>
<div> Volker Greimann:Purpose != what it is being used for</div>
<div> Volker Greimann:?</div>
<div> Greg Mounier 2:Having issues with audio...</div>
<div> steve metalitz:Who are members of the Board team?</div>
<div> Marika Konings:@ Steve - see <a href="https://features.icann.org/composition-and-scope-board-working-group-registration-data-directory-services-bwg-rds-0?language=ru">https://features.icann.org/composition-and-scope-board-working-group-registration-data-directory-services-bwg-rds-0?language=ru</a></div>
<div> Marika Konings:he Board hereby names the following Board members to serve on the BWG-RDS: Steve Crocker, Bruce Tonkin, Erika Mann, Rinalia Abdul Rahim, Markus Kummer, Cherine Chalaby, and Chris Disspain. The Board also names an ex-officio role on the
BWG-RDS for ICANN's CEO, however that role will not become operative until the next ICANN CEO takes office.</div>
<div> Volker Greimann:does not?</div>
<div> Volker Greimann:that's what I thought, Chuck, thanks for making that clear</div>
<div> Jim Galvin (Afilias):+1 chuck - a use today does not mean it that is the purpose of registration data going forward.</div>
<div> Lisa Phifer:sac055 link <a href="https://www.icann.org/en/system/files/files/sac-055-en.pdf">https://www.icann.org/en/system/files/files/sac-055-en.pdf</a></div>
<div> Volker Greimann:the definition of purpose is paramount to the legality of the collection of data</div>
<div> Jim Galvin (Afilias):+1 steve - an important point the SSAC report brings up is that if there are different purposes we should not constraing ourselves to a single method of access (currently the role that RDAP serves in "loose" conversation)</div>
<div> Maxim Alzoba (FAITID):it is just the tool, and it is hard to deny that people will use it in unimaginable ways ...</div>
<div> Kal Feher:that doesnt really read like a purpose to be honest. there arent any reasons in there. just statements of functions</div>
<div> Roger Carney:+1 Jim</div>
<div> Lisa Phifer:How specifically does registration data support ICANN's missuon t ensure the security and stability of the uniique identiier system?</div>
<div> Kal Feher:security of the internet is a goal. a purpose statement should give us the reason why certain things tangientially connect to that goal. this purpose does not tell me why RDS should exist</div>
<div> Lisa Phifer:+1 jim</div>
<div> Volker Greimann:give the statement again?</div>
<div> Volker Greimann:useful, maybe. Necessary, no!</div>
<div> Maxim Alzoba (FAITID):promotion is usually about marketing .. tech things might not intersect with that field</div>
<div> Greg Shatan:Is somebody someplace windy or on a train?</div>
<div> Jim Galvin (Afilias):@lisa - some short bullets: regarding stability: from the business side you need to know who to continue the relationship - this includes all kinds of things not just money, consider transfers.</div>
<div> Jim Galvin (Afilias):@lisa - regarding security - you need to know who if you want to track down malefactors</div>
<div> Greg Shatan:Maxim, promote is not being used in the "marketing" sense here. I believe this phrasing reflects a similar use in the Bylaws and/or Affirmation of Commitments.</div>
<div> Jim Galvin (Afilias):@lisa - all of this is entirely independent of the mechanism, viz RDAP, and expressly independent of who gets access and when (i.e., public access)</div>
<div> Michele Neylon:+1 Greg</div>
<div> Michele Neylon:on the "promote" bit anyway</div>
<div> Kal Feher:I'm disagreeing because that statement is not a purpose</div>
<div> Jim Galvin (Afilias):@kal - agree it is not a purpose, per se, but it is pretty close in my view</div>
<div> Klaus Stoll:Sorry, audio problems</div>
<div> Klaus Stoll:move on</div>
<div> Maxim Alzoba (FAITID):@Greg, I meant that it was not used in tech meaning , more about behavioural patterns of parties </div>
<div> Lisa Phifer:bulllets ere untended to describe how registratio data supported stated mission and purpose</div>
<div> Maxim Alzoba (FAITID):Could we add ? to the end?</div>
<div> Lisa Phifer:(as I reco;;ect the EWG discussion)</div>
<div> Kal Feher:@jim. actually I feel the whole statement is a long way from being a purpose. a prupose statement should be giving us reasons for the existance of this system. there's no link between this system and the goals</div>
<div> Jim Galvin (Afilias):@maxim - I agree with your point, as I think about it. privacy is a second order issue. with the purpose we can define what we need and then we have to overlay on top of that privacy concerns</div>
<div> Lisa Phifer:does anyone have an example of a well foormed statement of purpose that would be helpfuk to illustrate what this WG should aim for?</div>
<div> Jim Galvin (Afilias):@lisa - here's what I like to say</div>
<div> Jim Galvin (Afilias):@lisa - the purpose of registration data is to support the life cycle of a domain name.</div>
<div> Jim Galvin (Afilias):@lisa - everything else is a secondary purpose. :-)</div>
<div> Maxim Alzoba (FAITID):the last bullet itself is controversial</div>
<div> Maxim Alzoba (FAITID):which one is appropriate in which case?</div>
<div> Volker Greimann:not on phone line</div>
<div> Volker Greimann:sorry</div>
<div> Volker Greimann:aw enforcement can contact service provider directly.</div>
<div> Maxim Alzoba (FAITID):it is better to use"ensure ongoing effort to provide ..."</div>
<div> Volker Greimann:no need to put that information out there. similar to telephone lines or hosting services where there is no such database but law enforcement can do their job</div>
<div> Volker Greimann:can still do their job</div>
<div> steve metalitz:@Volker, not sure hos "contacting service provider" is inecessarily inconsistent with the final bullet. </div>
<div> steve metalitz:how.... necessarily... </div>
<div> Volker Greimann:we are talking about if that purpose is desirable. </div>
<div> Volker Greimann:I am not certain it is desirable, or even necessary for this purpose</div>
<div> Maxim Alzoba (FAITID):also they need more than RDS :)</div>
<div> Jim Galvin (Afilias):+1 chuck - the bullets are more requirements than a purpose</div>
<div> Jim Galvin (Afilias):to the extent they are requirements, the details are negotiable and thus may not be achievable</div>
<div> Maxim Alzoba (FAITID):vendors usually tend to evaluate via additional income instead of number of issues </div>
<div> Susan kawaguchi:@Michele name those registries</div>
<div> Chuck Gomes:Please remove your check marks and x's</div>
<div> Susan kawaguchi:there are very few that do not provide information</div>
<div> Alan Greenberg:@Michele, I will do my nonest best to say something so outrageous you will find it easy to disagree.</div>
<div> Sara Bockey:I believe .UK has a very narrow WHOIS published</div>
<div> Alan Greenberg:nonest=honest</div>
<div> VAIBHAV AGGARWAL:@Sara .UK puts the Onus on the Rgistrars</div>
<div> Volker Greimann:can LEAs use it? sure, is their use the purpose of it? no! is it a legitimate purpose for the collection in a legal sense? No!</div>
<div> Sara Bockey:Gotcha Vaibhav</div>
<div> Volker Greimann:VA: Actually, Nominet handles these directly.</div>
<div> Alan Greenberg:It seems rather masochistic for a registry to insis that they have to handle requests for information on a pure 1 by 1 basis.</div>
<div> VAIBHAV AGGARWAL::-)</div>
<div> Maxim Alzoba (FAITID):goals?</div>
<div> Nathalie Coupet:I believe hte purpose of an RDS depends on who you ask. Ebd-users might have a different take on this.</div>
<div> Michele Neylon:Sara - Nominet - IEDR - AFNIC all have quite limited whois</div>
<div> Nathalie Coupet:End-users</div>
<div> Michele Neylon:depending on how the registrant has classed themselves</div>
<div> Michele Neylon:in the case of .ie you'll often only get a name</div>
<div> Maxim Alzoba (FAITID):cctlds are free to do what they like ...for example .to ccTLD :)</div>
<div> Michele Neylon:so if it's patrick murphy good luck finding them :)</div>
<div> Michele Neylon:Obviously the registrar + registry have more data</div>
<div> VAIBHAV AGGARWAL:@Michele That is what I was just sharing with #Sara that Registries like Nominet have a Automated Feild Verfication System, use the eg. of .TEL and put the onus of the who is info on the Registrars</div>
<div> Maxim Alzoba (FAITID):also even RDS does not resolve issue when the legal company is hired to make registrstions and to provide additional services(so it is not regulated by p&P)</div>
<div> VAIBHAV AGGARWAL:so Incase the data is incomplete or not right then the regisrar is to be contacted</div>
<div> Michele Neylon:Vaibhav - their automated validation system doesn't work </div>
<div> Michele Neylon:it's horrendous</div>
<div> Benny Samuelsen / Nordreg AB:+1</div>
<div> Maxim Alzoba (FAITID):+1</div>
<div> Volker Greimann:remember: If we end up with a purpose statement that does not satisfy the requirements of data protection laws, we may end up with a situation where we build a system that is unworkable since it has a built-in conflict</div>
<div> Michele Neylon:my sales staff are currently working through several thousand *.uk registrations to manually validate them for nominet </div>
<div> Michele Neylon:and it's wrecking their heads (and my bottom line)</div>
<div> Michele Neylon:+1 Volker</div>
<div> Jim Galvin (Afilias):@chuck - I can take the proposal one step further too</div>
<div> Maxim Alzoba (FAITID):RDS reflects the lifecycle</div>
<div> Nathalie Coupet:Chuck, does that mean whois, whowas services and what else?</div>
<div> steve metalitz:could support jJim'as formulation as "a" purpose but not the sole purpose. It is necessary but not sufficient. </div>
<div> VAIBHAV AGGARWAL:@MN I agree </div>
<div> Greg Shatan:It all depends on what we mean by "the lifecycle of a domain name."</div>
<div> VAIBHAV AGGARWAL:but just to share the Purpose </div>
<div> steve metalitz:Jim's formulation </div>
<div> VAIBHAV AGGARWAL:I was about to loose two .Uk ones I saved :-)</div>
<div> Jim Galvin (Afilias):@greg - yes and hence my suggestion to take it one step further ....</div>
<div> Greg Shatan:It's an element but it lacks clarity and specificity.</div>
<div> Michele Neylon:Vaibhav - the argument we had with them was around "harm" ie. how many complaints had they got about domains associated with us</div>
<div> Michele Neylon:the total was ZERO</div>
<div> Kal Feher:to take it a little further Jim, the RDS supports the lifecycle by collecting relevent data for each lifecycle event. that data is defined by existing policies for those events. for example IRTP, renewals etc.</div>
<div> VAIBHAV AGGARWAL::-)</div>
<div> Jim Galvin (Afilias):@greg - I suspect that any purpose we could all agree too will be just vague enough to need a series of bullets to explain it.</div>
<div> Maxim Alzoba (FAITID):it is not handled, just reflected</div>
<div> Jim Galvin (Afilias):@kal - yes, we collect data based on policy for the events we agree are in the lifecycle</div>
<div> Greg Shatan:The little black book would be a failure as an RDS.</div>
<div> VAIBHAV AGGARWAL:@Susan not just that - If I want to have a FB verified Account / Page then My whois is verified too</div>
<div> VAIBHAV AGGARWAL:So Its Customer Facing too</div>
<div> Maxim Alzoba (FAITID):do we think that different expiry dates from registrars and registries are not going to survive RDAP profile stage ?</div>
<div> Susan kawaguchi:@ VA agree my example was just one of many uses</div>
<div> VAIBHAV AGGARWAL:@SK :-)</div>
<div> VAIBHAV AGGARWAL:Just the Importance from a Policy as well as the Business Case</div>
<div> Maxim Alzoba (FAITID):Directory will have issues with single instance and localisation issues</div>
<div> Maxim Alzoba (FAITID):latter is from legal side </div>
<div> Susan kawaguchi:I do! online information is critical</div>
<div> VAIBHAV AGGARWAL:I agree to RDDS</div>
<div> VAIBHAV AGGARWAL::-)</div>
<div> Susan kawaguchi:@Jim agree with the discussion disagree with your point that I can use anything other than verifying online in an emergency situation the status of my domain name. Lots of war stories to share</div>
<div> Volker Greimann:I for one would appreciate a fully thought out and 100% legal (no gray areas) system for a change</div>
<div> Kal Feher:@susan, not to be too pedantic, but the only check that matters with regards to your control of your domains is DNS. either your names are delegated to you or they arent. if you are using whois to answwer that question, you arent guaranteed
to get the correct answer</div>
<div> Maxim Alzoba (FAITID):@Volker, legal requirements viary from jurisdiction to jurisdiction , so it will require segmented tool </div>
<div> Volker Greimann:Susan: if there is only one mechanism to achieve something good, but using that mechanism has legal issues, that mechanism has a problem.</div>
<div> Volker Greimann:maybe a different mechanism must be developed</div>
<div> Michele Neylon:Kal - that's not true either. If I was hijacking your domain(s) I'd leave the DNS alone until the last minute</div>
<div> Nathalie Coupet:Won't IOT also require fast, bulk, daily Whois searches? </div>
<div> Michele Neylon:Nathalie - for what??</div>
<div> Volker Greimann:it is not our job to provide a service for every possible and useful use.</div>
<div> Kal Feher:@michele, if you hijacked the domain, I doubt you'd update whois first. there's no gain there</div>
<div> Michele Neylon:Kal - sorry, but most hijackers do .. </div>
<div> Nathalie Coupet:If devices are DDOSing your network, are faulty or any other type of technical pbs?</div>
<div> Michele Neylon:Nathalie - we look at the IPs not domains</div>
<div> Michele Neylon:Network = IP address </div>
<div> Michele Neylon:I don't really care about your domains</div>
<div> Michele Neylon:well I do, but not that much</div>
<div> Jim Galvin (Afilias):@susan - I do not dispute what works for you today. I believe we agree there needs to be discussion about whether to continue to support that use case going forward and, if so, what is the best mechanism for that (i.e., RDAP/WHOIS
may not be it).</div>
<div> Maxim Alzoba (FAITID):or we might leave some needs outside this time</div>
<div> Susan kawaguchi:@ Jim agree to the discussion but please do not discount other uses of the registration information because there may be another way we can do it. </div>
<div> Greg Shatan:@Jim, this is not jsut what works for Susan, it's what works for many many domain name owners/managers. And it's a critical use.</div>
<div> steve metalitz:"self-evident" may not be useful concept, depends on the self involved......</div>
<div> Kal Feher:@michele maybe. but at registries we tend to see quick dns hijacking for immediate gain. whois tends to be the long play and would be more applicable to dispute resolution processes.</div>
<div> Jim Galvin (Afilias):but then that means it's not self-evident. :-)</div>
<div> VAIBHAV AGGARWAL:Jim The WHOIS is the way for the time being till we dont do Brainstroming on the New System and till such time we should improve the Whois as I dont see the new system coming up that quickly anytime soon</div>
<div> VAIBHAV AGGARWAL:@Susan is right on the importance of the matter</div>
<div> Maxim Alzoba (FAITID):registry suports the lifecycle , I think RDS reflects the state of the domain</div>
<div> Greg Shatan:DNS is really a different set of records, useful for different (though probably overlapping) purposes..</div>
<div> Susan kawaguchi:@Kal I don't agree</div>
<div> Greg Shatan:If we're going to use a cramped definition of lifestyle, I can't support a statement that includes "lifecycle.."</div>
<div> VAIBHAV AGGARWAL:DNS cannot be Mixed with the RDS topic</div>
<div> Fabricio Vayra:thanks, all</div>
<div> Greg Shatan:lifestyle = lifecycle.</div>
<div> VAIBHAV AGGARWAL:it is a separate whole lot of it</div>
<div> Kal Feher:@greg. DNS is your name. everything else is stuff about your name</div>
<div> Sara Bockey:thanks all!</div>
<div> Susan kawaguchi:and very critical</div>
<div> Nathalie Coupet:thank you!</div>
<div> Greg Shatan:I know what DNS is, that's not the issue. But thanks.</div>
<div> Vlad Dinculescu:Thanks all.</div>
<div> Maxim Alzoba (FAITID):bye all</div>
<div> VAIBHAV AGGARWAL:Lets keep the entire Discussion focused and Simple</div>
<div> VAIBHAV AGGARWAL:From a perspective that we can make anything but will it be easy from the USer perspective </div>
<div> VAIBHAV AGGARWAL:so Users of the RDS is a Very Imotant Stake Holder</div>
<div> VAIBHAV AGGARWAL:hanks Guys</div>
<div> VAIBHAV AGGARWAL:Have a Good Rest week</div>
<div> VAIBHAV AGGARWAL::-)</div>
</div>
<div style="font-family: -webkit-standard;"><br>
</div>
</div>
</div>
</body>
</html>