Re: 193.in-addr.arpa procedures V1.3

> 
> 
>  bonito@localhost (Antonio_Blasco Bonito) writes:
>  * > 
>  * > 
>  * > Folks,
>  * > 
>  * > One last go. I think we folded in most of the comments from Blaso and othe
>  * rs.
>  * > We have included the procedures for single class C reverse zones, not via
>  * > block zones.
>  * > 
>  * > We are already doing our first trials with block delegations, all seems to
>  * > work fine. Please let's get this document accepted and delegate these bloc
>  * ks.
>  * 
>  * Sorry for this late comment, but it has come now to my mind:
>  * I think it would be wise to include recommended values for SOA fields
>  * (refresh, retry, etc). This could save problems to ns.ripe.net
>  * when acting as secondary.
> 
> What do you think recommended values are ? I know have for everything in
> 193.in-addr.arpa:
> 
> @               IN      SOA     ns.ripe.net.      hostmaster.ripe.net.
>                         (
>                                    1.20  ; Serial
>                                  14400  ; Refresh 4 hours
>                                   3600  ; Retry   1 hours
>                                 604800  ; Expire  7 days
>                                 518400  ; TTL     6 days
>                         )
> 
> which in my view is reasonable, since these things (just delegations) do not
> change too often. For the actual class C zones, we have for
> 45.87.192.in-addr.arpa (RIPE NCC net):
> 
> @               IN      SOA     ns.ripe.net.      hostmaster.ripe.net.
>                         (
>                                    1.4  ; Serial
>                                  28800  ; Refresh 8 hours
>                                   7200  ; Retry   2 hours
>                                 604800  ; Expire  7 days
>                                  86400  ; Minimum 1 day
>                         )
> 
> Are these fine to be recommended ?
> 
> -Marten
> 

I think the following could be reasonable values and rules to recommended.
Refresh and retry have a direct impact on how much ns.ripe.net will have
to do when acting as secondary for delegated 256-Cblocks.
Maybe Piet Berteema has something more to say on this subject.

	(
		yymmddv	; Serial
		28800	; Refresh 8 hours
		3600	; Retry   1 hour
		604800	; Expire  7 days
		172800	; Default TTL 2 days
	)

where yyddmmv is the recommended way to hold the update serial number
with yy being the two-digit year number (to become four-digits on year 2000)
     mm being the two-digit month number
     dd being the two-digit day number
      v being a one digit serial number



----------                                                     ----------
Antonio_Blasco Bonito                          E-Mail: bonito@localhost
GARR - Network Information Service      c=it;a=garr;p=garr;o=nis;s=bonito
c/o CNUCE - Istituto del CNR                         Tel: +39 (50) 593246
Via S. Maria, 36                                    Telex: 500371 CNUCE I
56126 PISA   Italy                                   Fax: +39 (50) 904052
----------                                                     ----------