RE: Comments on request-routing from IESG
"jayasurya venugopalan" <[email protected]> Fri, 31 Jan 2003 04:27:13 +0530
| Newsgroups | gmane.ietf.cdi |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPartTM-000-38ef6928-347a-11d7-ba7f-006067005148 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C8B2.ED730EA4" ------_=_NextPart_001_01C2C8B2.ED730EA4 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, I feel the issue of session persistence needs to be addressed in more = detail especially in the light of multiple sessions across different = shopping sites all linked up with a common discount or incentive factor. =20 Distributed session persitence management is not out of context I feel = in the current scenario where even in a country like India things are = ever rapidly becoming Net Transaction enabled. Rgds jayasurya -----Original Message----- From: Abbie Barbir [mailto:[email protected]] Sent: Fri 1/31/2003 2:36 AM To: Mark Day; [email protected] Cc:=09 Subject: RE: Comments on request-routing from IESG Hi, No problem, we will address the issues. abbie > -----Original Message----- > From: Mark Day [mailto:[email protected]]=20 > Sent: Thursday, January 30, 2003 3:41 PM > To: [email protected] > Subject: Comments on request-routing from IESG >=20 >=20 > Apparently we have some feedback on the request-routing draft=20 > as of 1/15. I didn't know about it until I went looking for=20 > the current state of our drafts. >=20 > You can see the comments at=20 > https://datatracker.ietf.org/public/pidtracker> .cgi > Put in=20 > "CDI" for WG acronym and hit "Search". Then hit=20 > the "DETAIL" button for the known-request-routing draft. >=20 > Abbie (and other interested parties), can you take a look at=20 > what's there and see what we need to do to fix the identified=20 > problems? >=20 > Thanks, >=20 > --Mark >=20 >=20 >=20 ------_=_NextPart_001_01C2C8B2.ED730EA4 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3DWindows-1252"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.0.6249.1"> <TITLE>RE: Comments on request-routing from IESG</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT SIZE=3D2>Hi,<BR> I feel the issue of session persistence needs to be addressed in = more detail especially in the light of multiple sessions across = different shopping sites all linked up with a common discount or = incentive factor.<BR> <BR> Distributed session persitence management is not out of context I feel = in the current scenario where even in a country like India things are = ever rapidly becoming Net Transaction enabled.<BR> <BR> Rgds<BR> jayasurya<BR> <BR> <BR> -----Original Message-----<BR> From: Abbie Barbir [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]= m</A>]<BR> Sent: Fri 1/31/2003 2:36 AM<BR> To: Mark Day; [email protected]<BR> Cc: <BR> Subject: RE: Comments on = request-routing from IESG<BR> <BR> <BR> Hi,<BR> <BR> No problem,<BR> <BR> we will address the issues.<BR> <BR> abbie<BR> <BR> > -----Original Message-----<BR> > From: Mark Day [<A = HREF=3D"mailto:[email protected]">mailto:[email protected]</A>]<BR> > Sent: Thursday, January 30, 2003 3:41 PM<BR> > To: [email protected]<BR> > Subject: Comments on request-routing from IESG<BR> ><BR> ><BR> > Apparently we have some feedback on the request-routing draft<BR> > as of 1/15. I didn't know about it until I went looking = for<BR> > the current state of our drafts.<BR> ><BR> > You can see the comments at<BR> > <A = HREF=3D"https://datatracker.ietf.org/public/pidtracker">https://datatrack= er.ietf.org/public/pidtracker</A>> .cgi<BR> > Put in<BR> > "CDI" for WG acronym and hit "Search". = Then hit<BR> > the "DETAIL" button for the known-request-routing = draft.<BR> ><BR> > Abbie (and other interested parties), can you take a look at<BR> > what's there and see what we need to do to fix the identified<BR> > problems?<BR> ><BR> > Thanks,<BR> ><BR> > --Mark<BR> ><BR> ><BR> ><BR> <BR> <BR> </FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C2C8B2.ED730EA4-- ------=_NextPartTM-000-38ef6928-347a-11d7-ba7f-006067005148--