From rserpool-bounces@ietf.org Thu Jun 08 17:05:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoRgq-0005bl-Fh; Thu, 08 Jun 2006 17:05:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoRgo-0005aq-UG for rserpool@ietf.org; Thu, 08 Jun 2006 17:05:14 -0400 Received: from lin1-118-39-27.ciena.com ([63.118.39.27] helo=mdmxm02.ciena.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoRgn-0004uq-NL for rserpool@ietf.org; Thu, 08 Jun 2006 17:05:14 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 8 Jun 2006 17:05:02 -0400 Message-ID: <0901D1988E815341A0103206A834DA07DEB467@mdmxm02.ciena.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Last Call on ASAP and ENRP specifications Thread-Index: AcaLPzWOamp9c+8VRAuenEN4WUzGoQ== From: "Ong, Lyndon" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: Lars Eggert , Maureen.Stillman@nokia.com Subject: [Rserpool] WG Last Call on ASAP and ENRP specifications X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1805918171==" Errors-To: rserpool-bounces@ietf.org This is a multi-part message in MIME format. --===============1805918171== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C68B3F.356CD973" This is a multi-part message in MIME format. ------_=_NextPart_001_01C68B3F.356CD973 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Folks, =20 Maureen and I would like to initiate WG Last Call on the ASAP and ENRP specs, plus the associated common parameters draft. The applicable drafts are: =20 1) draft-ietf-rserpool-asap-13.txt 2) draft-ietf-rserpool-enrp-13.txt 3) draft-ietf-rserpool-common-param-10.txt =20 Last Call will begin on Friday, June 9, ending Friday, June 23. Please submit comments with the related draft title in your subject header (e.g., "LC Comment on ASAP" or "LC Comment on Parameters") so people can keep track of comments more easily. =20 Cheers, =20 Lyndon ------_=_NextPart_001_01C68B3F.356CD973 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi=20 Folks,

Maureen and I would=20 like to initiate WG Last Call on the ASAP and ENRP specs, plus the=20 associated

common = parameters=20 draft. The applicable drafts are:

1)=20 draft-ietf-rserpool-asap-13.txt

2)=20 draft-ietf-rserpool-enrp-13.txt

3)=20 draft-ietf-rserpool-common-param-10.txt

Last = Call will begin=20 on Friday, June 9, ending Friday, June 23. Please submit comments = with=20 the

related draft title=20 in your subject header (e.g., "LC Comment on ASAP" or "LC Comment on=20 Parameters")

so = people can keep=20 track of comments more easily.

Cheers,

Lyndon

------_=_NextPart_001_01C68B3F.356CD973-- --===============1805918171== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool --===============1805918171==-- From rserpool-bounces@ietf.org Thu Jun 22 11:34:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtRCH-00054V-CU; Thu, 22 Jun 2006 11:34:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtRCG-00054Q-F5 for rserpool@ietf.org; Thu, 22 Jun 2006 11:34:20 -0400 Received: from adsl-070-155-160-098.sip.cae.bellsouth.net ([70.155.160.98] helo=lakerest.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtRCF-0002cm-1M for rserpool@ietf.org; Thu, 22 Jun 2006 11:34:20 -0400 Received: from [IPv6:::1] (localhost [IPv6:::1]) by lakerest.net (8.13.6/8.13.4) with ESMTP id k5MFXlDL087908; Thu, 22 Jun 2006 11:33:55 -0400 (EDT) (envelope-from randall@lakerest.net) Message-ID: <449AB86B.3090303@lakerest.net> Date: Thu, 22 Jun 2006 11:34:03 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ong, Lyndon" Subject: Re: [Rserpool] WG Last Call on ASAP and ENRP specifications References: <0901D1988E815341A0103206A834DA07DEB467@mdmxm02.ciena.com> In-Reply-To: <0901D1988E815341A0103206A834DA07DEB467@mdmxm02.ciena.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: Lars Eggert , Maureen.Stillman@nokia.com, rserpool@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rserpool-bounces@ietf.org All: I have a LOT of comments yet to make on asap and a couple of tweaks (if I remember right) to suggest for the common-param's... How I am coming up with these is by "eatting my own dog-food" and implementing asap based on the spec.. Now that being said, I am doing this mainly at 30,000 feet it seems.. and I am still not done implementing ASAP... there is no way I will get to ENRP (which I bet will have has many or MORE comments then I have already collected in my annotated version of asap-13)... I will try to convert my comments on ASAP into an email tommorrow at 30,000 feet again as I travel back from networkers... Will I make the Friday deadline? I hope so.. but I may not get it sent until Saturday AM.. IMO my comments are changes enough that I think we will need another spin of ASAP... and another LC.. after we sort things out :-D ENRP.. well.. this is a tricky one.. since I just don't have the cycles to implement this for a few weeks at the very least .. and I know it will need updates :-( R Ong, Lyndon wrote: > Hi Folks, > > Maureen and I would like to initiate WG Last Call on the ASAP and ENRP > specs, plus the associated > common parameters draft. The applicable drafts are: > > 1) draft-ietf-rserpool-asap-13.txt > 2) draft-ietf-rserpool-enrp-13.txt > 3) draft-ietf-rserpool-common-param-10.txt > > Last Call will begin on Friday, June 9, ending Friday, June 23. Please > submit comments with the > related draft title in your subject header (e.g., "LC Comment on ASAP" > or "LC Comment on Parameters") > so people can keep track of comments more easily. > > Cheers, > > Lyndon > > > > ------------------------------------------------------------------------ > > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool -- Randall Stewart 803-345-0369 815-342-5222(cell) _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Thu Jun 22 15:30:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtUsn-0007XO-14; Thu, 22 Jun 2006 15:30:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtUsl-0007Va-Fr for rserpool@ietf.org; Thu, 22 Jun 2006 15:30:27 -0400 Received: from ripley.ciena.com ([63.118.34.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtUsk-0002sy-7g for rserpool@ietf.org; Thu, 22 Jun 2006 15:30:27 -0400 Received: from mdmail4.ciena.com (HELO mdmxm02.ciena.com) ([63.118.39.27]) by ripley.ciena.com with ESMTP; 22 Jun 2006 15:39:11 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rserpool] WG Last Call on ASAP and ENRP specifications Date: Thu, 22 Jun 2006 15:30:04 -0400 Message-ID: <0901D1988E815341A0103206A834DA07E7C804@mdmxm02.ciena.com> In-Reply-To: <449AB86B.3090303@lakerest.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Rserpool] WG Last Call on ASAP and ENRP specifications Thread-Index: AcaWEVkQDO9dUoAKT+6xjm4lbG/tJAAILEvg From: "Ong, Lyndon" To: "Randall Stewart" X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: Lars Eggert , Maureen.Stillman@nokia.com, rserpool@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rserpool-bounces@ietf.org Hi Randy, If there are a lot of comments coming from implementation, and it will be a rush to document these by Friday, my suggestion would be to extend the Last Call period for another week. Would that be OK to everyone? That would make the end of Last Call Friday, June 30th. Cheers, Lyndon=20 -----Original Message----- From: Randall Stewart [mailto:randall@lakerest.net]=20 Sent: Thursday, June 22, 2006 8:34 AM To: Ong, Lyndon Cc: rserpool@ietf.org; Lars Eggert; Maureen.Stillman@nokia.com Subject: Re: [Rserpool] WG Last Call on ASAP and ENRP specifications All: I have a LOT of comments yet to make on asap and a couple of tweaks (if I remember right) to suggest for the common-param's... How I am coming up with these is by "eatting my own dog-food" and implementing asap based on the spec.. Now that being said, I am doing this mainly at 30,000 feet it seems.. and I am still not done implementing ASAP... there is no way I will get to ENRP (which I bet will have has many or MORE comments then I have already collected in my annotated version of asap-13)... I will try to convert my comments on ASAP into an email tommorrow at 30,000 feet again as I travel back from networkers... Will I make the Friday deadline? I hope so.. but I may not get it sent until Saturday AM.. IMO my comments are changes enough that I think we will need another spin of ASAP... and another LC.. after we sort things out :-D ENRP.. well.. this is a tricky one.. since I just don't have the cycles to implement this for a few weeks at the very least .. and I know it will need updates :-( R Ong, Lyndon wrote: > Hi Folks, > =20 > Maureen and I would like to initiate WG Last Call on the ASAP and ENRP > specs, plus the associated common parameters draft. The applicable=20 > drafts are: > =20 > 1) draft-ietf-rserpool-asap-13.txt > 2) draft-ietf-rserpool-enrp-13.txt > 3) draft-ietf-rserpool-common-param-10.txt > =20 > Last Call will begin on Friday, June 9, ending Friday, June 23. =20 > Please submit comments with the related draft title in your subject=20 > header (e.g., "LC Comment on ASAP" > or "LC Comment on Parameters") > so people can keep track of comments more easily. > =20 > Cheers, > =20 > Lyndon >=20 >=20 >=20 > ---------------------------------------------------------------------- > -- >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool -- Randall Stewart 803-345-0369 815-342-5222(cell) _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Thu Jun 22 16:44:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtW2M-0001ae-Ah; Thu, 22 Jun 2006 16:44:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtW2K-0001OK-TZ for rserpool@ietf.org; Thu, 22 Jun 2006 16:44:24 -0400 Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtW2J-0002Ca-DP for rserpool@ietf.org; Thu, 22 Jun 2006 16:44:24 -0400 Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k5MKiEUZ008399; Thu, 22 Jun 2006 23:44:19 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jun 2006 23:44:17 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Jun 2006 15:43:45 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Rserpool] WG Last Call on ASAP and ENRP specifications Date: Thu, 22 Jun 2006 15:43:46 -0500 Message-ID: In-Reply-To: <0901D1988E815341A0103206A834DA07E7C804@mdmxm02.ciena.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Rserpool] WG Last Call on ASAP and ENRP specifications Thread-Index: AcaWEVkQDO9dUoAKT+6xjm4lbG/tJAAILEvgAAKgG1A= From: To: , X-OriginalArrivalTime: 22 Jun 2006 20:43:45.0149 (UTC) FILETIME=[8E0452D0:01C6963C] X-Spam-Score: 0.2 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Cc: lars.eggert@netlab.nec.de, rserpool@ietf.org X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rserpool-bounces@ietf.org Sounds good.=20 -- Maureen Maureen Stillman Nokia Enterprise Solutions Acting Director SMC Systems Architecture -----Original Message----- From: ext Ong, Lyndon [mailto:Lyong@Ciena.com]=20 Sent: Thursday, June 22, 2006 3:30 PM To: Randall Stewart Cc: Lars Eggert; Stillman Maureen (Nokia-ES/MtView); rserpool@ietf.org Subject: RE: [Rserpool] WG Last Call on ASAP and ENRP specifications Hi Randy, If there are a lot of comments coming from implementation, and it will be a rush to document these by Friday, my suggestion would be to extend the Last Call period for another week. Would that be OK to everyone? That would make the end of Last Call Friday, June 30th. Cheers, Lyndon=20 -----Original Message----- From: Randall Stewart [mailto:randall@lakerest.net] Sent: Thursday, June 22, 2006 8:34 AM To: Ong, Lyndon Cc: rserpool@ietf.org; Lars Eggert; Maureen.Stillman@nokia.com Subject: Re: [Rserpool] WG Last Call on ASAP and ENRP specifications All: I have a LOT of comments yet to make on asap and a couple of tweaks (if I remember right) to suggest for the common-param's... How I am coming up with these is by "eatting my own dog-food" and implementing asap based on the spec.. Now that being said, I am doing this mainly at 30,000 feet it seems.. and I am still not done implementing ASAP... there is no way I will get to ENRP (which I bet will have has many or MORE comments then I have already collected in my annotated version of asap-13)... I will try to convert my comments on ASAP into an email tommorrow at 30,000 feet again as I travel back from networkers... Will I make the Friday deadline? I hope so.. but I may not get it sent until Saturday AM.. IMO my comments are changes enough that I think we will need another spin of ASAP... and another LC.. after we sort things out :-D ENRP.. well.. this is a tricky one.. since I just don't have the cycles to implement this for a few weeks at the very least .. and I know it will need updates :-( R Ong, Lyndon wrote: > Hi Folks, > =20 > Maureen and I would like to initiate WG Last Call on the ASAP and ENRP > specs, plus the associated common parameters draft. The applicable=20 > drafts are: > =20 > 1) draft-ietf-rserpool-asap-13.txt > 2) draft-ietf-rserpool-enrp-13.txt > 3) draft-ietf-rserpool-common-param-10.txt > =20 > Last Call will begin on Friday, June 9, ending Friday, June 23. =20 > Please submit comments with the related draft title in your subject=20 > header (e.g., "LC Comment on ASAP" > or "LC Comment on Parameters") > so people can keep track of comments more easily. > =20 > Cheers, > =20 > Lyndon >=20 >=20 >=20 > ---------------------------------------------------------------------- > -- >=20 > _______________________________________________ > rserpool mailing list > rserpool@ietf.org > https://www1.ietf.org/mailman/listinfo/rserpool -- Randall Stewart 803-345-0369 815-342-5222(cell) _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From rserpool-bounces@ietf.org Mon Jun 26 13:50:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuvEO-0007KA-2v; Mon, 26 Jun 2006 13:50:40 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuvEN-0007K5-Av for rserpool@ietf.org; Mon, 26 Jun 2006 13:50:39 -0400 Received: from adsl-070-155-160-098.sip.cae.bellsouth.net ([70.155.160.98] helo=lakerest.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FuvEM-0004v4-Ql for rserpool@ietf.org; Mon, 26 Jun 2006 13:50:39 -0400 Received: from [IPv6:::1] (localhost [IPv6:::1]) by lakerest.net (8.13.6/8.13.4) with ESMTP id k5QHoWHh012871 for ; Mon, 26 Jun 2006 13:50:32 -0400 (EDT) (envelope-from randall@lakerest.net) Message-ID: <44A01E6E.6070303@lakerest.net> Date: Mon, 26 Jun 2006 13:50:38 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'rserpool@ietf.org'" Content-Type: multipart/mixed; boundary="------------090000000004090104090409" X-Spam-Score: 0.1 (/) X-Scan-Signature: bf422c85703d3d847fb014987125ac48 Subject: [Rserpool] comments to ASAP.. and a few for ENRP X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rserpool-bounces@ietf.org This is a multi-part message in MIME format. --------------090000000004090104090409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Now here is what I picked off at 30,000 feet... Friday.. and I added one more at the end that I detected as I was implementing... Notice that term.. considering I am not done implementing and still generating comments.. I think there will be more comments as I finish implementing.. and a bunch of comments (besides the few I make here) when I get to implementing ENRP... ---------Comments---------------------- -- Randall Stewart 803-345-0369 815-342-5222(cell) --------------090000000004090104090409 Content-Type: text/plain; name="asap-comments" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="asap-comments" -------------------------------------------- Section 2.2.10 The server idenity field is confusing.. it is actually (from at least what I can tell and what I remember) a 32 bit field.. yet it appears in the document to be a TLV.. it should not be. Note also I researched this a bit in ENRP as well and there seems to be multiple names used for the same field.. this needs to be consistent (so here is an ENRP comment.. I guess I lied :-D) -------------------------------------------- End of Section 2... and a confusion on my part. No where in asap can I find a specific directive that the way you tell ASAP vs other things is in the PPID field from SCTP (or its equivalant tcp adaption thingy). Now this should be spelled out here. Secondary question.. should we not have an ENRP related PPID as well? Or is that really needed since the ENRP deamons can setup seperate sockets to deal with inter ENRP comm? -------------------------------------------- Section 3.4 There is no specification of how your home server changes. This should be explictly stated. In general an ASAP client should be promiscuous.. any time a HB comes in from an ENRP server, that should become the new home ENRP servers. ENRP servers themeselves end up agreeing on who owns whom.. and thus only one will send a HB.. normally where you orginally registered at. Now also we need comments about the "subscribe for update" that we wanted to do in here somewhere too. I.e. I can ask for dynamic updates to any pool handle reg/de-reg as a client. A change occurs and the ENRP home server pushes it out to me.. but of course a change of home server forces a re-reg of this request since ENRP does not share who is getting pushed data. This all needs to be put in both ENRP and ASAP.. so far its un-specified. ------------------------------------------- 3.6 server hunt... states: SH1) The PE or PU SHOULD try to establish an association or connection with no more than three ENRP server addresses. An endpoint MUST NOT try to establish more than three association or connections at any single time. RRS:different or the same guy (3 addresses)? What I think we want is 3 unique ENRP servers.. not 3 addresses.. since an ENRP server can and should be multi-homed :-D Also this section states: SH5.1) The endpoint MUST double the value of the T5-Serverhunt timer. RRS: What caps the doubling.(RTO.Max?). or does it just go on and on? And for that matter, why double with a 120 second timer? It really is so SLOW I think we should NOT double it Note in TCP/SCTP RTO.Max is 60 seconds... ------------------------------------------- 3.7.1 send failure states: In such a case, the ASAP endpoint should not re-send the failed message. Instead, it should discard the failed message and start the ENRP server hunt procedure as described in Section 3.6 Should it not also note the action it was after and queue this to use once you find a new enrp server? Aka if you are requesting resolution of pool name X, should you not indicate to the request (there is a timer running there) that you are now getting a new name server.. and then after that occurs, resubmit the request? You should but this is not clearly defined... It is also not clear what you do in case C i.e. a registration failure. This should be specified (fix what is wrong if you can deduce it and retry.. or report to the user the failure) ---------------------------------------- 5.1 default values T5-Serverhunt - This timer is used during the ENRP server hunt procedure and is normally set to 120 seconds. RRS: This is way to big if your doubling --------------------------------------- 5.3 states: MAX-REG-ATTEMPT - The maximum number of registration attempts to be made before a server hunt is issued. RRS: So what is the default. and MAX-REQUEST-RETRANSMIT - The maximum number of attempts to be made when requesting information from the local ENRP server before a server hunt is issued. RRS: So what are the default values for the above three items?? --------------------------------------- Another issue.. PE-Id.. The value is globally unique to all pools? Or should be. We need to specify this very clearly... the fact that there is a home-enrp-server id in the pe info is confusing. It makes one wonder if the home-enrp-server+pe-id is unique OR is it just the pe-id which is unique?? I think we wanted pe-id unique alone, so in such a case maybe the name resolution response message should have the home-enrp-server id set to 0 for the responses to the PU's and PE's... I think the field is there for use in ENRP.. but for ASAP we don't need to see this field.. it is confusing and it actually gives away a bit of information. Maye ENRP should say something about this field MUST be set to 0 in the response message to a name resolution request... --------------090000000004090104090409 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool --------------090000000004090104090409-- From rserpool-bounces@ietf.org Wed Jun 28 09:44:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvaLR-0005VB-93; Wed, 28 Jun 2006 09:44:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FvaLP-0005HT-Bg for rserpool@ietf.org; Wed, 28 Jun 2006 09:44:39 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FvaLP-0000Tz-AE for rserpool@ietf.org; Wed, 28 Jun 2006 09:44:39 -0400 Received: from adsl-070-155-160-098.sip.cae.bellsouth.net ([70.155.160.98] helo=lakerest.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FvaJM-00089A-SN for rserpool@ietf.org; Wed, 28 Jun 2006 09:42:34 -0400 Received: from [IPv6:::1] (localhost [IPv6:::1]) by lakerest.net (8.13.6/8.13.4) with ESMTP id k5SDgKnC024084 for ; Wed, 28 Jun 2006 09:42:22 -0400 (EDT) (envelope-from randall@lakerest.net) Message-ID: <44A28743.1090607@lakerest.net> Date: Wed, 28 Jun 2006 09:42:27 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'rserpool@ietf.org'" Subject: Re: [Rserpool] comments to ASAP.. and a few for ENRP References: <44A01E6E.6070303@lakerest.net> In-Reply-To: <44A01E6E.6070303@lakerest.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.3 (-) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 X-BeenThere: rserpool@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Reliable Server Pooling List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rserpool-bounces@ietf.org All: And another thought as I work through implementing the PE/PU side stuff.. In the Pool Element are two sets of transport addresses: User Transport Param ASAP Transport Param. Now, the ASAP param must be SCTP... What is the purpose of this entry? The document is not clear and, in thinking about its uses I can come up with a couple of scenario's none of which I like: a) The ASAP TP is the communication endpoint used by the PE to register and talk to the ENRP server... problem with this IMO is that the PU does NOT need this information! Now it may be here implicitly since ENRP and ASAP use the same message format.. if so thats ok.. we just need to make sure the parameter is NOT sent in a name-resolution-resp by the ENRP server... this needs to be documented if so.. b) The ASAP TP is used when the peer has a different DATA transport (say UDP) and wants to still communicate with ASAP.. i.e. we end up with seperate control and data connections/paths. This, I think, is the real purpose of this info.. and I don't like it one bit. Why, it really becomes a mess if you allow seperate PU <-> PE data and asap communication. The issue is coordination. We have, over the PE<->PU control side a number of messages (COOKIES, BUSINESS-Cards ... etc).. The COOKIE, for example, needs to arrive first.. ahead of anything else to assit the PE in building state... But coodinating between two transports is a royal pain.. and much more difficult. IMO if the user wishes to use UDP for DATA only, then thats ok.. they work at a more primitive level.. and don't get all the benefits necessarily... If the transport for data is control+data then no matter how you slice it in the case of its redundant .. since it should contain the same information... So, I think we should cut the ASAP transport parameter out of the PE message unless ENRP uses it between its peer servers... have not looked at that aspect.. but if its for multiple connections between PU-PE.. I think it will be more headache then usefulness. Comments?? R -- Randall Stewart 803-345-0369 815-342-5222(cell) _______________________________________________ rserpool mailing list rserpool@ietf.org https://www1.ietf.org/mailman/listinfo/rserpool From 2Dmr76G5na@mail.ru Fri Jun 30 22:02:20 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwUoO-0000sN-6m for rserpool-archive@lists.ietf.org; Fri, 30 Jun 2006 22:02:20 -0400 Received: from [220.180.110.138] (helo=lenovo-f8df3482) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwUoM-0002Oy-Na for rserpool-archive@lists.ietf.org; Fri, 30 Jun 2006 22:02:20 -0400 Date: Sat, 1 Jul 2006 02:02:17 -0480 From: "Shauna Silva" X-Mailer: The Bat! (v3.6.07) UNREG / 77YIB4V52SDZ8OWANJ Reply-To: "Shauna Silva" X-Priority: 3 (Normal) Message-ID: <2162355037.20060701020217@mail.ru> To: rserpool-archive@lists.ietf.org Subject: :), Owl nebula MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.7 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Even if you have no erectin problems SOFT CIAzLIS would help you to make BETTER SE X MORE OFTEN! and to bring unimagnable plesure to her. Just disolve half a pil under your tongue and get ready for action in 15 minutes. The tests showed that the majority of men after taking this medic ation were able to have PERFECT ER ECTI ON during 36 hours! VISIT US, AND GET OUR SPECIAL 70% DISC OUNT OFER! http://I9QTQE.notifylearn.com ========== said kindly. "If anybody can show someone on the ground how to see a said screw it long ago and gone to work on something else for the same Lowell Gull became a condemned bird, labeled Outcast; and the eighth of more rails, a locomotive with flatcars on the rails. In other words, an twisting curve through his wings. The curve meant that he would fly laid the tracks to it yet. You know that. So here we come back from the Zone proud or how hurt a bird was Fletcher Seagull. The breeze seemed to have died down and I didn't hear anything bad. The